Tag Info

Hot answers tagged

29

This is a terrific idea! Terrifically bad! You'll need to backup your registry, SYSVOL folder, Ntds.dit, Edb.chk, Edb*.log, Res1.log and Res2.log. Oh, but that's not all! If there are other domain controllers in the domain you'll have to worry about non-authoritative versus authoritative restores. Just try doing that without a proper, "Microsoft Sanctioned" ...


12

Here is something interesting to consider: Backing up the mysql database limits you greatly in that you can only restore such a database to the same version of mysql you ran the backup from. Here is why: Here is mysql.user from MySQL 5.0.45 mysql> desc mysql.user; ...


10

If you use innodb tables, you can use http://www.percona.com/docs/wiki/percona-xtrabackup:start That will take a dump of your database that can be imported by their tools also without locking. I believe if you have myisam tables it locks those.


9

Yes, you definitely want to backup the mysql database -- it's an integral part of your service. While you can reconstruct it's contents from other information, the difficulty of doing so is prohibitive if you're trying to get back to service quickly.


8

Ok, first - Tape is more reliable than (disc) drives. Mostly / also because with a drive the drive is on the medium, with a tape you can use another drive to read a tape. Tapes also store huge amounts of data for a relatively low price - they are the most efficient form for offline backup (no real time single file restore) and often used in combination with ...


8

The minimum permissions to back up a database are PUBLIC at the server level and DB_BACKUPOPERATOR at a database level. In SQL Server 2005, Microsoft recommended against removing NT AUTHORITY\SYSTEM from the sysadmin role: The NT AUTHORITY\SYSTEM account is also granted a SQL Server login. The NT AUTHORITY\SYSTEM account is provisioned in the ...


7

Full backups, successful or failed, do not truncate the log. Only log backups do. So a failed full backup has no impact on the log backup chain, is like no operation was done at all. If that would not be true, you could not possibly create a safe maintenance plan: any failed full backup would put your database at danger if it would interrupt the log backup ...


6

ReplicaSet will work in this scenario. However, I cannot tell if having two MongoDB instances at the same server is a good idea -- this depends on the server hardware/software and load. To make sure your backup MongoDB node does not become master, set its priority parameter to 0, e.g. rs.add({_id: 1, host: "localhost:<port>", priority: 0}) NOTE: if ...


6

There is a way to get the result you're after but it's not a backup and should not be considered as such (see gbn's answer to understand why). This is a handy tool for generating scripts that you might use in an application installer and to prime your application's database with objects such as stored procedures, views reference tables and data. But it's ...


6

It all depends on the database. If you don't have a way to tell the database engine "get all your files in a consistent state", then you can't do a snapshot, because the snapshot has no guarantee that the files within it are consistent between themselves -- you could take the snapshot at a moment when one file in the database has been changed, and another ...


6

RESTORE HEADERONLY FROM DISK = 'pathTobackupFile' The database version can be found in the column: DatabaseVersion From Jonathan Kehayias blog post here the number in this column: SQL Server 7.0 databases have version number 515 SQL Server 2000 databases have version number 539 SQL Server 2005 databases have version number 611/612 SQL Server 2008 ...


5

1) Setup a second server, replicate your DB to it, backup from there This might not be a good solution if you have lots of changes on your master server, since replication on the slave is single threaded. 2) Use http://www.percona.com/doc/percona-xtrabackup/ Or as always, consult the official documentation which outlines other alternatives: ...


5

Backups of MySQL are normally done via the command line but if you really want a GUI interface you could use something like HeidiSQL, which allows you to export and import your data as eithe CSV or SQL files, which you can place wherever you like. I do recommend that you learn to use the command line tools, such as mysqldump as that will allow you to ...


5

If you are using innodb or another backend that's fully transactional, you can use mysqldump --single-transaction .... I have used this on fairly large (~100GB) databases with good results; if the database is under heavy load it can take hours but it does work without locking your tables. Replication is generally better but sometimes you want a nice solid ...


5

Use mysqldump --no-data to dump the database schema but not the data and then restore that dump on your new database server. If you are using triggers or stored procedures you should include the respective parameters in your mysqldump call. See 4.5.4. mysqldump — A Database Backup Program for details.


5

I've had good success with MySQL replication and nightly tarballs. For smaller db, the mysql database, and schema I use a combination of scripts designed to use mysqlhotcopy and mysqldump. InnoDB hot backup is a great commercial product but I'm not sure how it handles mixed tables in the same database. pQd's recommendation for XtraBackup may be good to ...


5

When you run a command from cron, it doesn't have access to your environment information the same way that it would if it were run from the shell. This means that it doesn't find your ssh key, or whatever environment variables you are using to set your SSH agent. If you're using a passwordless key, change your rsync line to this: rsync -chavzP -e "ssh -i ...


4

No, you don't want to go messing with previous backups. The next backup which is made will not contain the deleted user anymore. Your backups should be frequent enough that if you need to restore one there isn't too much work to redo (like deleting users again).


4

I would do like this: Backup database Create new log file Run shrinkfile on the old database Set the Initial Size of old Log File to 1MB and Authogrowth to None. You will have two log files, but one will have only 1 MB. Hope it would help. I hope there is some better way to do that


4

xtrabackup - at least for innodb.


4

A differential backup contains all the changes made to the database since the last full backup. You only need to restore the full backup and the last differential one.


4

My strategy would include: Implementing a Active-Passive Cluster Bare Metal Recovery Backups A warm-site spare if downtime costs justified it


4

Ok, you really need to head over to the documentation and read it - become a small dba. Expecting people here to copy / paste the EXTREMELY detailed information from BOOKS ONLINE - the SQL Server documentation - is not good behavior. That said, you also areon the wrong site - this is so absolutely NOT a programming issue. There is a sister site ...


4

Those permissions should be all that's needed for the mysqldump. Since you've granted LOCK TABLES, and it's erroring on LOCK TABLES, seems like the permissions are inconsistent. Have you run a FLUSH PRIVILEGES?


4

To run a backup from Right Click > Tasks > Backup in SSMS you do not require the SQL agent to be running (this backup method works in SQL Express which does not allow the Agent to run).


4

As long as you restore to a similar mysql version, you can restore of the mysql database from a backup. If you are in doubt, just make a diff between mysql database schemas (the one from the backup and the one from the new mysql server).


4

You can restore the mysql database between versions, at least fairly recent versions. There is a tool called mysql_upgrade included in new versions of MySQL that will upgrade the system tables for you. http://dev.mysql.com/doc/refman/5.0/en/mysql-upgrade.html


4

Wow. Amazing number of questions. I will try to address some, but this answer is not complete yet. how to determine where the bottleneck is. Use top first to see what's going on during the dump. Inspect process CPU usage, process status. D means "waiting for I/O". Is the poor performance caused by heavy I/O operations? Yes, most probably. ...


4

Look into VMware vSphere 5.0 with VSA (Virtual Storage Appliance). This will allow you to run a cluster on the two machines and will automatically replicate the VMs between the two machines in real time. Data within SQL Server isn't considered accepted until it is written to the transaction log. Once that has been written to disk the client application ...


4

250TB is a lot of data. I will give you an example of how I would accomplish this task in the enterprise, which would be fairly concerned with budget (since I assume you want this on the cheap), yet not overly concerned with finding the best free products to do the job. Just an FYI - I am writing this as an 8 year professional of both the storage world and ...



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