Comments
Sort by recent activity
Could you please post the SQL Backup logs of a scheduled backup and an ad-hoc backup here for us to take a detailed look? Thanks. / comments
Could you please post the SQL Backup logs of a scheduled backup and an ad-hoc backup here for us to take a detailed look? Thanks.
If every other external factor is equal, one item that would affect backup speed from within SQL Backup is the compression level. Are you using the same compression levels in the scheduled backup and the ad-hoc backup? / comments
If every other external factor is equal, one item that would affect backup speed from within SQL Backup is the compression level. Are you using the same compression levels in the scheduled backup ...
One option may be to create serverB as a linked server on serverA, then set up the restore as a job step after the backup job step on serverA. / comments
One option may be to create serverB as a linked server on serverA, then set up the restore as a job step after the backup job step on serverA.
One option, using the SINGLERESULTSET option and a temporary table: IF OBJECT_ID('tempdb..#sqboutput') IS NOT NULL DROP TABLE #sqboutput CREATE TABLE #sqboutput (lines nvarchar(4000)) DECLARE @cmd nvarchar(1024) SET @cmd = 'master..sqlbackup ''-sql "RESTORE DATABASE ... WITH ..., SINGLERESULTSET"''' INSERT INTO #sqboutput EXEC sp_executesql @cmd SELECT * FROM #sqboutput DROP TABLE #sqboutput / comments
One option, using the SINGLERESULTSET option and a temporary table:IF OBJECT_ID('tempdb..#sqboutput') IS NOT NULL DROP TABLE #sqboutputCREATE TABLE #sqboutput (lines nvarchar(4000))DECLARE @cmd ...
This might help with regards to understanding the rights required (https://www.sqlbackuprestore.com/settinguprights.htm). Essentially, your SQL Server Agent job needs to have the same rights as a end-user - i.e. to run the SQL Backup extended stored procedures and rights to back up and restore the databases. / comments
This might help with regards to understanding the rights required (https://www.sqlbackuprestore.com/settinguprights.htm). Essentially, your SQL Server Agent job needs to have the same rights as a ...
Could you please post a screenshot of the SQL Backup screen where your database is shown in the 'Replication' section? Thank you. / comments
Could you please post a screenshot of the SQL Backup screen where your database is shown in the 'Replication' section? Thank you.
It is by design that the <CLUSTER> tag returns the server name if the database that is being backed up does not belong to an availability group. E.g. say for the msdb database (not part of an availability group) for both instances, it would be confusing if the backups of that database from both instances have the same name but are contextually different. While for availability groups, the databases are usually identical, and also users would have a preferred backup node, so it would make sense that the naming convention (using the <CLUSTER> tag) is identical from whichever node the backup is taken from. If you really want to use the cluster name as part of the file name, one option would be to hardcode the value in the naming convention instead of using the <CLUSTER> tag. / comments
It is by design that the <CLUSTER> tag returns the server name if the database that is being backed up does not belong to an availability group. E.g. say for the msdb database (not part of an avai...
Are the backup files password protected? If so, you need to enter the password in the area below the list of files, and click on the Decrypt button. / comments
Are the backup files password protected? If so, you need to enter the password in the area below the list of files, and click on the Decrypt button.
If you took a full backup of any database from the source using SQL Backup with the minimum of options e.g. EXEC master..sqlbackup '-sql "BACKUP DATABASE [database name] TO DISK = [backup file name]"' and restored this backup on the destination server, is the same error raised? If not, could you then try incrementally adding the other options used in the original backups until the restore fails? When that restore fails, could you please post the contents of the backup and restore logs? The default folder for the logs is C:\ProgramData\Red Gate\SQL Backup\Log\<instance name> / comments
If you took a full backup of any database from the source using SQL Backup with the minimum of options e.g.EXEC master..sqlbackup '-sql "BACKUP DATABASE [database name] TO DISK = [backup file name]...
Which SQL Server version were the backups taken from, and which version are they being restored to? / comments
Which SQL Server version were the backups taken from, and which version are they being restored to?