Comments
Sort by recent activity
If you are comfortable using the 'regedit' application, could you please check the "SQLDataRoot" value of the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Setup
If you are using a 64-bit server to run SQL Server, this will be under:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\MSSQLServer\Setup
--
Normally, this will be set to the folder SQL Server was installed at, for example "C:\Program Files\Microsoft SQL Server\MSSQL" or "C:\Program Files (x86)\Microsoft SQL Server\MSSQL".
If this folder is incorrect or missing, it causes SQL Backup to exhibit the behaviour you have described.
If the key is missing:
* Right click the "Setup" folder in the left hand pane
* Select "New >" and String Value
* Set the value to "SQLDataRoot", minus the double quotes
* Double Click on the value, and set it to your SQL Server directory, for example "C:\Program Files\Microsoft SQL Server\MSSQL" for a 32-bit server.
If this doesn't resolve the problem or you have any other questions, feel free to follow up either on the forum, or by contacting James or myself via email. If this does resolve the problem please let us know so that we know that it is a working solution and will aim to fix the problem in a subsequent release.
Thanks,
Jason / comments
If you are comfortable using the 'regedit' application, could you please check the "SQLDataRoot" value of the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Setup
If you ...
The created job can be edited through Enterprise Manager or Management Studio in the same way as any other job created outside the SQL Backup interface.
The following example shows a full backup of the database 'mydatabase' generated as a job by SQL Backup 4. The *** Insert *** comment is where you would need to add the NOWRITE statement mentioned previously.
The job would then perform the truncation of the log, and then the full backup of the database 'mydatabase' at the scheduled times. DECLARE @exitcode int
DECLARE @sqlerrorcode int
*** Insert NOWRITE command here ***
EXECUTE master..sqlbackup N'-SQL "BACKUP DATABASE [mydatabase] TO DISK = ''<AUTO>'' WITH COMPRESSION = 1"', @exitcode OUT, @sqlerrorcode OUT
IF (@exitcode >= 500) OR (@sqlerrorcode <> 0)
BEGIN
RAISERROR ('SQL Backup failed with exit code: %d SQL error code: %d', 16, 1, @exitcode, @sqlerrorcode)
END
Alternatively, you can create a new job in Enterprise Manager or Management Studio and for the "steps" section, paste in the NOWRITE code mentioned before.
Hope that helps,
Jason / comments
The created job can be edited through Enterprise Manager or Management Studio in the same way as any other job created outside the SQL Backup interface.
The following example shows a full backup of...
SQL Backup behaves much the same as Native Backups in this regard. By default the log will be truncated when a log backup is performed, but will not be truncated during a full/complete or differential backup.
--
If you need to truncate the log only and don't want to perform transaction log backups, natively the TRUNCATE_ONLY keyword exists.
However since this breaks the log chain, Microsoft are planning to deprecate this keyword in a future release - a full or differential backup must be performed immediately after executing the command, otherwise a break in the backup chain will occur.
If you are sure that is what you want to do, SQL Backup can perform a similar operation, using the following command:
execute master..sqlbackup '-SQL "BACKUP LOG [dbname] TO DISK = ''c:\backup.sqb'' WITH NOWRITE"';
The DISK location is required but can be set to an arbitrary value (e.g. 'c:\backup.sqb'). Likewise, a full or differential *must* be performed immediately after the truncation.
More information on the above is provided in Books Online here: http://msdn2.microsoft.com/en-us/library/ms189085.aspx
Hope that helps,
Jason / comments
SQL Backup behaves much the same as Native Backups in this regard. By default the log will be truncated when a log backup is performed, but will not be truncated during a full/complete or differen...
Hi,
This is indeed an issue that exists in version 4.6 - the same occurs with other formatting such as using the tab key in the middle of a statement. Unfortunately the only solution is to ensure the command remains on one line, without newline or tabbing characters.
For reference, this issue has been resolved in the soon to be released version 5.0, where newline and tab characters can be used in the middle of a SQL Backup expression without problems.
Thanks,
Jason / comments
Hi,
This is indeed an issue that exists in version 4.6 - the same occurs with other formatting such as using the tab key in the middle of a statement. Unfortunately the only solution is to ensure ...
The SQL Backup binaries/server components need to be installed onto a local disk (such as the c:\ drive). Any backups created (or restores used) will need to go onto the shared storage.
More information on setting up SQL Backup 4.x for a clustered installation is provided here: http://www.red-gate.com/messageboard/vi ... php?t=1880
Jason / comments
The SQL Backup binaries/server components need to be installed onto a local disk (such as the c:\ drive). Any backups created (or restores used) will need to go onto the shared storage.
More infor...
Yes, keyboard shortcuts will be included in the final release.
Thanks,
Jason / comments
Yes, keyboard shortcuts will be included in the final release.
Thanks,
Jason
The command Peter provided will change the database from the "loading" state to the "live" state without any subsequent restores - the database will be made available (and start processing requests) in the state the log shipping wizard left it.
Jason / comments
The command Peter provided will change the database from the "loading" state to the "live" state without any subsequent restores - the database will be made available (and start processing requests...
The restore header steps are designed for diagnostic use. The two commands provide different information about the backup:
HEADERONLY returns information about the backup itself, including the database that was backed up, Server and SQL Server instance name, LSN information and more.
FILELISTONLY returns a list of the logical and physical files that are in the backup, and some basic information about each file (LSN information, size and so on).
Given that you have established the restore is working fine, there is no need to try the above commands (since they can be used as the first step to identify if the file has been corrupted)... but if you do wish to try them, they will not touch the database, and will not change the backup file.
As for the performance... 20 minutes for a 50GB database restore seems to be in the right ballpark (about 40mb/s)... it will depend on what compression and encryption levels you were using.
Hope that helps,
Jason / comments
The restore header steps are designed for diagnostic use. The two commands provide different information about the backup:
HEADERONLY returns information about the backup itself, including the dat...
Both the command line and extended stored procedure will create the full size of the file before it performs the restore - this can take some time if the changes in file size are significant.
Unfortunately the beta version does not give any feedback on the progress of creating the file, but I will raise this with the developers and see if it is possible to include for the final release.
If the files already exist and are a similar size to the current files being replaced then the "file creation" step will be very short (a matter of seconds) before it moves onto the next step - it's entirely dependent on the amount of disk space that needs to be allocated.
===
As for the Retrieving History comment, can you perform the steps that HJoyce described in the post above yours? Does that return anything, or does that never return?
Thanks,
Jason / comments
Both the command line and extended stored procedure will create the full size of the file before it performs the restore - this can take some time if the changes in file size are significant.
Unfor...
Hi Julian,
Thankyou for posting and emailing the application logs.
Unfortunately, SQL Server 2005 does not support the backing up or restoring of snapshots, such that SQL Backup likewise does not support this feature. As a result the error "SQL error 3002: Cannot BACKUP or RESTORE a database snapshot." was raised in the log.
There is an issue in the user interface however as it should not be allowing you to perform a backup of a snapshot, and I have added a report so that the developers can hopefully look into this at some stage before the final release.
Thanks,
Jason / comments
Hi Julian,
Thankyou for posting and emailing the application logs.
Unfortunately, SQL Server 2005 does not support the backing up or restoring of snapshots, such that SQL Backup likewise does not s...