Comments
Sort by recent activity
Hi,
After SQL Backup creates the job, it is just like any other job in SQL Server which has a SQL Backup command.
If the jobs were running correctly before your server was rebooted and no permissions has been changed ... then I will verify the following:
Go to 'SQL Server Management Studio' (SSMS/ Enterprise Manager). Under the 'Jobs', select the job and right click and select the 'Properties'. Under 'General' verify the 'Owner'. After your server is rebooted and the jobs have started failing ... verify the owner again and see if this is changed.
Thanks,
Priya / comments
Hi,
After SQL Backup creates the job, it is just like any other job in SQL Server which has a SQL Backup command.
If the jobs were running correctly before your server was rebooted and no permissio...
Thanks Anna-Mari and Alan for your feedback.
This is not supported in SQL Response Version 1. But we are right now working on SQL Response Version 2 and this feature is under strong consideration for V 2.0. For your reference, the enhancement number for this request is SSR-1336.
Regards,
Priya / comments
Thanks Anna-Mari and Alan for your feedback.
This is not supported in SQL Response Version 1. But we are right now working on SQL Response Version 2 and this feature is under strong consideration f...
Hi,
Thanks for your suggestion. All the three features which you have mentioned is under consideration. So hopefully you would see them in one of the future releases of SQL Backup soon.
Thanks,
Priya / comments
Hi,
Thanks for your suggestion. All the three features which you have mentioned is under consideration. So hopefully you would see them in one of the future releases of SQL Backup soon.
Thanks,
Priya
Hello,
I am glad to hear that! Though you can backup directly to the network but it is not considered good... as per the best practise for the reasons below:
• Network errors may occur during the backup process (for example, outages or data corruption).
• More resources are required than for a local backup. This can result in increased load on the SQL Server and increased duration for the backup.
• By depending on external network resources, backup performance becomes less predictable.
Ideally, you should backup locally and then use 'COPYTO' keywords to copy the backup file to network. You can read the help file and use the embedded help in the product itself to get more information. There are quite a few 'Notes & articles' as well as 'Knowledge base' articles which might be useful for you. Let us know if you have any specific questions and we would try our best to answer it.
Regards,
Priya / comments
Hello,
I am glad to hear that! Though you can backup directly to the network but it is not considered good... as per the best practise for the reasons below:
• Network errors may occur during th...
Hi,
Yes, you can backup/ restore directly over the network drive.
We also have a functionality where backups can be copied to the network drives after backing up locally.
Thanks,
Priya / comments
Hi,
Yes, you can backup/ restore directly over the network drive.
We also have a functionality where backups can be copied to the network drives after backing up locally.
Thanks,
Priya
Hi,
You can backup directly to network \\server\share without mapping it to drive letter.
SQL Backup has 14 days of free trial. You might want to try it on your own.
Thanks,
Priya / comments
Hi,
You can backup directly to network \\server\share without mapping it to drive letter.
SQL Backup has 14 days of free trial. You might want to try it on your own.
Thanks,
Priya
Hi,
You might be aware but I thought it is worth mentioning that in the last step of the Backup and Restore Wizard, you can view the scripts for 'Command Line' and 'Extended Stored Procedure' under the Script tabs. This might be useful for you.
Thanks,
Priya / comments
Hi,
You might be aware but I thought it is worth mentioning that in the last step of the Backup and Restore Wizard, you can view the scripts for 'Command Line' and 'Extended Stored Procedure' under...
Hi,
The command has a syntax error, it misses WITH. Try this SQLBackupC.exe -SQL "BACKUP DATABASES [*] TO
DISK = 'X:\<TYPE>_<SERVER>_<DATABASE>_<DATETIME yyyymmdd_hhnnss>.sqb'" WITH COMPRESSION = 2, ERASEFILES = 3
and let us know if it still doesn't work.
Thanks,
Priya / comments
Hi,
The command has a syntax error, it misses WITH. Try thisSQLBackupC.exe -SQL "BACKUP DATABASES [*] TO
DISK = 'X:\<TYPE>_<SERVER>_<DATABASE>_<DATETIME yyyymmdd_hhnn...
Its great to hear that it works fine for you now. We will investigate this scenario further in-house to verify why this happened.
Thanks,
Priya / comments
Its great to hear that it works fine for you now. We will investigate this scenario further in-house to verify why this happened.
Thanks,
Priya
Sorry Bill, I should have explained it more clearly.
SQL Backup has a client installation and then you install server components for each of the SQL Server instance. If you look at 'Add and Remove' program then you can see the server components installed separately for each of your SQL Server instance. You can find the server components installer in your client Install directory and it is named as SQBServerSetup.exe.
When you install server components for your SQL Server instance using SQBServerSetup.exe then you get an option to 'Select the authentication mode that the service application will use to log into SQL Server'. So this is the option which I meant you to change. It is independent of the set up which you have done in your Enterprise Manager or SQL Backup GUI.
So you have two options here now:
1. Either use sqbsetlogin as explained here http://www.red-gate.com/supportcenter/Content.aspx?p=SQL%20Backup&c=knowledgebase%5cSQL_Backup%5cKB200701000003.htm
Or
2. Go to your 'Add and Remove' Program and uninstall the server components for this instance. Run SQBServerSetup.exe again and then enter the correct password.
Hopefully this will resolve your problem. / comments
Sorry Bill, I should have explained it more clearly.
SQL Backup has a client installation and then you install server components for each of the SQL Server instance. If you look at 'Add and Remove'...