Comments
Sort by recent activity
Hi there,
The reason is because there is a quoting error in the syntax... your script should read: SQLBackupC.exe -SQL "BACKUP DATABASES [*] TO
DISK = 'X:\<TYPE>_<SERVER>_<DATABASE>_<DATETIME yyyymmdd_hhnnss>.sqb' WITH COMPRESSION = 2, ERASEFILES = 3"
Your COMPRESSION=2 and ERASEFILES=3 syntax should be inside the double quotes... because it is not, the SQLBackupC.exe is ignoring the two keywords. The compression will still occur because the default is compression level 1.
Hope that helps,
Jason / comments
Hi there,
The reason is because there is a quoting error in the syntax... your script should read:SQLBackupC.exe -SQL "BACKUP DATABASES [*] TO
DISK = 'X:\<TYPE>_<SERVER>_<DA...
Hi there,
The types of backup available in SQL Backup is the same as those available in SQL Server... so when considering incremental backups, you have two main choices:
The differential backup, which records all changes since the last full backup. This means that you do not need to keep the older differential backups if you are happy with the latest one (although you do still need the corresponding full backup file).
-- The advantage is that you only need that one file in addition to the full backup;
-- The disadvantage is that this file will grow over time (and hence take longer to back up).
The transaction log backup, which records all changes since the previous transaction log backup.
-- The advantage of this is that the files created will usually be a lot smaller than a differential or full backup (resulting in much quicker backups)
-- The disadvantage is that you require *all* transaction log backups (referred to as a "log chain") since the last full backup, if any are missing then you will be unable to restore the later transaction log backups.
Hope that helps,
Jason / comments
Hi there,
The types of backup available in SQL Backup is the same as those available in SQL Server... so when considering incremental backups, you have two main choices:
The differential backup, wh...
Hi Giggles,
Would you be willing to send us your SQL Backup data files for further investigation? There are two sets of information we would require, and can use those to identify why the issue is occurring.
Firstly, the data.sdf file (the Server Components' data store), which can be found in
C:\Documents and Settings\All Users\Application Data\Red Gate\SQL Backup\Data\<instance>\
on the server hosting the SQL Server instance exhibiting the issue.
Secondly, the contents of your local GUI cache, which can be found at
C:\Documents and Settings\<user>\Local Settings\Application Data\Red Gate\SQL Backup\
I would recommend zipping the contents up, as this could be quite large. If it's more than 10mb zipped let me know and I'll give you more details to get the right data.
You can email them to me at jason.cook@red-gate.com
Thanks,
Jason / comments
Hi Giggles,
Would you be willing to send us your SQL Backup data files for further investigation? There are two sets of information we would require, and can use those to identify why the issue is...
Hi Kermi,
Have you got the entire output generated by the SQL Backup command in question? You may need to look in the log directory under "All Users" to find it (e.g. c:\Documents And Settings\All Users\Application Data\Red Gate\SQL Backup\Log\[instance name]\)
If it contains information you wouldn't want to post on a forum, you can email it to me at jason.cook@red-gate.com
Thanks,
Jason / comments
Hi Kermi,
Have you got the entire output generated by the SQL Backup command in question? You may need to look in the log directory under "All Users" to find it (e.g. c:\Documents And Settings\All...
Could you return the entire output from the command line when you run the command? Normally there is one or more messages in addition to the VDI 1010 error, and those usually help to indicate the cause of the problem.
Thanks,
Jason / comments
Could you return the entire output from the command line when you run the command? Normally there is one or more messages in addition to the VDI 1010 error, and those usually help to indicate the ...
Hi there,
If you have problems with automatic activation, you can try manual activation using the following link: http://www.red-gate.com/webactivation/activate.aspx
When using the activation wizard in the SQL Backup GUI, select "Activate the license by email", and copy/paste the supplied text into the form on that page.
More information on manual activation can be found at http://www.red-gate.com/supportcenter/C ... Backup.htm ,
Alternatively, if you require more help, contact the support team directly at support@red-gate.com (as you may need to provide the activation request being generated, and I wouldn't recommend posting that on the forums as it exposes your license key)
Hope that helps,
Jason / comments
Hi there,
If you have problems with automatic activation, you can try manual activation using the following link:http://www.red-gate.com/webactivation/activate.aspx
When using the activation wizard...
Hi Chris,
As Nigel mentioned, we hope that it will be fixed in the next release. Because of the visible nature of the problem, if it is included in the next release, it will be covered in the release notes (or alternatively you can ask the support team for an update specifically on bug issue SB-3421 and they will be able to confirm if it has been fixed or not).
As for the "waittype MSQL_XP fix", I have looked back at the previous thread at http://www.red-gate.com/messageboard/vi ... php?t=7908 and I believe there may have been some confusion.
The MSQL_XP wait type in SQL Server indicates that SQL Server is waiting for the extended stored procedure to complete. Because of the way SQL Backup functions (that is, everything is done through the extended stored procedure call), the connection will indicate one of two states - either idle (task hasn't started, or has finished) or MSQL_XP (waiting for master..sqlbackup to return).
It would have no effect on the speed of the backup, it's just a status update.
Now, if a backup or restore task is taking substantially longer than expected, there is one feature within SQL Backup that can help with identifying the state of the backup, which is the master..sqbstatus command:
Using SQL Backup 5, execute the following: execute master..sqbstatus 1
This will tell you how much of the backup has been completed, so it can be used to give an idea of progress so far.
If you need any further information on this, please let us know.
Hope that helps,
Jason / comments
Hi Chris,
As Nigel mentioned, we hope that it will be fixed in the next release. Because of the visible nature of the problem, if it is included in the next release, it will be covered in the rele...
In the first example, you need to use the internal name (listed as "ServiceName"), so you would run: sc sdshow "SqlBackupAgent"
A couple of questions:
- Are there other instances on the same machine, and what version of SQL Server are they.
- What account is the SQL Backup Agent account running as?
Jason / comments
In the first example, you need to use the internal name (listed as "ServiceName"), so you would run:sc sdshow "SqlBackupAgent"
A couple of questions:
- Are there other instances on the same machi...
Hi Jerry,
The purpose of the time zone tab is to group servers in the same time zone together, so that the "now" times are all the same on the timeline. The location name is just a free-text description of the tab.
Groups are for organisational purposes only - they allow groups of servers to be displayed or collapsed out of view, and have no impact on time information.
From what you've got set up, my suggestion would be the following:
- Set up two time zone tabs - one for Eastern, one for UTC.
- In each time zone, add two groups, one for data centre 1, and another for data centre 3.
While you have to flick between the two tabs to view the state for one data centre, for a given tab you can quickly read off what is happening by just scanning down the list with the current time highlighted.
If you did it the other way (one data centre per tab) you would see a fragmented orange bar - appearing 5 hours apart depending on the server time. Not only would you have to keep scrolling horizontally, there's scope for misreading the timeline due to the mixture of time zones.
Hope that helps,
Jason / comments
Hi Jerry,
The purpose of the time zone tab is to group servers in the same time zone together, so that the "now" times are all the same on the timeline. The location name is just a free-text descr...
The error is generated by the SMTP server, and generally implies the server doesn't want to accept the mail (rather than a technical problem). This could be because the mail is being flagged as spam, or the machine sending the test has been flagged as an open relay.
Some links that contain more information on this error: http://kb.mozillazine.org/Administrative_Prohibition http://www.thunder.net/faq.html#admin-prohibition
Hope that helps,
Jason / comments
The error is generated by the SMTP server, and generally implies the server doesn't want to accept the mail (rather than a technical problem). This could be because the mail is being flagged as sp...