Comments
Sort by recent activity
Just for further clarification, DURING the backup process, SQL Backup does not create any temporary files anywhere on the system. All compression/encryption is done in-memory and written to the backup file(s) directly. There are no 'work' files or 'temporary' files used to store any data prior to being written out to the backup file(s). This also applies for backups to network shares. However, if you were backing up to a local share and then using the COPYTO option to copy to a network share, then yes, you would need space to hold the backup file(s) locally first, as Mac mentioned above. / comments
Just for further clarification, DURING the backup process, SQL Backup does not create any temporary files anywhere on the system. All compression/encryption is done in-memory and written to the ba...
You would need to stagger them. The SQL Backup engine is a 32-bit application, and it can only access up to 1.4 GB of memory realistically. Running 40 restores simultaneously will easily use up the memory it can access. There is then also the CPU and storage device limitations keeping up with 40 simultaneous restores. / comments
You would need to stagger them. The SQL Backup engine is a 32-bit application, and it can only access up to 1.4 GB of memory realistically. Running 40 restores simultaneously will easily use up t...
There isn't an option in SQL Backup to restore a series of databases automatically, unlike backups. Each restore process will only restore a single database. / comments
There isn't an option in SQL Backup to restore a series of databases automatically, unlike backups. Each restore process will only restore a single database.
In the folder where the SQL Backup Agent executable (SQBCoreService.exe) is installed in, you should find the hosted storage upload executable file (SQBHostedStorageClient.exe), and 2 Amazon client libraries (AWSSDK.Core.DLL and AWSSDK.S3.dll). Could you please check if the version numbers of those files are consistent across your servers? Also, do you have .Net 4.5 installed on the servers where the upload fails? / comments
In the folder where the SQL Backup Agent executable (SQBCoreService.exe) is installed in, you should find the hosted storage upload executable file (SQBHostedStorageClient.exe), and 2 Amazon client...
In the restore job, before the job step that runs the SQL Backup restore command, try adding a job step to forcibly kill all connections to the database in question. You could use something like this: USE master DECLARE @execSql varchar(1000), @databaseName varchar(100) -- Set the database name for which to kill the connections SET @databaseName = '<your database name>' SET @execSql = '' SELECT @execSql = @execSql + 'kill ' + convert(char(10), spid) + ' ' FROM master.dbo.sysprocesses WHERE db_name(dbid) = @databaseName AND DBID <> 0 AND @spid EXEC (@execSql) / comments
In the restore job, before the job step that runs the SQL Backup restore command, try adding a job step to forcibly kill all connections to the database in question. You could use something like t...
If you can restore the backups taken by Azure Site Recovery (ASR) into a non-recovery state, can you restore the transaction log backups taken by SQL Backup? The ASR shouldn't 'invalidate' the SQL Backup backups, just that you can't use the GUI to restore backups taken by ASR. / comments
If you can restore the backups taken by Azure Site Recovery (ASR) into a non-recovery state, can you restore the transaction log backups taken by SQL Backup? The ASR shouldn't 'invalidate' the SQL...
1. True. 2. The encryption uses a combination of SHA256 and AES for hasing/deriving the password. Password length and characters shouldn't matter, though the longer the password, the harder it'll be to crack. If you plan on using special characters in the password, would suggest testing a backup and restore using them first. 3. Yes. This is intentional, to remind the user that you need to secure the SQL instance. Even if we encrypted the password, anybody with access to the script can just use the same script with the encrypted password to restore the database, without actually knowing the actual password. / comments
1. True.2. The encryption uses a combination of SHA256 and AES for hasing/deriving the password. Password length and characters shouldn't matter, though the longer the password, the harder it'll...
SQL Backup keeps a list of files it needs to copy in the backupfiles_copylist table, stored in a SQL Server Compact database. In order to stop it from repeatedly attempting to copy the file, you need to set the file's status to expired (E) e.g. EXEC master..sqbdata 'UPDATE backupfiles_copylist SET status = ''E'' WHERE name = ''<the backup file name>'' ' / comments
SQL Backup keeps a list of files it needs to copy in the backupfiles_copylist table, stored in a SQL Server Compact database. In order to stop it from repeatedly attempting to copy the file, you n...
The error message indicates that the transaction logs are being restored out of sequence. You need to determine if the earlier transaction log backup file does exist in the folder where SQL Backup is restoring from, and if so, why SQL Backup is not picking up that file to restore. It could be something like the earlier transaction log backup having a password, while the later ones do not, and the restore command now does not provide a password. Or a situation where SQL Backup failed to fill in the backup details for that earlier backup, causing SQL Backup not to be able to identify that backup set correctly. If you cannot find the required file, then it could be that the SQL Backup service on the backup server failed to copy the file over (if you were using the COPYTO option), or a transaction log backup was made outside of SQL Backup, in which case you'll need to track down that file using details from the msdb..backupset and msdb..backupmediafamily tables on the backup instance. / comments
The error message indicates that the transaction logs are being restored out of sequence. You need to determine if the earlier transaction log backup file does exist in the folder where SQL Backup...
Yes, you still need to make the changes in the registry. / comments
Yes, you still need to make the changes in the registry.