- RSS Channel Showcase 7524665
- RSS Channel Showcase 3280301
- RSS Channel Showcase 4184743
- RSS Channel Showcase 8256730
Articles on this Page
- 11/07/13--01:25: _RE: Click on server...
- 11/07/13--03:12: _SQL Backup 7.5
- 11/11/13--07:47: _SQL Backup failed w...
- 11/11/13--08:03: _Cluster service cou...
- 11/11/13--15:52: _RE: SQL Backup fail...
- 11/11/13--17:49: _RE: Cluster service...
- 11/12/13--06:16: _RE: Cluster service...
- 11/12/13--06:28: _RE: Cluster service...
- 11/13/13--08:14: _Any Way to Configur...
- 11/14/13--10:01: _Upgrade/Update Path...
- 11/14/13--10:38: _RE: Any Way to Conf...
- 11/14/13--14:48: _RE: Any Way to Conf...
- 11/14/13--15:54: _RE: Any Way to Conf...
- 11/15/13--07:36: _seeing MDB size wit...
- 11/17/13--21:46: _RE: seeing MDB size...
- 11/20/13--22:28: _RE: SQL Backup 7.5
- 11/21/13--13:12: _RE: SQL Backup 7.5
- 11/21/13--20:20: _RE: SQL2012 - Avail...
- 11/27/13--10:41: _Please STOP auto-re...
- 11/28/13--02:14: _RE: SQL Backup fail...
- 11/07/13--01:25: RE: Click on server name, green circle spins forever
- 11/07/13--03:12: SQL Backup 7.5
- 11/11/13--07:47: SQL Backup failed with exit code: 669
- 11/11/13--08:03: Cluster service could not write... RG Ver 126.96.36.199
- 11/11/13--15:52: RE: SQL Backup failed with exit code: 669
- 11/11/13--17:49: RE: Cluster service could not write... RG Ver 188.8.131.52
- 11/12/13--06:16: RE: Cluster service could not write... RG Ver 184.108.40.206
- 11/12/13--06:28: RE: Cluster service could not write... RG Ver 220.127.116.11
- 11/13/13--08:14: Any Way to Configure Include and Exclude DBs. ...
- 11/14/13--10:01: Upgrade/Update Path from 18.104.22.1686
- 11/14/13--10:38: RE: Any Way to Configure Include and Exclude DBs. ...
- 11/14/13--14:48: RE: Any Way to Configure Include and Exclude DBs. ...
- 11/14/13--15:54: RE: Any Way to Configure Include and Exclude DBs. ...
- 11/15/13--07:36: seeing MDB size without restoring ?
- 11/17/13--21:46: RE: seeing MDB size without restoring ?
- 11/20/13--22:28: RE: SQL Backup 7.5
- 11/21/13--13:12: RE: SQL Backup 7.5
- 11/21/13--20:20: RE: SQL2012 - Availability Groups - backing up via replica
- 11/27/13--10:41: Please STOP auto-refresh!
- 11/28/13--02:14: RE: SQL Backup failed with exit code: 669
I just want to know if there is already another solution excluding deleting the old backup history?
I have seen the same query running for hours (may be more, but I stop it after 2h) what tleblanc mentioned.
It would be very nice to find a way that the GUI is working again as expected.
We're pleased to announce that SQL Backup 7.5 has been released and is available to download. This is a minor release and includes new features and bug fixes.
â¢Improved Windows 2012 Cluster installation support
â¢SQL Server 2012 support in the Maintenance Plan Conversion Wizard.
â¢When backing up, you can use the USEQUEUEDCOPY keyword to place backup files in the transaction log copy queue providing additional retries.
This means that in the event of long network outages, SQL Backup will keep trying to copy the file for 24 hours
For more information, see The BACKUP command. This option is not available from the GUI.
â¢Allow reading of password from a text file, as an alternative to storing it in a SQL Server Agent Job. This means access to the password can be restricted using Windows file permissions.
For more information, see The BACKUP command and The RESTORE command. This option is not available from the GUI.
â¢Improved upload performance for backups to Hosted Storage
SQL Backup 7.5 is a free upgrade from versions 7.0, 7.1, 7.2, 7.3 and 7.4. To upgrade, from the Help menu select Check for Updates or download a trial from the SQL Backup page and use your serial number to activate.
User interface version: 22.214.171.1249 (to check the version number, from the Help menu select About SQL Backup).
Server components version: 126.96.36.199 (to check the version number, from the Edit menu select Properties).
- Project Manager, SQL Backup
- Red Gate Software Ltd.
Anybody know what a 669 is?
the "Error code reference - SQL Backup" page here skips from 668 to 680.
The version i'm running is 188.8.131.52
Date 11/11/2013 8:43:36 AM
Log Job History (SQL Backup differential backup: model and 6 others (created 10/24/2013 3:44:44 PM))
Step ID 1
Job Name SQL Backup differential backup: model and 6 others (created 10/24/2013 3:44:44 PM)
Step Name execute master..sqlbackup
Sql Severity 16
Sql Message ID 50000
Operator Net sent
Retries Attempted 0
Executed as user: CWI\sql-sa-bb1db. SQL Backup failed with exit code: 669 SQL error code: 0 [SQLSTATE 42000] (Error 50000). The step failed.
We are running Red Gate Version 184.108.40.206 in a clustered environment. A while back we fixed this error by upgrading to a higher version of the Redgate Software, but seems it came back.
Here's the error:
Event Type: Error
Event Source: ClusSvc
Event Category: Database Mgr
Event ID: 1080
Time: 9:23:35 AM
Computer: <<SERVER NAME>>
Cluster service could not write to a file (C:\DOCUME~1\!CLUST~1\LOCALS~1\Temp\CLSC67F.tmp). The disk may be low on disk space, or some other serious condition exists.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
0000: 05 00 00 00
Has anyone else countered this problem, and if so, how was it fixed?
SQL Backup generates a log file for each process that it runs. 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.
Could you please post the contents of the log file for the backup that failed?
Does this help (http://technet.microsoft.com/en-us/library/cc960220.aspx)?
thanks for your post.
The disk isn't even close to being full and the path points to the C:\ drive not the Quorum. We've verified permissions, etc. and it all checks out clean.
This issue first appeared a couple of years back on version 6.x and had something to do with Red Gate's registry key replication.
I know what the work around was back then, but there were side effects that we didn't care for, and it was fixed on a later upgrade... so I am intrigued as to why did it come back, and of course need a solution that wont disable the replication.
Did SQL Backup report any errors in the backup or restore process?
I may be missing something, but is there an option when creating "Scheduled Backup Job" to Configure RedGate Backup to Automatically Include New Dbs
to be backed up and exclude the ones which were deleted on the Server?
SQL 2008 standard on a Server 2008R2 host
I have an maintenance windows tomorrow and I'd like to bring my version of RedGate up the latest known good release.
However I'm searching for information on the best way to do this
When I choose check for updates - it comes up as SqlBackup 7.4 Minor release as the only option.
Do I need to stop and services in sql before the upgrade?
Will this require a reboot?
Basically what can I expect so I know how to plan for the upgrade?
If you have detailed instructions those would probally work as well.
But - just saying download and install the upgrade doesn't tell me enough to know what to expect before moving forward.
I've looked through the help file for "Installing or Upgrading on a SQL Server Instance" It's kind of helpful, except I'm having issues with the registered servers - the are mostly not available. I have to keep refreshing to get them connected - but that's only for a few seconds that they stay connected - certainly not log enough for me to setup a log shipping job. I'm pretty sure this is part of the problem that the fix for 3.1.1 fixes. Not sure
Anyway any help would be greatly appreciated.
You could use the All or USER option to to backup all or all user databases.
Unfortunately these options are not available from the UI as the UI will script out all the database names.
You will have to manually edit the job step in SQL Server Agent.
The idea behind using "RedGate" was to automate backups as much as possible.
so, GUI doesn't allow to specify all and script will get regenerated?
it means that i need to go to GUI daily on each Server and check "All"?
or instead of
EXECUTE master..sqlbackup '-SQL "BACKUP DATABASES [master,model,...
I can somehow specify all?
if not, is this option in new release?
In the GUI when you check the ALL check box it will script out all the names of the databases.
EXECUTE master..sqlbackup '-SQL "BACKUP DATABASES [master,model,msdb,db1,db2......
You can edit the job so that it uses the ALL argument or * wildcard.
EXECUTE master..sqlbackup '-SQL "BACKUP ALL DATABASES
EXECUTE master..sqlbackup '-SQL "BACKUP DATABASES [*]
There are no plans to change this behavior in new or future releases
If I purchase, will I be able to open an .sqb file in the Microsoft restore gui and see the size of the LIVE .MDB file WITHOUT RESTORING like I can directly with a .bak file ?
You can use the SQL Backup GUI to see the database size e.g.
You can also check the database size using Windows Explorer, as SQL Backup comes with an Explorer add-on e.g.
Lastly, you can run the RESTORE SQBHEADERONLY command to check the database size e.g.
Allow reading of password from a text file, as an alternative to storing it in a SQL Server Agent Job. This means access to the password can be restricted using Windows file permissions.
I've opened a support case but how come SQLToolbelt shows SQLBackup 7.4 now?
Did you back out 7.5 from being available?
Modify the error checking in the command to this:
IF (@exitcode >= 500) OR (@sqlerrorcode <> 0 and @sqlerrorcode <> 976)
so that the SQL agent job will succeed and ignore the 976 error and report success
I know I've asked for this before, AND added a request to Uservoice, but after six YEARS of constantly being annoyed and LOSING TIME while reviewing the Activity History BECAUSE OF THE DARNED AUTO-REFRESH, could you please, like Microsoft so kindly gives in Profiler, GIVE US AN OPTION IN THE VIEW MENU TO STOP AUTO-REFRESH, PLEASE!
Sorry, just got another time-waster auto-refresh and I'm a bit peeved that I have to take a lot longer to do a simple thing than I should.
THANKS in advance.
SQL Backup Exit Code 669 indicates that the start-up account for the SQL Backup Agent service does not have read / write permissions to the SQL Backup registry folders.
Please check the following registry folders and ensure that the account given to the SQL Backup Agent service has read/write permissions to the following registry folders:
HKEY_LOCAL_MACHINE\SOFTWARE\Red Gate\SQL Backup\BackupSettings\<InstanceName>
HKEY_LOCAL_MACHINE\SOFTWARE\Red Gate\SQL Backup\BackupSettingsGlobal\<InstanceName>
HKEY_LOCAL_MACHINE\SOFTWARE\Red Gate\SQL Backup\InstalledInstances\<InstanceName>
Where <InstanceName> is the name of the SQL Instance for a named instance or (local) for the default instance?