Tag Info

Hot answers tagged

33

dpkg -i --force-confmiss mysql-common.deb will recreate any missing configuration files, ie /etc/mysql/my.cnf in your case.


25


15

One thing that may be slowing the process is the key_buffer_size, which is the size of the buffer used for index blocks. Tune this to at least 30% of your RAM or the re-indexing process will probably be too slow. For reference, if you were using InnoDB and foreing keys, you could also disable foreing key checks and re-enable it at the end (using SET ...


14

Use the --no-data switch with mysqldump to tell it not to dump the data, only the table structure. This will output the CREATE TABLE statement for the tables. Something like this mysqldump --no-data -h localhost -u root -ppassword mydatabase > mydatabase_backup.sql To target specific tables, enter them after the database name. mysqldump --no-data -h ...


12

NOOOO, do NOT discontinue backup of master! Whereas most apps don't directly interface with the master database, master contains data for the current state of your server, databases, all kinds of things. That is horrible advice, to the point where I would seriously consider dumping their product. That really surprises me coming from a support agent of a ...


10

The answer is no, for whatever backup software is being used. A backup is a physical operation, not a logical operation. It reads all extents containing allocated pages (i.e. even though only a single page from an 8-page extent is allocated, it will backup the entire 64K extent), and it does it in physical order. A restore is a physical operation, not a ...


10

The solution was dumping it like this: pg_dump --no-owner --no-acl blah > blah.psql and importing it like this: psql blah_devel < blah.psql > /dev/null I still get this warning: WARNING: database "blah" does not exist but the rest seems to work.


10

Just run $ md5sum <filename> on each system, and verify the checksums match.


10

There's also the whole "Dropbox can read your stuff" problem. What you should do is encrypt everything before putting it into Dropbox. Use something like KeePass as a secrets vault. Put a good password on it. KeePass will encrypt locally, before putting your stuff into Dropbox. You will then use KeePass on other computers to access those secrets. Take ...


9

If you are creating a text dump you can export the database without the CREATE DATABASE bits (i.e. don't specify -c and -C options to pg_dump) ; This will prevent Postgres from trying to drop, create & connect to the database. If you're using one of the archive formats you can specify the -d option to pg_restore to name the database you want to restore ...


8

Your approach sounds very good - but I can think of a possible way to improve it. To reduce the impact of data loss since the last backup, and EBS volume failure (unlikely, but still possible) you could store your data on a separate EBS volume than your system files, and back up the data volume more frequently than the system volume. With your current ...


8

It's really pretty simple: Don't give the users "Administrator" rights and you're 95% of the way to keeping clean, happy machines. Don't give them "Power Users" under Windows XP or earlier, either, because that's effectively the same as "Administrator" (it's very, very easy to get to "Administator" from "Power Users"). Not having "Administrator" rights ...


8

Yes, there are lots of ways. There is a page in the documentation which summarizes many of the available methods. For example, you could take a look at: mysqldump db_name > dump_file


7

IBM has documentations for this scenario. See this page on DeveloperWorks: Using DB2 utilities to clone databases across different platforms Summary: Two DB2 utilities, db2move and db2look, can be used to clone databases when there is no support for cross-platform backup and restore operations. This article provides an overview of these ...


7

Restore the System State portion of the backup on another machine running W2K3 or Windows XP, choosing the "Single Folder" option for the "Restore files to" and picking some sensible "Alternate location" (like a directory you make for that purpose). You'll be warned about how this is an "advanced" feature and that not all files will be restore. For your ...


7

The backup headers in MSSQL2008 are different than those in MSSQL2005, which is likely the source of your problem. Try exporting the DB instead of the backup-restore paradigm, or set up MSSQL2008 on your DEV server.


7

I had the exact same problem in Srv2008 R2 and this is how I solved it: Right click on the folder your trying to restore from shadow copy and chose 'Previous versions'. Chose a date and click on open. Right click on any file or folder within the previous folder and chose 'properties'. Under 'General' copy what reads in 'location' - .e.g.: ...


6

You might try using Windows Server Backup, since it does support bare metal restores to different hardware. http://www.wbadmin.info/articles/hardware-independent-bare-metal-restore-windows-server-2008.html


6

A native SQL backup is just a page-by-page dump of the backup files, so the answer there is "no". A Quest lightspeed backup likely uses some sort of compression compression algorithm, but it still won't "rebuild" the data files or indexes, which would take a horrendously large amount of time on a big database.


6

In Debian Squeeze — at least —, we also can do it this way, after su — or sudo for Ubuntu — aptitude install -o Dpkg::Options::=--force-confmiss mysql-server This will care for the dependencies of mysql-server and reset all the missing conf files of the lot, including mysql-common. Conflicting (remaining) files will be prompted out to be kept or reset. ...


5

+1. Wow! The recommendation from Commvault partner support is horrifying. The master database holds the keys to the kingdom (database info, login info, server info, etc., etc). Without it you're effectivley toast. As others have stated, the master, model, and msdb databases should be set to Simple recovery mode and as such, can not have transaction log ...


5

This type of question is one reason why we never buy OEM server licenses. I want to be able to move licenses around if necessary. The usual rule for OEM licenses is that if you change the motherboard, it's a different computer and you can't use the license. Here's one article about what hardware changes in XP can require a new OEM license. If it were me, ...


5

The SQL Server Publishing Wizard can be automated with command line arguments. From the help page The following command will script the FooDB database from the default instance on a machine named MYSERVER using SQL Server authentication with the username "Alice" and the password "7h92-v6k3" to the file C:\FooDB.sql: sqlpubwiz script -d FooDB -S ...


5

This is imho the best answer for installing windows quickly and effortlessly: Microsoft Windows Remote Installation Service and Windows Deployment Services A PXE server that offers installation of windows and slipstreamed applications and drivers across a network. The difference between the two is that WDS is newer, comes with 2k3 Server SP2 and 2k7, ...


5

Assuming you stored your volume shadow copies on the same disk that you just moved the 100GB file onto you're probably out of luck. Undelete on NTFS, especially after making changes to the volume, is iffy at best. Shadow copies aren't backup. They're a nice crutch to help you recover files in some situations, but they shouldn't be relied upon as existing ...


5

You used the "NORECOVERY" flag which indicates to SQL server that you want to restore additional T-log backups. You should have used the "RECOVERY" flag instead (or nothing as this is the default). To recover, either recover the missing T-logs or, if you don't want to restore any more logs, issue the following statement: RESTORE DATABASE [MyDatabase] WITH ...


5

So far, I've been able to come up with the following procedure, but I really hope there is some simpler way: Install the operating system on a new server Create a new "dummy" domain and make the server its domain controller Install the operating system on a second server Join the server to the "dummy" domain Install DPM on the second server and connect it ...


5

I don't know anything about Veeam or VRanger/HP Data Protector but I wouldn't expect them to be compatible unless Veeam made specific statements about it. Even if Veeam made those statements I would certainly have tested the claim before I needed to use it. The last time I switched backup products I kept my legacy solution available until the retention ...


4

Thank you to l0c0b0x for your help on this. Based on http://msmvps.com/blogs/bradley/archive/2010/03/25/fixing-a-bit-of-pending-xml.aspx Steps: Boot from the Windows Server 2008 CD. Select the Command Prompt option. Execute the command "del C:\Windows\winsxs\pending.xml". Reboot from HDD. Notes: The original article talks about running the command ...


4

(upfront, I'll say hopefully you aren't using Previous Versions as your backup) Couple of ideas come to mind: First, search Microsoft's KB here: http://technet.microsoft.com/en-us/ms772425.aspx for any VSS updates that might be applicable to your OS revision level. Second check that the VSS writers are working correctly: Open an administrative cmd ...



Only top voted, non community-wiki answers of a minimum length are eligible