Comments
Sort by recent activity
Hi Mike,
How often are you taking these backups?
You can set your SQL Backup job to backup locally, copy the backup file to your network drive, deleting local copies of the backups older than 2 days and backups on your network drive older than 1 hour (This is the current minimum) with a command similar to the following : EXECUTE master..sqlbackup N'-SQL "BACKUP DATABASE [AdventureWorks] TO DISK = ''C:\Backup\<AUTO>.sqb'' WITH COMPRESSION = 1, COPYTO = ''\\Storage\Backups'', ERASEFILES = 2, ERASEFILES_REMOTE = 1h, FILEOPTIONS = 1"'
Scheduling the restore part of this is a little more tricky, how often are you going to be restoring? Are these going to be Full Backups, Transaction log backups?
Is this just for one database or several? / comments
Hi Mike,
How often are you taking these backups?
You can set your SQL Backup job to backup locally, copy the backup file to your network drive, deleting local copies of the backups older than 2 day...
Hi Bjorn,
SQL Response depends on WMI when connecting to the servers it is monitoring, WMI/DMOM uses a range of ports so setting up SSH to listen on all of these ports and forward would be a real pain.
I am guessing the SQL Servers are in a different domain to your Alert Repository/Client which we currently don't support.
You could try installing the Alert Repository in the same domain/site as your SQL Servers.
I hope this helps. / comments
Hi Bjorn,
SQL Response depends on WMI when connecting to the servers it is monitoring, WMI/DMOM uses a range of ports so setting up SSH to listen on all of these ports and forward would be a real p...
Hi PWales,
SQL Response will store trace files on the server, it will store either a maximum of 20 files or 1GB in size for each instance before they are deleted/recycled.
Relevant sections of the trace files are transferred to the Alert Repository before being deleted from the SQL Server. The trace data is kept on the alert repository for the time specified in the alert repository options dialog.
The location of the trace files is :
[All Users]\Application Data\Red Gate\SQL Response 1\Alert Repository\\[nn]\[nn]\[nn]\[nn].trace
I hope this helps. / comments
Hi PWales,
SQL Response will store trace files on the server, it will store either a maximum of 20 files or 1GB in size for each instance before they are deleted/recycled.
Relevant sections of the ...
Hi Traci,
Unfortunately you have run into a bug with SQL Prompt.
I have recreated this my end and unfortunately the only way to get this working correctly is to disable cross-database support.
I have added this to our bug tracking system.
Thank you for pointing this out to us. / comments
Hi Traci,
Unfortunately you have run into a bug with SQL Prompt.
I have recreated this my end and unfortunately the only way to get this working correctly is to disable cross-database support.
I ha...
Hi John,
What happens if you try to compare your msdb database to itself?
Does this succeed or fail with the same message?
Would it be possible for you to send the SQL Backup backup file to support@red-gate.com quoting reference number F0017400 in the subject?
Thanks, / comments
Hi John,
What happens if you try to compare your msdb database to itself?
Does this succeed or fail with the same message?
Would it be possible for you to send the SQL Backup backup file to support...
Hi Simut,
Thank you for your post into the forum.
The amount of compression will depend on the type of data in your databases. If for example your databases contain a lot of image or binary data the amount of compression achievable will be minimal.
We do have a Compression Analyzer which you can use to see the expected amount of compression for each of the different levels, have you tried this? It is available on Step 4 of the Backup wizard or in the SQL Backup GUI installation directory.
With regards to the backup time increasing, have you tried multiple threads in your job?
Thanks, / comments
Hi Simut,
Thank you for your post into the forum.
The amount of compression will depend on the type of data in your databases. If for example your databases contain a lot of image or binary data t...
Hi,
Try this : SET @cmd = '-SQL "CONVERT ''' + @f1 + ''' TO ''' + @f2 + '''"'
EXEC MASTER..sqlbackup @cmd, @exitcode OUT, @sqlerrorcode OUT
I hope it helps, / comments
Hi,
Try this :SET @cmd = '-SQL "CONVERT ''' + @f1 + ''' TO ''' + @f2 + '''"'
EXEC MASTER..sqlbackup @cmd, @exitcode OUT, @sqlerrorcode OUT
I hope it helps,
Hi clinford,
It seems to be a permissions issue, if you right click the job in SSMS/Enterprise Manager and start it, do you get an error message and an entry in the Application Log/SQL Server logs or does it start ok?
What is the error message if any?
When you look at the properties of the job, does it have an owner with sufficient permissions?
Thanks, / comments
Hi clinford,
It seems to be a permissions issue, if you right click the job in SSMS/Enterprise Manager and start it, do you get an error message and an entry in the Application Log/SQL Server logs ...
Hi John,
This is a current bug in the SQL Backup 5.3 GUI.
Unfortunately the only advice I can offer at this time is to ignore the Activity History entries that do not have the Red SQL Backup safe icon next to them.
I apologise you are encountering this, we are hoping to fix it in a future version.
Thanks, / comments
Hi John,
This is a current bug in the SQL Backup 5.3 GUI.
Unfortunately the only advice I can offer at this time is to ignore the Activity History entries that do not have the Red SQL Backup safe i...
Hi lculley,
Are the backup files for this database restorable?
System error 64 is generally encountered due to network problems, is it always the same backup job/database that fails or is it seemingly random?
If you could paste the contents of the SQL Backup log file here or e-mail it to support@red-gate.com with this forum article in the subject that would be useful.
The following article may apply here : Preventing SQL Backup network backups from timing out
I hope this helps, / comments
Hi lculley,
Are the backup files for this database restorable?
System error 64 is generally encountered due to network problems, is it always the same backup job/database that fails or is it seemin...