RE: Using 'master..sqlbackup' to do virtual restore

February 8, 2013, 4:41 am

≫ Next: RE: Restore Log takes many hours to fail

≪ Previous: RE: Using 'master..sqlbackup' to do virtual restore

$

0

0

I am looking to automate doing virtual restores on a number of databases after each nightly backup. The extended sp does this nicely, but it doesnt take advantage of the virtual restore feature -- too bad.

Using native sql then for each database that I want to check, I need something like this:

-- Script generated by Red Gate SQL Virtual Restore v2.4.0.164
-- Multi-threaded SQL Backup backups are handled by repeating the DISK parameter in the RESTORE command, once for each thread used during the backup process.
RESTORE DATABASE [MyDB_Virtual] FROM
DISK=N'D:\SQLBackup\MyDB\MyDB_FULL_20130205201700.sqb',
DISK=N'D:\SQLBackup\MyDB\MyDB_FULL_20130205201700.sqb',
DISK=N'D:\SQLBackup\MyDB\MyDB_FULL_20130205201700.sqb'
WITH MOVE N'MyDB_Data' TO N'F:\SQLBackup\MyDB\MyDB_MyDB_Virtual.vmdf',
MOVE N'MyDB_Log' TO N'F:\SQLBackup\MyDB\MyDB_MyDB_Virtual.vldf',
NORECOVERY, STATS=1
GO
RESTORE DATABASE [MyDB_Virtual] FROM
DISK=N'D:\SQLBackup\MyDB\MyDB_DIFF_20130207220005.sqb',
DISK=N'D:\SQLBackup\MyDB\MyDB_DIFF_20130207220005.sqb',
DISK=N'D:\SQLBackup\MyDB\MyDB_DIFF_20130207220005.sqb'
WITH NORECOVERY, STATS=1
GO
RESTORE DATABASE [MyDB_Virtual] WITH RECOVERY, RESTRICTED_USER
GO
DBCC CHECKDB ([MyDB_Virtual])
GO
DROP DATABASE [MyDB_Virtual]
GO

Obviously, this script changes each night in terms of file names and, if for some reason, the number of threads used changes.

So, is there something available that will generate this sort of sql given a database name and the folder that holds the full+diff backups?

Thanks.

---

RE: Restore Log takes many hours to fail

February 9, 2013, 5:58 am

≫ Next: RE: Restore Log takes many hours to fail

≪ Previous: RE: Using 'master..sqlbackup' to do virtual restore

$

0

0

Is the secondary database read-only, or read-write?

RE: Restore Log takes many hours to fail

February 11, 2013, 7:24 am

≫ Next: RE: Restore Log takes many hours to fail

≪ Previous: RE: Restore Log takes many hours to fail

$

0

0

Standy/Read-only because it's the log shipping target.

Reinis

RE: Restore Log takes many hours to fail

February 12, 2013, 5:52 am

≫ Next: RE: Restore Log takes many hours to fail

≪ Previous: RE: Restore Log takes many hours to fail

$

0

0

Could you please post the contents of the SQL Backup log file for the restore process that failed? The default folder where the logs are stored is C:\Documents and Settings\All Users\Application Data\Red Gate\SQL Backup\Log\<instance name> on Windows 2003 and older, and C:\ProgramData\Red Gate\SQL Backup\Log\<instance name> on Windows Vista and newer.

RE: Restore Log takes many hours to fail

February 12, 2013, 10:31 am

≫ Next: RE: Using 'master..sqlbackup' to do virtual restore

≪ Previous: RE: Restore Log takes many hours to fail

$

0

0

Here is the log. The names have been changed to protect the innocent. javascript:emoticon('') Failed_LS is the target database for the restore, and server2 is the Windows Server 2003 the instance is on.

I included only a partial list of the connections that were listed because I didn't want to go through changing all of them. There are a number that are shown as connected to the database we are trying to restore to but immediately before i start the restore I kill all the connections to that database. The connections listed for the restore DB are therefore created in the intervening 6 hours that the restore is failing - i checked the last batch time for all of them.

If you can figure out why it seems the restore still does not work despite the disconnect_existing, and my kill spids routine that would be a bonus. I've also tried having a trigger on the database to disallow any connections for 5 mins around the time the restore starts and that didn't work either.

Reinis

------------------------------------------------------------------------------
SQL Backup log file 6.5.1.9

-SQL "RESTORE LOG [Failed_LS] FROM DISK = '\\server2\Failed_LS_Share\LOG_Failed_*.sqb' WITH ERASEFILES = 5, DISCONNECT_EXISTING, FILEOPTIONS = 1, STANDBY = 'I:\Failed_LS\UNDO_Failed_LS.dat', MOVETO = 'J:\Failed_LS\Completed' "

----------------------------- ERRORS AND WARNINGS -----------------------------


2/10/2013 9:30:00 PM: Restoring Failed_LS (transaction logs) from:
2/10/2013 9:30:00 PM: \\server2\Failed_LS_Share\LOG_Failed_20130209220000.sqb

2/10/2013 9:30:04 PM: ALTER DATABASE [Failed_LS] SET ONLINE RESTORE LOG [Failed_LS] FROM VIRTUAL_DEVICE = 'SQLBACKUP_FF135A4B-697A-4263-B702-0A2FFFF8AEEA', VIRTUAL_DEVICE = 'SQLBACKUP_FF135A4B-697A-4263-B702-0A2FFFF8AEEA01', VIRTUAL_DEVICE = 'SQLBACKUP_FF135A4B-697A-4263-B702-0A2FFFF8AEEA02', VIRTUAL_DEVICE = 'SQLBACKUP_FF135A4B-697A-4263-B702-0A2FFFF8AEEA03', VIRTUAL_DEVICE = 'SQLBACKUP_FF135A4B-697A-4263-B702-0A2FFFF8AEEA04', VIRTUAL_DEVICE = 'SQLBACKUP_FF135A4B-697A-4263-B702-0A2FFFF8AEEA05', VIRTUAL_DEVICE = 'SQLBACKUP_FF135A4B-697A-4263-B702-0A2FFFF8AEEA06' WITH BUFFERCOUNT = 28, BLOCKSIZE = 65536, MAXTRANSFERSIZE = 1048576 , NORECOVERY

2/11/2013 4:19:40 AM: VDI error 1010: Failed to get the configuration from the server because the timeout interval has elapsed. Check that the SQL Server instance is running, that you have the SQL Server System Administrator server role; and that no other processes are blocking the backup or restore process; or try increasing the value of the VDITimeout registry setting in HKEY_LOCAL_MACHINE\SOFTWARE\Red Gate\SQL Backup\BackupSettingsGlobal\[InstanceName]
2/11/2013 4:19:40 AM: Also check that the database is not currently in use.
2/11/2013 4:19:40 AM:
2/11/2013 4:19:40 AM: SPID Status Login HostName BlkBy DBName Command CPUTime DiskIO LastBatch ProgramName SPID_1 REQUESTID
2/11/2013 4:19:40 AM: ----- ------------------------------ -------------------------------------------------------- ---------- ----- ---------------- ---------------- ------- -------- -------------- ------------------------------------------------------------------------- ------ ---------
2/11/2013 4:19:40 AM: 1 BACKGROUND sa . . RESOURCE MONITOR 1257406 26548 01/25 14:46:54 1 0
2/11/2013 4:19:40 AM: 2 SUSPENDED sa . . LOG WRITER 2825296 0 01/25 14:46:54 2 0
2/11/2013 4:19:40 AM: 3 BACKGROUND sa . . master SIGNAL HANDLER 0 0 01/25 14:46:54 3 0
2/11/2013 4:19:40 AM: 4 BACKGROUND sa . . LOCK MONITOR 31 0 01/25 14:46:54 4 0
2/11/2013 4:19:40 AM: 5 BACKGROUND sa . . LAZY WRITER 1626859 0 01/25 14:46:54 5 0
2/11/2013 4:19:40 AM: 6 sleeping sa . . master TASK MANAGER 0 0 01/25 14:46:54 6 0
2/11/2013 4:19:40 AM: 7 BACKGROUND sa . . master TRACE QUEUE TASK 11765 0 01/25 14:46:54 7 0
2/11/2013 4:19:40 AM: 8 sleeping sa . . UNKNOWN TOKEN 0 0 01/25 14:46:54 8 0
2/11/2013 4:19:40 AM: 9 BACKGROUND sa . . master BRKR TASK 0 0 01/25 14:46:54 9 0
2/11/2013 4:19:40 AM: 10 BACKGROUND sa . . master CHECKPOINT 2473062 97776 01/25 14:46:54 10 0
2/11/2013 4:19:40 AM: 11 BACKGROUND sa . . master TASK MANAGER 125 38 01/25 14:46:54 11 0
2/11/2013 4:19:40 AM: 12 BACKGROUND sa . . master BRKR EVENT HNDLR 15 39 01/25 14:46:54 12 0
2/11/2013 4:19:40 AM: 13 BACKGROUND sa . . master BRKR TASK 0 0 01/25 14:46:54 13 0
2/11/2013 4:19:40 AM: 14 sleeping sa . . master TASK MANAGER 0 3 01/25 14:46:54 14 0
2/11/2013 4:19:40 AM: 15 sleeping sa . . master TASK MANAGER 0 0 01/25 14:46:54 15 0
2/11/2013 4:19:40 AM: 16 sleeping sa . . master TASK MANAGER 0 114 01/25 14:46:54 16 0
2/11/2013 4:19:40 AM: 17 sleeping sa . . master TASK MANAGER 0 0 01/25 14:46:54 17 0
2/11/2013 4:19:40 AM: 18 sleeping sa . . master TASK MANAGER 0 0 01/25 14:46:54 18 0
2/11/2013 4:19:40 AM: 19 sleeping sa . . master TASK MANAGER 0 29 01/25 14:46:54 19 0

.....................................................

2/11/2013 4:19:40 AM:
2/11/2013 4:19:40 AM: SQL error 3013: RESTORE LOG is terminating abnormally.
2/11/2013 4:19:40 AM: SQL error 3101: Exclusive access could not be obtained because the database is in use.

RE: Using 'master..sqlbackup' to do virtual restore

February 12, 2013, 3:42 pm

≫ Next: RE: Restore Log takes many hours to fail

≪ Previous: RE: Restore Log takes many hours to fail

$

0

0

Does this question have to now be raised in a different forum?

RE: Restore Log takes many hours to fail

February 12, 2013, 7:02 pm

≫ Next: RE: Restore Log takes many hours to fail

≪ Previous: RE: Using 'master..sqlbackup' to do virtual restore

$

0

0

By default, SQL Backup would only wait 30 seconds for SQL Server to start the restore, before it aborts the process. In this case, it waited almost 7 hours. What is the VDITimeout value in the HKEY_LOCAL_MACHINE\SOFTWARE\Red Gate\SQL Backup\BackupSettingsGlobal\[InstanceName] registry node?

RE: Restore Log takes many hours to fail

February 12, 2013, 9:02 pm

≫ Next: RE: Using 'master..sqlbackup' to do virtual restore

≪ Previous: RE: Restore Log takes many hours to fail

$

0

0

The value is 24576 which would be 6.8 hours (I assume that is in seconds) so it seems to make sense. I have no idea why that would be set to such a high value. I switched it to 30 so we'll see what happens with that.

Thanks,

Reinis

---

RE: Using 'master..sqlbackup' to do virtual restore

February 13, 2013, 9:32 pm

≫ Next: Tran Log backups on FusionIO cards are 6 times larger

≪ Previous: RE: Restore Log takes many hours to fail

$

0

0

Thanks for your forum post. This does not need to be raised in a new post.

The TSQL script that you have generated using the wizard is the correct one and should work fine for that specific backup. To dynamically generate the TSQL depending on the backup will require using variables to substitute the relevant values. Unfortunately we haven't written any TSQL that can do this at the moment.

Please note this will need to be customised in your environment and depending on the number of threads, database structure the 'move syntax' will change as well.

Thanks for your patience and feedback in this matter.

Tran Log backups on FusionIO cards are 6 times larger

February 14, 2013, 11:30 am

≫ Next: RE: Tran Log backups on FusionIO cards are 6 times larger

≪ Previous: RE: Using 'master..sqlbackup' to do virtual restore

$

0

0

We added FusionIO cards to a database server. HP recommends changing the sector size from 512 to 4096 for SQL Server. We did that and moved our log files from DASD to the FusionIO cards. The backups are now 6 times larger but the database activity has not changed.

Has anyone else experienced this?

RE: Tran Log backups on FusionIO cards are 6 times larger

February 15, 2013, 3:55 am

≫ Next: RE: Tran Log backups on FusionIO cards are 6 times larger

≪ Previous: Tran Log backups on FusionIO cards are 6 times larger

$

0

0

Could you please post the contents of a SQL Backup log file for the backup of a transaction log that grew in size?

The default folder where the logs are stored is C:\Documents and Settings\All Users\Application Data\Red Gate\SQL Backup\Log\<instance name> on Windows 2003 and older, and C:\ProgramData\Red Gate\SQL Backup\Log\<instance name> on Windows Vista and newer.

Could you also please post the contents of a log file for a transaction log backup prior to the switch to FusionIO?

Thanks.

RE: Tran Log backups on FusionIO cards are 6 times larger

February 15, 2013, 2:22 pm

≫ Next: Backup stuck in KILLED/ROLLBACK

≪ Previous: RE: Tran Log backups on FusionIO cards are 6 times larger

$

0

0

You might want to look at this KB http://support.microsoft.com/kb/926930
You didn't mention what version of SQL or O/S you were running?

HTH

Chris

Backup stuck in KILLED/ROLLBACK

February 18, 2013, 7:41 am

≫ Next: Redgate Backup - Won't Delete All Files Before Backing Up

≪ Previous: RE: Tran Log backups on FusionIO cards are 6 times larger

$

0

0

Do failed backups require rollback?
Are multiple instances of process "SQBCoreService.exe " normal?

One of our production servers was experiencing memory pressure which required intervention. The memory pressure was caused from SQL utilizing 31GB of 32GB when max memory was set to 28GB. (No other memory heavy programs/processes run from this box)

I stopped the sql agent service.
I stopped SQL Backup service. (redgate)
Multiple backups were hung for over 3 hours. 2 FULL backups and 2 LOG backups.
An attempt to kill the proccesses inside SQL resulted in a KILLED/ROLLBACK status for all 4 processes.

Further investigation found multiple instances of process "SQBCoreService.exe "

All other production servers (even during multiple backups) have only 1 instance of process "SQBCoreService.exe "

Do failed backups require rollback?
Are multiple instances of process "SQBCoreService.exe " normal?

Redgate Backup - Won't Delete All Files Before Backing Up

February 18, 2013, 11:24 am

≫ Next: RE: Backup stuck in KILLED/ROLLBACK

≪ Previous: Backup stuck in KILLED/ROLLBACK

$

0

0

I am running backups to a location with limited storage. Because these backups aren't exactly critical, I only need one backup file. I am setting the program to run and delete existing backup files except for the latest "1" and also with "delete prior to start of backup" enabled. However, when I run this, it keeps the last backup and causing space issues on the drive. How can I change the program to delete all backup files before the program runs? Can i change the step in the job within sql and set it to 0b instead of 1b?

Thanks

RE: Backup stuck in KILLED/ROLLBACK

February 18, 2013, 11:53 am

≫ Next: RE: Redgate Backup - Won't Delete All Files Before Backing Up

≪ Previous: Redgate Backup - Won't Delete All Files Before Backing Up

$

0

0

I contacted support for this issue and we were unable to rectify the issue. I don't believe the underlying issue was caused by Redgate software. I will be reviewing the cause for the memory 'explosion'.

We have scheduled an emergency server reboot this evening.

I did learn that 1 process =SQBCoreService.exe is expected per SQL instance on the box. We only have a single instance, so 4 was abnormal, but no investigation was possible.

Support also shared this ...unfortunately for my scenario it requires that SQL Backup Agent service be operational.

Code:

Thanks for your call - to try and get the crash-log, do the following: USE master GO EXECUTE master..sqbutility 9997 GO

---

RE: Redgate Backup - Won't Delete All Files Before Backing Up

February 18, 2013, 11:56 am

≫ Next: RE: Redgate Backup - Won't Delete All Files Before Backing Up

≪ Previous: RE: Backup stuck in KILLED/ROLLBACK

$

0

0

I think you will get more assistance if you provide the code you are currently running.
You can adjust database/server names for confidentiality.

I know we had an issue with this some time back, but in recent versions no problems.

Be sure to pay attention to any TAPE backup that may be picking up(locking) the previously created file.
You should be able to rename the file as a test to see if it is locked.

RE: Redgate Backup - Won't Delete All Files Before Backing Up

February 18, 2013, 1:46 pm

≫ Next: RE: Redgate Backup - Won't Delete All Files Before Backing Up

≪ Previous: RE: Redgate Backup - Won't Delete All Files Before Backing Up

$

0

0

Sure, below is the code,

DECLARE @exitcode int
DECLARE @sqlerrorcode int
EXECUTE master..sqlbackup '-SQL "BACKUP DATABASES [DB1,DB2,DB3] TO DISK = ''C:\Backup\Full\<database>\<AUTO>.sqb'' WITH ERASEFILES_ATSTART = 1b, PASSWORD = ''<ENCRYPTEDPASSWORD>xxxxxxxxxxx</ENCRYPTEDPASSWORD>'', CHECKSUM, DISKRETRYINTERVAL = 30, DISKRETRYCOUNT = 10, KEYSIZE = 256, THREADCOUNT = 23"', @exitcode OUT, @sqlerrorcode OUT
IF (@exitcode >= 500) OR (@sqlerrorcode <> 0)
BEGIN
RAISERROR ('SQL Backup failed with exit code: %d SQL error code: %d', 16, 1, @exitcode, @sqlerrorcode)
END




I also double checked and no tape backups are running or did run at the same time.

RE: Redgate Backup - Won't Delete All Files Before Backing Up

February 19, 2013, 7:30 am

≫ Next: RE: Redgate Backup - Won't Delete All Files Before Backing Up

≪ Previous: RE: Redgate Backup - Won't Delete All Files Before Backing Up

$

0

0

We use the erasefiles_atstart option with a value of 40h.
This assumes we are running a daily backup (every 24 hours) and wish to always have at least 1 complete backup available on disk.

If you wish to essentially overwrite the previous backup you can simply set this value to less than your expected backup schedule.

So if you are running a daily backup, try

Code:

erasefiles_atstart = 1h

RE: Redgate Backup - Won't Delete All Files Before Backing Up

February 19, 2013, 8:19 am

≫ Next: RE: Backup stuck in KILLED/ROLLBACK

≪ Previous: RE: Redgate Backup - Won't Delete All Files Before Backing Up

$

0

0

Thanks epetro, I thought of something like that too. It's not super clean but it should work for our office.

RE: Backup stuck in KILLED/ROLLBACK

February 19, 2013, 9:56 am

≫ Next: RE: Tran Log backups on FusionIO cards are 6 times larger

≪ Previous: RE: Redgate Backup - Won't Delete All Files Before Backing Up

$

0

0

Thanks for posting back the end result - and I'm glad you're up and running now!