User profile for Gladiatr

Hi, Is there a way to convert SQLBackup 5 (.SQB) file format to SQLBackup 6 or higher file format. I would like to use the SQLVirtual Restore to mount the .sqb files that were backed up in SQLBackup 5.4. Thanks. -Muneeb / comments

Hi, Is there a way to convert SQLBackup 5 (.SQB) file format to SQLBackup 6 or higher file format. I would like to use the SQLVirtual Restore to mount the .sqb files that were backed up in SQLBacku...

0 votes

Thanks David for the quick reply. I'll be glad to provide you ideas about the license tracking later. One quick question popped-up in my mind is that I have already running one license on my production machine and if I fill out the form for the fresh activation will I lose my current license on my production server? In that case, do I have to re-activate my license on the production machine. Can you please shed some light on this. -gladiatr. / comments

Thanks David for the quick reply. I'll be glad to provide you ideas about the license tracking later. One quick question popped-up in my mind is that I have already running one license on my produc...

0 votes

Tracking SQLBackup 5 Pro Licenses on the internal network

Hi there, We have purchased two SQLBackup 5 Pro licenses from the Red_Gate for our production and log shipping servers and we deployed one license already on the production sql server. The other li...

2 followers 3 comments 0 votes

Hi Petey, Once again thank you so much for your prompt reply and in fact you have also saved my day as well. I guess, I must have misunderstood what you said in your first reply to my query. Anyhow, I download the hot fix throught the link that you had sent to me on my x64 box and installed it and problem seems to be fixed now as this time I'm able to take the backup of my databases through the SQLBackup 5.4 GUI and as well through the MS SQL Management Studio. Before that, I was unable to take the backup or verify the databases. May be what I did wrong could be this that on my x64 box I must have installed the SQL Backward Compatibility pack for 32bit instead of 64bit. This might have caused this problem. But once again thank you for your support. -gladiatr. / comments

Hi Petey, Once again thank you so much for your prompt reply and in fact you have also saved my day as well. I guess, I must have misunderstood what you said in your first reply to my query. Anyhow...

0 votes

Thanks Petey for the prompt reply. I did check as you mentioned the sqlvdi.dll version and I found four copies at the following locations and there version numbers are stated in brackets: C:\Program Files\Microsoft SQL Server\80\sqlvdi.dll (2000.85.2102.0) C:\Program Files\Microsoft SQL Server\80\Tools\sqlvdi.dll (2000.85.2102.0) C:\Program Files (x86)\Microsoft SQL Server\80\sqlvdi.dll (2000.85.2004.0) C:\Program Files (x86)\Microsoft SQL Server\80\Tools\sqlvdi.dll (2000.85.2004.0) So, as you said in your reply I matched the entry in HKEY_CLASSES_ROOT\Wow6432Node\CLSID to the 64-bit copy. Now, my 32bit and 64bit are using C:\Program Files\Microsoft SQL Server\80\sqlvdi.dll (2000.85.2102.0), but now I'm getting VDI error 1030. Do I have to use this file C:\Program Files (x86)\Microsoft SQL Server\80\sqlvdi.dll (2000.85.2004.0) instead which looks more updated to me but its in the 32bit program files folder. Any thought on this? This is a bit urgent now because we have plans for this coming Saturday to use this box as our new productions server. Any help on this will be appreciated. Thanks. -gladiatr / comments

Thanks Petey for the prompt reply. I did check as you mentioned the sqlvdi.dll version and I found four copies at the following locations and there version numbers are stated in brackets: C:\Progra...

0 votes

SQLBackup 5.4 - Backup and Restore Failed

Hi guys, I need some help on this issue. We have W2K8SP1 Enterprise x64bit w/ SQL 2005 SP2 standard running on 16GB. When I try to restore the database from the backup I get this: TEST: Restore - F...

2 followers 4 comments 0 votes

Matthew Flatt wrote: Hi, Thank you for your post into the forum. Unfortunately there isn't a way to fix these corrupt transaction log files, so if you do not have a local copy on the source server your database will need to be reseeded. In your job scripts, you are using the MIRRORFILE option, if you have now resolved your source server space issues I would advise replacing this with COPYTO. You should then have a good transaction log backup file available on your source server if the copied file does get corrupted. You may wish to use a different program to replace this copying process if you get a lot of logs which become corrupted. Our CopyTool written by Petey may work for you and is available from Here I hope this helps, Hi Matthew, I have a question now regarding this CopyTool. As you have suggested in your earlier reply to use the CopyTool to copy logs file. I have already setup my logshipping in this way now. Now, there is a new problem I discovered today when we again ran out of space on the production server but this time on the C: drive. When I investigated the cause I found out that there was a huge file created by this CopyTool on the C: drive under FTPTools folder in Document and Settings\All Users\Application Data\FTPTools. The size of this file was over 1GB. Now, my question is there any way to change the path of the this CopyTool error log file to some other drive by using parameters like /use or /filelist etc. Or, is there any way not to create this error log file? My other question is, this is a CopyTool so why it is creating an FTPTool folder instead in Document and Settings\All Users\Application Data. Please provide your feedback on this. Also please let me know what /INITLIST exactly does when used. Thanks. -Gladiatr. / comments

Matthew Flatt wrote: Hi, Thank you for your post into the forum. Unfortunately there isn't a way to fix these corrupt transaction log files, so if you do not have a local copy on the source serv...

0 votes

Hi Petey, Thanks for replying to my post. On the production server (PS) we have a job schedule to run every 10 minutes executing the following command to generate a transaction log file locally: DECLARE @exitcode int DECLARE @sqlerrorcode int exec master..sqlbackup N'-sql "BACKUP LOG [Application] TO DISK = ''E:\SQLbackups\Transaction Logs\Application_Log_<DATETIME yyyymmdd_hhnnss>.sqb'' WITH NAME = ''<AUTO>'', DESCRIPTION = ''<AUTO>'', PASSWORD = ''<ENCRYPTEDPASSWORD>password==</ENCRYPTEDPASSWORD>'', KEYSIZE = 256, MIRRORFILE = ''\\LS2\Solomon\Application_Log_<DATETIME yyyymmdd_hhnnss>.sqb'', COMPRESSION = 3, THREADS = 1"', @exitcode OUTPUT, @sqlerrorcode OUTPUT IF (@exitcode <>0) OR (@sqlerrorcode <> 0) BEGIN RAISERROR ('SQL Backup job failed with exitcode: %d SQL error code: %d', 16, 1, @exitcode, @sqlerrorcode) END Once this job executes, it creates a sqlbackup log file locally on the PS and then it mirrors the log file to the standby server (LS). The following log file generated when we had the space issue on the PS with the log file of zero size. Here is the log: SQL Backup log file 10/11/2008 2:00:01 AM: Backing up Application (transaction log) to: E:\SQLbackups\Transaction Logs\Application_Log_20081011_020001.sqb \\LS2\Solomon\Application_Log_20081011_020001.sqb 10/11/2008 2:00:01 AM: BACKUP LOG [Application] TO DISK = 'E:\SQLbackups\Transaction Logs\Application_Log_20081011_020001.sqb' WITH NAME = '<AUTO>', DESCRIPTION = '<AUTO>', PASSWORD = 'XXXXXXXXXX', KEYSIZE = 256, MIRRORFILE = '\\LS2\Solomon\Application_Log_20081011_020001.sqb', COMPRESSION = 3, THREADS = 1 Thread 0 warning: Warning 210: Error writing to backup file: E:\SQLbackups\Transaction Logs\Application_Log_20081011_020001.sqb Warning: System error code: (There is not enough space on the disk) 10/11/2008 2:00:06 AM: Backup data size : 49.500 MB Processed 5698 pages for database 'Application', file 'Application_Log' on file 1. BACKUP LOG successfully processed 5698 pages in 3.749 seconds (12.450 MB/sec). The following command restore the logs on the LS: DECLARE @exitcode int DECLARE @sqlerrorcode int exec master..sqlbackup N'-sql "RESTORE LOG [Application] FROM DISK = ''E:\Solomon\Application_Log_*.sqb'' WITH STANDBY = ''E:\DATABASES\UNDO\UNDO_Application.DAT'', PASSWORD = ''password'', MOVETO = ''E:\Solomon\ApplicationTransactionLogArchive\''"', @exitcode OUTPUT, @sqlerrorcode OUTPUT IF (@exitcode <>0) OR (@sqlerrorcode <> 0) BEGIN RAISERROR ('SQL Backup job failed with exitcode: %d SQL error code: %d', 16, 1, @exitcode, @sqlerrorcode) END When I try to restore the file from the LS which was generated by the MIRRORFILE option produces the following log: SQL Backup log file 10/11/2008 2:10:00 AM: Not a SQL Backup nor native backup file: 'E:\Solomon\Application_Log_20081011_020001.sqb' Since this happens, I have to always restore the full backup once again then apply the individual log files to make the log shipping working. Being in the following situation, this made me think that the MIRRORFILE option is no more reliable. This is just one database example I mentioned here. I have 18 other databases running on the PS and jobs similar to the one I mentioned above to generate sqlbackup logs and because of this space issue those jobs obviously created 0 size file but at the LS end the MIRRORFILE option looks like created a reliable restorable transaction log file but it fails only when you try to restore those logs on the LS. So the outcome, my log shipping breaks everytime the space issue arises. Your help is appreciated. Thanks again. -gladiatr. / comments

Hi Petey, Thanks for replying to my post. On the production server (PS) we have a job schedule to run every 10 minutes executing the following command to generate a transaction log file locally: DE...

0 votes

MIRRORFILE Option in SQLBackup 5.3

Hi All, One thing I don't understand about the MIRRORFILE Option in SQLBackup 5.3 is that when you are using the SQLBackup backup command to get the backup locally along with the MIRRORFILE Option ...

2 followers 3 comments 0 votes

Thanks Matthew for the reply. Actually, since you mentioned this, I noticed the Edition is expired now. This could be the cause to my problem. In September we have purchased the 2 SQLBackup Pro licences and still I haven't get a chance to use any of them. Right now this is a test server that I'm working on and soon is going to become a production server and I thought that I should wait till it becomes production and then I will use the one license. Thanks. -gladiatr / comments

Thanks Matthew for the reply. Actually, since you mentioned this, I noticed the Edition is expired now. This could be the cause to my problem. In September we have purchased the 2 SQLBackup Pro lic...

0 votes

How can we help you today?

Gladiatr

Activity overview