- RSS Channel Showcase 3451702
- RSS Channel Showcase 9917365
- RSS Channel Showcase 6008416
- RSS Channel Showcase 9827365
Articles on this Page
- 04/19/13--07:45: _RE: Issue with 7.3
- 04/21/13--03:49: _RE: Restore Append ...
- 04/23/13--10:56: _Backup taking TOO l...
- 04/24/13--18:35: _RE: SQL Backup 22.214.171.124
- 04/24/13--23:07: _RE: Backup taking T...
- 04/25/13--03:03: _configure restore r...
- 04/25/13--05:35: _Installation on Win...
- 04/25/13--06:04: _RE: Installation on...
- 04/25/13--06:06: _RE: Backup taking T...
- 04/25/13--09:34: _RE: Backup taking T...
- 04/25/13--17:34: _RE: Use of file loc...
- 04/26/13--05:58: _RE: Use of file loc...
- 04/26/13--07:02: _MindShare Media | 8...
- 04/26/13--09:23: _RE: configure resto...
- 04/18/13--09:22: _RE: Issue with 7.3
- 05/03/13--15:03: _How to backup??
- 05/06/13--03:18: _RE: How to backup??
- 05/08/13--15:09: _How to generate rep...
- 05/10/13--01:59: _RE: How to generate...
- 05/10/13--02:37: _SQL Backup 126.96.36.199
- 04/19/13--07:45: RE: Issue with 7.3
- 04/21/13--03:49: RE: Restore Append instead of Restore Replace?
- 04/23/13--10:56: Backup taking TOO long after migration from SQL 2005 to SQL
- 04/24/13--18:35: RE: SQL Backup 188.8.131.52
- 04/24/13--23:07: RE: Backup taking TOO long after migration from SQL 2005 to SQL
- 04/25/13--03:03: configure restore retry
- 04/25/13--05:35: Installation on Windows 2012 Cluster - Registry replication
- 04/25/13--06:04: RE: Installation on Windows 2012 Cluster - Registry replication
- 04/25/13--06:06: RE: Backup taking TOO long after migration from SQL 2005 to SQL
- 04/25/13--09:34: RE: Backup taking TOO long after migration from SQL 2005 to SQL
- 04/25/13--17:34: RE: Use of file location tags in "Copy backup to network locatio
- 04/26/13--05:58: RE: Use of file location tags in "Copy backup to network locatio
- 04/26/13--07:02: MindShare Media | 866-307-0902 - 2X Business Income Within 1
- 04/26/13--09:23: RE: configure restore retry
- 04/18/13--09:22: RE: Issue with 7.3
- 05/03/13--15:03: How to backup??
- 05/06/13--03:18: RE: How to backup??
- 05/08/13--15:09: How to generate report on database restore durations
- 05/10/13--01:59: RE: How to generate report on database restore durations
- 05/10/13--02:37: SQL Backup 184.108.40.206
Sorry. Did not check back on the thread until today.
Thanks, installed and it seems to fix the issue for me. No more green spinning thing on server or restore button
Once a SQL Server database is online then there is no option to append additional data changes from a backup to that 'online' database.
Having said that there is one way you could try to apply more changes to that database. To do this you will have to take this database offline by changing its state to 'norecovery' (using restore database with 'norecovery' option). After this you can apply further backups to this same database. Now the backups that 'could' be applied will need to have the correct LSN sequence (so if the next backup was was a FULL then that will need to be applied, if it was a DIFF then that will need to be applied etc).
I hope this helps in your situation.
We just migrated our databases from SQL 2005 to 2008 R2. It's on Active Passive cluster with a shiny new hardware. It used to take 30 minutes to backup 500 GB database on old crappy hardware. Now it takes over 6 hours and takes too much resources too. Checked everything but looks like hardware is not an issue at all.
Any immediate suggestions? Thanks in advance.
After upgrading both the client and Server components to 220.127.116.11, the history comes up blazingly fast. It's been turbo charged.
Could you please send me the SQL Backup log for a backup that was made on the SQL 2005 instance, and another log for a backup that was made for the migrated database on the SQL 2008 R2 instance?
The default folder where the logs are stored is C:\Documents and Settings\All Users\Application Data\Red Gate\SQL Backup\Log\<instance name> on Windows 2003 and older, and C:\ProgramData\Red Gate\SQL Backup\Log\<instance name> on Windows Vista and newer.
Please send the files to email@example.com.
SQL Backup has already a out of the box retry feature on restoring a database. Apparently is configured to retry 10 times every 30 seconds.
Could I configure somewhere these values for restoring a database? I know for backup it is already possible via the GUI and command line. Do I have the same possibility for the restore command?
We are installing SQL Backup 7 on a Windows Server 2012/SQL Server 2012 cluster and are following the manual installation method, which is working fine except for the part where the cluster resource for the service must be configured.
It seems Microsoft dropped the ball a bit in Windows 2012 and forgot to include the tab for setting up registry replication in cluster manager for generic services (oops!) and since the cluster.exe tool is no longer included either, we have to resort to using Powershell cluster cmdlets to set up the registry replication, according to a Technet article we found: http://social.technet.microsoft.com/Forums/en-US/winserverClustering/thread/dd71da37-ccac-468a-bb03-fb81dc88d290/
Would you happen to have any examples/templates for this on hand that we can use to get it set up correctly for the SQL Backup agent service?
With some more help from Technet (http://technet.microsoft.com/en-us/library/hh847255.aspx) I found the following seems to work:
Add-ClusterCheckpoint -ResourceName "SQL Backup Agent-<INSTANCE>" -RegistryCheckpoint "SOFTWARE\Red Gate\SQL Backup\BackupSettings\<INSTANCE>"
Add-ClusterCheckpoint -ResourceName "SQL Backup Agent-<INSTANCE>" -RegistryCheckpoint "SOFTWARE\Red Gate\SQL Backup\BackupSettingsGlobal\<INSTANCE>"
Emailed you the logs. Please let me know if you need more details.
Have you tried backing up the database using THREADCOUNT = 8, as you were previously doing on the SQL 2005 instance?
SQL Backup doesn't support multiple DATETIME tags. If you really do need this feature, you can download patch 18.104.22.168, that does support it. You can download it using the following URL:
To apply the patch, please follow the steps below:
1. Close all GUI connections to the SQL Server.
2. Ensure that no SQL Backup jobs are in progress.
3. Stop the SQL Backup Agent Service, or disable the cluster resource if on a cluster.
4. On the SQL Server where the SQL Backup server components are installed, navigate to the installation directory. Defaults are:
32-bit Machines - C:\Program Files\Red Gate\SQL Backup 6\(local) or <SQL Instance Name>
64-bit Machines - C:\Program Files (x86)\Red Gate\SQL Backup 6\(local) or <SQL Instance Name>
5. In the folder you will find an existing SQBCoreService.exe and SQL BackupC.exe. Rename the existing files, for example to OLDSQBCoreService.exe and OLDSQLBackupC.exe.
6. Now copy in the files extracted from the downloaded zip.
7. Restart the SQL Backup agent service/cluster resource, and ensure that it starts successfully.
8. Perform a test backup to ensure that all is OK. Then run a backup using multiple DATETIME tags via the extended stored procedure, to see if the the folders are generated correctly.
866-307-0902 | Double your business Online income within 1 year by combining SEO, Content Marketing, Social Media, Email Marketing and PR. Guaranteed results!
youtube video marketing
video marketing service
internet marketing consultants
mobile marketing company
search engine optimization seo
Unfortunately the tool does not currently have this capability
You can request features for this product in our uservoice forums
These forums are actively monitored by our development team and allow our users to request features and vote on them.
If a feature receives a significant amount of votes or is deemed to have merit development may include the feature in a future release.
We have released a patch to address this issue, version 22.214.171.124. You can download this using Check for Updates (from the Help menu in the SQL Backup GUI) or by downloading the installer from the SQL Backup page.
If you have already upgraded to SQL Backup 7.3, you will not need to upgrade your server components again.
How to backup/restore MySQL database without a plain dump? How do you backup and restore a MySQL database on your system without using the plain dump?
Unfortunately, SQL Backup is not compatible with MySQL databases.
I want to generate a report of the log restores of a database. The GUI has an option to generate the backup history but not the restore history. I am trying to troubleshoot something and this is needed. I can see all the logs in the GUI in the Activity History pane, but don't want to copy/paste. Any possibilities? Through GUI or sql query? Of course, I am talking about log backups taken using RedGate.
Thank you for your forum post.
Sadly the reporting feature of SQL Backup Pro does not generate reports on restore tasks.
I have added the details of this forum post to an existing feature request whose reference is SB-4562.
Hopefully you may see this feature in a future version of the product.
The latest version for SQL Backup is 126.96.36.199. The latest version of the server components is 188.8.131.52. This is a patch release to fix the following problems:
-SB-5468 - Including WITH COPYTO_HOSTED, VERIFY and COPYTO = '<network location>' in a BACKUP command causes backup files to be uploaded to a hosted storage account twice.
- SB-5459 - If WITH VERIFY is included in a BACKUP command, the outcome of copying a backup to a network share is not reported in the Activity History or Backup Properties.
To upgrade to the latest version, use Check for Updates (available from the Help menu) or download a trial from the SQL Backup Pro page and use your serial number to activate.
Once you have upgraded the GUI, you will need to upgrade the SQL Backup server components:
- Right-click the SQL Server instance in the Registered SQL Servers pane and select Install or Upgrade Server Components, then follow the instructions.
- Run SQBServerSetup.exe on the server. By default, this is located in %ProgramFiles%\Red Gate\SQL Backup 7 or %ProgramFiles(x86)%\Red Gate\SQL Backup 7 on 64-bit servers.