Comments
Sort by recent activity
SQL Backup 6 can be used to restore all backup files created by prior versions of SQL Backup.
Could you please try to restore the backup file using the extended stored procedure e.g. EXEC master..sqlbackup '-sql "RESTORE DATABASE ... FROM DISK = ... WITH NORECOVERY" '
and let me know if it works?
Thanks. / comments
SQL Backup 6 can be used to restore all backup files created by prior versions of SQL Backup.
Could you please try to restore the backup file using the extended stored procedure e.g.EXEC master..sq...
If you can reproduce this issue consistently after the first backup, you can try the following.
- determine if it happens for all databases, or just that particular database
- determine the system component that's causing the slow throughput. See this help topic for details. Basically, you need to run backups using the NOCOMPRESSWRITE and NOWRITE options on the affected database(s) and record the numbers. You should be able to determine if it's the disk read I/O, CPU or disk write I/O, or a combination of those components, that's the bottleneck.
Thanks. / comments
If you can reproduce this issue consistently after the first backup, you can try the following.
- determine if it happens for all databases, or just that particular database
- determine the system ...
Itanium? SQL Backup has not been tested to run on that platform. / comments
Itanium? SQL Backup has not been tested to run on that platform.
You need to provide the plain text (non-encrypted) password in order to restore the database.
E.g. when you back up a database or set up a backup job using the GUI, it encrypts the password you entered so that anyone looking at the script will not know the plain-text password.
If SQL Backup allowed users to restore the database using the same encrypted value, it defeats the purpose of encrypting the password. Thus, you need to know the plain text password to restore the database. / comments
You need to provide the plain text (non-encrypted) password in order to restore the database.
E.g. when you back up a database or set up a backup job using the GUI, it encrypts the password you ent...
SQL Backup is fully backwards compatible, so you can restore backup files created with older versions of SQL Backup with all newer versions of SQL Backup.
Could you please run a small test for us:
- back up a small database e.g. model
EXEC master..sqlbackup '-sql "BACKUP DATABASE model TO DISK = [c:\model.sqb] WITH PASSWORD = [test]"'
- copy the file to the other server
- run and send us the output from the following commands on the other server:
EXEC master..sqlbackup '-sql "RESTORE HEADERONLY FROM DISK = [...] "'
EXEC master..sqlbackup '-sql "RESTORE HEADERONLY FROM DISK = [...] WITH PASSWORD = [test]"'
where [...] is the fully qualified name of the copied file.
Thank you. / comments
SQL Backup is fully backwards compatible, so you can restore backup files created with older versions of SQL Backup with all newer versions of SQL Backup.
Could you please run a small test for us:
...
You might want to try the suggestion here, which involves:
- setting up a new instance of SQL Server 2005
- restoring the backup to that instance
- upgrading that instance to SQL Server 2008
- backing up the msdb database on that instance
- restoring that backup on your target SQL Server 2008 instance / comments
You might want to try the suggestion here, which involves:
- setting up a new instance of SQL Server 2005
- restoring the backup to that instance
- upgrading that instance to SQL Server 2008
- back...
Thanks for the details. The problem lies with the database name. Restoring the latest backup sets from folders require the original and current database name to be identical i.e. AdventureWorks. The syntax for restoring from the backup history allows you to specify the original database name, but not when restoring from folders.
This is a known issue (SB-4445), and is under consideration for a fix in a future release. / comments
Thanks for the details. The problem lies with the database name. Restoring the latest backup sets from folders require the original and current database name to be identical i.e. AdventureWorks. ...
What was the command you used, that did not work?
Thanks. / comments
What was the command you used, that did not work?
Thanks.
fatherjack wrote:
Nice call Jerry,
automated restores are something that I would love to see integrated into SQLBackup and being able to use these would be a good move towards it.
Jonathan
The recently released version 6.3 goes some way towards achieving this. The following syntax: EXEC master..sqlbackup '-sql "RESTORE DATABASE AdventureWorks FROM BACKUPHISTORY LATEST_FULL"'
will cause SQL Backup to look in its backup history records and simply restore the latest full backup that it finds. You can also use LATEST_DIFF to restore the latest differential backup, but the state of your database obviously needs to be in a non-recovery/read-only state, and is the correct base backup for the latest differential restore.
Another point to note is that RESTORE ... FROM BACKUPHISTORY only works if you are restoring on the server instance where the backup was created, since that is where the backup history records reside. If you are restoring on another server instance, you can use the following: EXEC master..sqlbackup '-sql "RESTORE DATABASE AdventureWorks FROM DISK = [g:\backups\AdventureWorks*] LATEST_FULL"'
will cause SQL Backup to find all files matching the AdventureWorks* search pattern in the g:\backups\ folder, determine the latest complete full backup set that's available, and restore it. Again, LATEST_DIFF is also available here.
One last point is that all the other restore options can still be used with the above syntax e.g. MOVE, NORECOVERY, STANDBY etc.
Thanks. / comments
fatherjack wrote:
Nice call Jerry,
automated restores are something that I would love to see integrated into SQLBackup and being able to use these would be a good move towards it.
Jonathan
The...
By default, SQL Backup only uses 1 backup device. It only uses multiple backup devices when the THREADCOUNT option is explicitly used, or when multiple DISK options are used.
So if your original script does not use the THREADCOUNT option, nor multiple DISK options, then it will not automatically use multiple backup devices regardless of the version of SQL Backup that is used.
Thanks. / comments
By default, SQL Backup only uses 1 backup device. It only uses multiple backup devices when the THREADCOUNT option is explicitly used, or when multiple DISK options are used.
So if your original s...