Comments
2 comments
-
We run many SQLBackup backup jobs at the same time as they get scheduled into SQL Agent. Remember each job needs 6Mb of contiguous VAS memory. Also get the latest 6.5.1.9 from the download page as it has a needed fix for large database restores.
Chris -
In production, we process each backup as part of that databases maintenance process. Many of these overlap in schedule. I have seen duration reductions when they are staggered.
In development and QA (20+ databases) I use the keyword "USER". This processes one after the other and works well with tags(<database>,<auto>). The only downside is a few errors have been hard to identify the source./*FULL BACKUP FOR ALL USERS*/ DECLARE @exitcode int DECLARE @sqlerrorcode int EXECUTE master..sqlbackup N'-SQL "BACKUP USER DATABASES TO DISK = ''k:\DatabaseBAK\<database>\<AUTO>.sqb'' WITH COMPRESSION = 4, ERASEFILES_ATSTART = 1h, THREADCOUNT = 7"', @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
Add comment
Please sign in to leave a comment.
I am asking can I run both of these at the same time.
EXECUTE master..sqlbackup '-SQL "BACKUP DATABASE [DB1]
TO DISK = ''D:\Backups\DB1_1.sqb'',
DISK = ''D:\Backups\DB1_2.sqb''
WITH ERASEFILES_ATSTART = 3h, DISKRETRYINTERVAL = 30, DISKRETRYCOUNT = 10, COMPRESSION = 2, INIT"'
GO
EXECUTE master..sqlbackup '-SQL "BACKUP DATABASE [DB2]
TO DISK = ''D:\Backups\DB2_1.sqb'',
DISK = ''D:\Backups\DB2_2.sqb''
WITH ERASEFILES_ATSTART = 3h, DISKRETRYINTERVAL = 30, DISKRETRYCOUNT = 10, COMPRESSION = 2, INIT"'
GO