Activity overview
Latest activity by RBA
Hi,
New databases will only be automatically included if you have a generic backup operation such as BACKUP DATABASES *, or BACKUP DATABASES EXCLUDE [...]. (See 'toolkit syntax' in help).
Creating a new database will not alter your existing SQL Server Agent jobs. If you created the job using SQL Backup, you'll be able to easily edit the job from within the GUI (Select the instance and switch to the jobs tab, then right click -> Edit)
The GUI is smart enough to know what's possible and will grey-out databases that are in simple recovery mode for TLOG operations. If you use the stored procedure directly, an error will be generated if you attempt to perform such an action. If you use a generic operation like 'BACKUP LOGS * TO DISK...' it will automatically exclude simple recovery mode databases.
Hope this helps, / comments
Hi,
New databases will only be automatically included if you have a generic backup operation such as BACKUP DATABASES *, or BACKUP DATABASES EXCLUDE [...]. (See 'toolkit syntax' in help).
Creating ...
You can read more about this here. The default value is 30 seconds, so 45 could be a good start.
Thanks, / comments
You can read more about this here. The default value is 30 seconds, so 45 could be a good start.
Thanks,
Hi Randy,
This should be a DWORD (note that the default entry format might be hexadecimal). Please let me know if you have any more problems.
Thanks, / comments
Hi Randy,
This should be a DWORD (note that the default entry format might be hexadecimal). Please let me know if you have any more problems.
Thanks,
Each thread uses its own VDI which is treated as separate media.
So this is the sort of thing that happens behind the scenes if you perform a 3-thread backup: (from SQL Profiler) BACKUP DATABASE [small] TO VIRTUAL_DEVICE = 'SQLBACKUP_7101A731-CB71-43DF-93E3-12CD2704FA0A', VIRTUAL_DEVICE = 'SQLBACKUP_7101A731-CB71-43DF-93E3-12CD2704FA0A01', VIRTUAL_DEVICE = 'SQLBACKUP_7101A731-CB71-43DF-93E3-12CD2704FA0A02' WITH BUFFERCOUNT = 18, BLOCKSIZE = 65536, MAXTRANSFERSIZE = 1048576, NAME = N'Database (small), 06/11/2009 11:52:58', DESCRIPTION = N'Backup on 06/11/2009 11:52:58 Server: TST-ROBIN Database: small', FORMAT
This means three entries into the media set table which is the correct behaviour. / comments
Each thread uses its own VDI which is treated as separate media.
So this is the sort of thing that happens behind the scenes if you perform a 3-thread backup: (from SQL Profiler)BACKUP DATABASE 	...
Hi Chris,
Yes, the fix for SB-4359 is in for 6.3 and it is still coming soon.
Sorry for the delay,
Thanks, / comments
Hi Chris,
Yes, the fix for SB-4359 is in for 6.3 and it is still coming soon.
Sorry for the delay,
Thanks,
Hi Randy,
Permissions are always a curious one. That it works using L$ confirms that SQLBackup is a member of the administrators group on the machine hosting the share. The green tick indicates that *both* instances have access. I suspect that if there's a permissions problem, it's on the server hosting the destination instance (since the wizard's file browser uses the SQL Backup agent on the source server to browse and that worked for you).
If you log onto the destination server using the SQL Backup account you could try two things:
1) Browse the shared folder using Windows Explorer, and if this doesn't fail:
2) Use (locally) SQLCMD or Management Studio to execute
exec master..sqbdir '//[path to share]'
go
If both show you the contents of the share then I'm confused as to why the wizard would complain.
Please let me know how you get on,
Regards, / comments
Hi Randy,
Permissions are always a curious one. That it works using L$ confirms that SQLBackup is a member of the administrators group on the machine hosting the share. The green tick indicates tha...
Hi MvdV,
This is a known issue and has been fixed in the latest build. Please contact myself or Red Gate Support for a patch (robin.anderson@red-gate.com) referencing bug SB-4359.
Regards, / comments
Hi MvdV,
This is a known issue and has been fixed in the latest build. Please contact myself or Red Gate Support for a patch (robin.anderson@red-gate.com) referencing bug SB-4359.
Regards,
Hi Richard,
It sounds like you're UI is version 6 and your server components didn't upgrade. To start afresh, you'll need to uninstall at least two things from your server.
The first is the SQL Backup Agent, which can be uninstalled via Add/Remove Programs.
The second is the extended stored procedure from SQL Server. Normally, uninstalling the agent automatically removes the XPs, but sometimes SQL Server holds refuses to release our DLL. In this circumstance you'll have to manually remove it.
There are some other components, such as the shell extention to provide statistics when you hover the mouse over a backup file, but these should not interfere with installation.
Please re-install using the manual installer, which can be found in the install directory of the UI (SQBServerSetup.exe). This will need to be copied to all servers you wish to upgrade. Once you've installed, you can verify the version numbers of the xp_sqlbackup.dll in SS's /binn directory and the agent's version number by querying 'exec master..sqlbackup' with no arguments. They should be 6.2.0.134 at time of writing.
Please let me know how you get on,
Thanks, / comments
Hi Richard,
It sounds like you're UI is version 6 and your server components didn't upgrade. To start afresh, you'll need to uninstall at least two things from your server.
The first is the SQL Bac...
Hi Toeho,
We are currently looking into compatibility for Windows 7 and 2008 R2.
I would be grateful if you could forward me any details regarding these RPC conflicts (robin.anderson@red-gate.com) and mention any other interesting details regarding your 2008 R2 x64 cluster. For example, how many SQL instances do you have on your cluster and do you run them active/active?
Many thanks, / comments
Hi Toeho,
We are currently looking into compatibility for Windows 7 and 2008 R2.
I would be grateful if you could forward me any details regarding these RPC conflicts (robin.anderson@red-gate.com) ...
Hi John,
Currently, the associated error messages are pasted into the log file for a given task. SQL Backup has its own email-on-error / warning feature which of course includes the messages.
As for the quick reference DB - I have such a database here. You can use it via:
DECLARE @exitcode int
DECLARE @sqlerrorcode int
exec master..sqlbackup '', @exitcode OUTPUT, @sqlerrorcode OUTPUT
SELECT [message] from test.dbo.SqlBackupErrorCodes where code = @exitcode
I doubt we'd ever insert any tables as part of the installation, but it would be nice to have an easier way to access the strings. I'll have a word with the developers about this.
Thanks, / comments
Hi John,
Currently, the associated error messages are pasted into the log file for a given task. SQL Backup has its own email-on-error / warning feature which of course includes the messages.
As fo...