SQL Backup Agent has stopped.
- Click Start, click in the search box, type services.msc, and then press ENTER.
- Find service "SQL Backup Agent" and open
- Click "Start"
When SQL Backup writes out compressed backup data to disk, it does so in 2 MB blocks. If the backups are saved to a network drive, the network may be having difficulty transporting blocks of this size. A solution is to reduce the size of each block:
- Append MAXDATABLOCK = 524288 to the backup command.
This can be done in increments of 64 Kb:
- 262144 (256 Kb)
- 524288 (512 Kb)
- 1048576 (1 MB)
Example:
EXECUTE master..sqlbackup '-SQL "BACKUP LOGS [database] TO DISK = ''C:\Backup\Log\<AUTO>.sqb'' WITH MAXDATABLOCK = 524288, ERASEFILES_ATSTART = 25b, DISKRETRYINTERVAL = 30, DISKRETRYCOUNT = 10, COMPRESSION = 3, INIT, THREADCOUNT = 4"', @exitcode OUT, @sqlerrorcode OUT
END
Add SkipChecks
to registry HKEY_LOCAL MACHINE\Software\Red Gate\SQL Backup\BackupSettingsGlobal\(LOCAL)
or <SQL Instance Name>
with a 32-bit DWORD
decimal value of 1
VDI error 1010: Failed to get the configuration from the server because the timeout interval has elapsed.
Update VDITimeout
in registry HKEY_LOCAL MACHINE\Software\Red Gate\SQL Backup\BackupSettingsGlobal\(LOCAL)
or <SQL Instance Name>
with an increased decimal value
SQL Backup could not access [HKEY_LOCAL_MACHINE\SOFTWARE\Red Gate\SQL Backup\BackupSettingsGlobal(LOCAL)] running as user
Set "Full Control" permissions for backup service user on above registry location.