Comments
Sort by recent activity
SQL Backup 4 and 5 returns two integer values from the extended stored procedure, the first is the SQL Backup exit code, the second is the SQL Server error code.
When the SQL Backup statement is executed, you can extract them in the following way (where @var1 and @var2 are declared "int" variables):
execute master..sqlbackup '-SQL "BACKUP DATABASE [master] TO DISK = ''c:\temp\master.sqb'' WITH INIT"', @var1 OUTPUT, @var2 OUTPUT
If you wanted to use this with temporary tables, the definition you would need would be something like the following:
CREATE TABLE #temp (sqbexitcode int, sqlservercode int);
Unfortunately there is no easy/trivial way to capture the textual output from the extended stored procedure in 4.x, 5.0 or 5.1... but we will be introducing a new function for this in 5.2 so that this information can also be captured easily.
Hope that helps,
Jason / comments
SQL Backup 4 and 5 returns two integer values from the extended stored procedure, the first is the SQL Backup exit code, the second is the SQL Server error code.
When the SQL Backup statement is ex...
Hi RB,
While SQL Backup doesn't offer explicit support for maintenance plans per-say, you can generate Transact-SQL code that can be inserted into the maintenance plans by hand.
The following is an example Transact-SQL statement that would compress the generated backup file (and automatically name it, for example with a timestamp):
execute master..sqlbackup '-SQL "BACKUP DATABASE [mydatabase] TO DISK = ''c:\backups\<auto>.sqb'' WITH COMPRESSION = 2"';
Alternatively, you can use the Scheduling Wizard in the SQL Backup 5 user interface to generate SQL Server Agent jobs that can perform the backups - which will offer much the same functionality as maintenance plans will.
If you need any more information or specifics, let us know.
Hope that helps,
Jason / comments
Hi RB,
While SQL Backup doesn't offer explicit support for maintenance plans per-say, you can generate Transact-SQL code that can be inserted into the maintenance plans by hand.
The following is an...
Hi NewDBAGirl,
You may need to click "Tools" at the top of the explorer window, and select "Folder Options". On the "View" tab, make sure the "Show Hidden Files and Folders" option is selected.
You should then see the "Application Data" folder appear.
If you need any more help finding the log files, let me know.
Jason / comments
Hi NewDBAGirl,
You may need to click "Tools" at the top of the explorer window, and select "Folder Options". On the "View" tab, make sure the "Show Hidden Files and Folders" option is selected.
Yo...
Hi flyfish,
You appear to have two issues with your log shipping configuration.
The first is the SQL Server Error (4326), which relates to log backups being out of sequence.
If you look in your SQL Backup logging directory (by default, this is at c:\documents and settings\all users\application data\red gate\sql backup\log\<instance name>), you should find a timestamped log that corresponds to the restore in question.
This log should give you information on what was wrong with the restore, and you can find which files in your "backups" directory you need to copy to the network share (or need to move from the network share to the "processed" directory). The log shipping should then start functioning correctly.
The second issue you appear to have is the SQL Backup Warning 150, which is because you haven't configured a SMTP mail server in the SQL Backup 4.6 User Interface.
If you open the "Options" dialog, and select the SQL Server instance(s) you are working with, you can enter a SMTP mail server, and this particular warning should then go away.
Ideally you should be entering an SMTP server name on both the SQL Server instances used for log shipping.
If you need any more information or detailed help with your question, feel free to follow-up on the forum or drop me an email.
Hope that helps,
Jason / comments
Hi flyfish,
You appear to have two issues with your log shipping configuration.
The first is the SQL Server Error (4326), which relates to log backups being out of sequence.
If you look in your SQL...
When installing the SQL Backup 5 server components, you need to install from the active host (i.e. the physical hardware) - nothing needs to be installed to the virtual cluster or clustered sql server... SQL Backup will handle that part of it.
When upgrading, the steps are much the same as for an install - the only difference is that some of the steps may be skipped in the installer (for example, you may not be asked for service credentials or windows/sql authentication details again).
While the upgrade should go smoothly, if the components are not upgraded on the second node, copying the installer to the second node and running the installer by hand (as a clustered install) will resolve the problem. No additional action is required to "synchronise" the two upgrades.
Hope that helps,
Jason / comments
When installing the SQL Backup 5 server components, you need to install from the active host (i.e. the physical hardware) - nothing needs to be installed to the virtual cluster or clustered sql ser...
The version 5 installer for the server components is cluster aware by design, so should perform all of the necessary steps covered in the v4 clustering document.
The installer must be run from the active node, and you must select the clustered installation option when prompted.
If this installs correctly the components will also be installed on the passive node(s), as well as all the clustering resources being set up automatically.
If the installer warns that it could not install the components on the passive node, you can run the installer on the passive node (again as a clustered installation) and it should fill in anything that could not be performed from the active node.
To upgrade the server components to 5.1, just run the updated installer from the active node, fill in the details required for the clustered installation, and you should be good to go.
If you need more specific information or help on the above, feel free to follow-up on the forum, or drop me an email.
Thanks,
Jason / comments
The version 5 installer for the server components is cluster aware by design, so should perform all of the necessary steps covered in the v4 clustering document.
The installer must be run from the ...
Regarding your updated comment - As long as the SQL Backup Agent exists as a clustered resource, and both nodes return the same version number for the server components, then you've completed the upgrade successfully.
As for the dependencies [SQL Server and Disk; SQL Server Agent if using SQL Backup Jobs], this is a known issue with the 5.x installer. I have previously mentioned this to the developers and I hope that it will be included in a future release - but unfortunately I do not have any additional information on when that may be.
Jason / comments
Regarding your updated comment - As long as the SQL Backup Agent exists as a clustered resource, and both nodes return the same version number for the server components, then you've completed the u...
If you contact our support team ( can email them at support@red-gate.com ) they can help you with this.
Thanks,
Jason / comments
If you contact our support team ( can email them at support@red-gate.com ) they can help you with this.
Thanks,
Jason
The trial download from the website ( http://www.red-gate.com/products/SQL_Backup/index.htm ) is the same as the update available from the "check for updates" menu.
Once you have downloaded the file from the website and installed it, you may need to reactivate the server components (right click the server name in the user interface and activate from there, or use the ProductActivation.exe program) - but apart from that you should be good to go.
Hope that helps,
Jason / comments
The trial download from the website ( http://www.red-gate.com/products/SQL_Backup/index.htm ) is the same as the update available from the "check for updates" menu.
Once you have downloaded the fil...
Unfortunately the version listed on the prerequisities webpage is still the 5.0 version. There are two ways you can get hold of the 5.1 version:
* Install the 5.1 version of SQL Backup, and then you can copy the sqb2mtf.exe file;
* Alternatively, you can drop me an email (jason.cook@red-gate.com) and I'll send you the 5.1 version.
Jason / comments
Unfortunately the version listed on the prerequisities webpage is still the 5.0 version. There are two ways you can get hold of the 5.1 version:
* Install the 5.1 version of SQL Backup, and then y...