Tag Info

New answers tagged

0

Use grep to exclude databases you don't want: candidates=$(echo "show databases" | mysql | grep -Ev "^(Database|mysql|performance_schema|information_schema)$") mysqldump --databases $candidates From looking at http://stackoverflow.com/questions/19354870/bash-command-line-and-input-limit it seems like you'll be able to handle long lines. Otherwise you can ...


1

Straight to answer your questions : Can I stop, pause, or cancel the backup after it has started if it is taking too long or slowing things down too much? You cannot pause a backup - either running using Tsql or using sql agent job. You can stop it or kill it using the kill spid command. you have to be cautious as if you kill a job that is already ...


0

I will be assuming that you are using native backups as you have not mentioned a specific product. However, depending on what backup product you are using (Litespeed, RedGate Hyperbac, etc) you may be able to stop a backup but it may not be as simple as clicking stop from within management studio for an Ad-Hoc backup command. For a native backup the engine ...


0

Simply make new folder "C:\DB\" and restore there your DB with MOVE option - in any case if you again reinstall another SQL Server VERSION on your PC - this path will NOT BE CHANGED.


-3

RESTORE DATABASE DB_NAME ... WITH RECOVERY, REPLACE; -- will restore your "DB"(overwrite) ALWAYS! Do not listen for "DB_A & DB_B as well". "DB" will be your restored database name. Use RECOVERY for the state "ON-LINE" and REPLACE for overwriting existing database files. Use MOVE for the different file location (different from original one). No other ...


0

A partly online backup is certainly possible but switching to and back from archivelog mode needs downtime. As an alternative you could run in regular archivelog mode and trash the generated archived log files, until you run a backup. For the backup to be recoverable it is important that it has ALL archived log files that were generated during the backup. ...


0

This KB isn't directly related but the quote in it is. http://support.microsoft.com/kb/2615182 When Windows Server Backup attempts to backup a disk volume, a Volume Shadow Copy Snapshot is created for the volume. When the snapshot is created any VSS writer associated with the volume is called. If there are SQL Server VSS writer backups being taken ...


0

I encountered this problem a couple of times. The issue is not with SQL Server but with Windows Permission of the folder. You have to add appropriate permission to the folder where you copied .bak file (I think System Network role). The easier solution is, to move the file to the default back up folder in Program Files. It has all the necessary permission. ...


1

You literally do not need a third party tool. STEP 01 Find out the path to the data by running mysql> SHOW GLOBAL VARIABLES LIKE 'datadir'; For this example, let's suppose it is C:\Program Files\MySQL\MySQL 5.6\data STEP 02 Pick a destination folder to copy the data directory For this example, let's pick D:\MySQLBackup STEP 03 Create batch file ...


1

If you do not have any backups that contains the deleted table, you can't restore the database to it's original form.


1

Basically, you need the following paradigm Session #1 (MySQL) Lock all tables Read Lock Sleep for a Long Time Session #2 (Windows) : This you are already doing Copy the .frm, .MYD, .MYI files for every MyISAM table Session #3 (After Session #2 is Complete) Look for Sleeping Connection of Session #1 Kill the SLEEP Query (Session #1 Will Terminate) ...



Top 50 recent answers are included