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

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

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

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

Hi all, I would also need some help on this. The following job works fine on my log shipping machine, DECLARE @exitcode int DECLARE @sqlerrorcode int exec master..sqlbackup N'-sql "RESTORE LOG [SomeDatabaseName] FROM DISK = ''E:\SQLBackup\SomeDatabaseName_Log_*.sqb'' WITH STANDBY = ''E:\DATABASES\UNDO\UNDO_SomeDatabaseName.DAT'', PASSWORD = ''SomePassword'', MOVETO = ''E:\SQLBackup\TransactionLogArchive\''"', @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 Until I ran in some situation and now when I try to use the above script, the script just runs and never restore anything and keeps running until I stop it manually. I did some research and found that if I replace the asterisk (*) and with actual transaction log backup file that I'm restoring then it works. I use asterisk to restore all the log backup files that are sitting in the central repository. Can please someone provide me help on this. Thanks. gladiatr / comments

Hi all, I would also need some help on this. The following job works fine on my log shipping machine, DECLARE @exitcode int DECLARE @sqlerrorcode int exec master..sqlbackup N'-sql "RESTORE LOG [Som...

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, Thank you Matthew for replying to my post. I didn't get a chance to check your reply earlier since we are busy in upgrading our SQL 2000 database engine to SQL 2005. I understand we can't fix the corrupt transaction log files, however, it would be nice in future if we can do this as well, but I have couple of questions below now: Firstly, I ran into space issue on my PS server and I'm using the MIRRORFILE option, isn't it the job would generate the warning message in the SQLBackup eventlog about running out of space on the PS but at the same time it would mirror the same transaction log on my Standby (LS) server even the job is unable to backup the transaction log backup on the PS machine. According to my understanding this is what MIRRORFILE option is suppose to do. Secondly, the reason we used the MIRRORFILE option is we would like to keep a transaction log backup on the PS as well as on the LS together. If I use the COPYTO option the transaction log backup that is being happening on the PS would copy the corrupt log backup to the LS as well, then this way I would end up having two copies of the corrupt transaction log backup file. Atleast, by using the MIRRORFILE option I have an advantage of a good file on either of the servers. And thirdly, we are keeping the transaction log files on our PS because we have an additional drives on the PS for this purpose with RAID capabilities and we are mirrioring the transaction log backups to the LS so in case of disaster or space issue we can have atleast one fully trusted working transaction log backup. Please put some light on this. Also, thank you for providing me the link to the CopyTool written by Petey I will definitely try this as well. I appreciate your help. 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

RichardB wrote: Hi I've had a shufti around and can't see anything about this. I am logshipping beween 2 servers, using the copyto switch. However occasionally (well 3 times today) the destination file has brought the restores to a halt due to corrupt file. Trying to restore the headeronly on the logship destination failed, trying to convert to trn failed. Solution was simply to copy the file over again, and restart the restore job. Running 4.5.704 on both machines, server2k3 and 2000Ent sp4. Any help gratefully received! Hi, I am having this similar kind of a problem with my log shipping machine and can I get some input on this please. The details are below: We have a production server (PS) and a standby server (LS). On the PS and LS we are running SQLBackup 4.6 and every night we take the full backup of our production databases on the PS and mirror them to the LS using the following command: exec master..sqlbackup N'-SQL "BACKUP DATABASE [DatabaseName] TO DISK = [E:\SQLbackups\DatabaseName_<DATETIME yyyymmdd_hhnnss>] WITH NAME = [<AUTO>], DESCRIPTION = [<AUTO>], PASSWORD = ''<ENCRYPTEDPASSWORD>somepassword</ENCRYPTEDPASSWORD>'', KEYSIZE = 256, COMPRESSION = 3, THREADS = 1, INIT, MIRRORFILE=[\\LS2\SQLBackup\DatabaseName_<DATETIME yyyymmdd_hhnnss>], ERASEFILES=7"', @exitcode OUTPUT, @sqlerrorcode OUTPUT Once the full backup is completed then we backup the transaction logs every 10 minutes on the PS and mirror it to LS using the following command: exec master..sqlbackup N'-sql "BACKUP LOG [DatabaseName] TO DISK = ''E:\SQLbackups\Transaction Logs\DatabaseName_Log_<DATETIME yyyymmdd_hhnnss>.sqb'' WITH NAME = ''<AUTO>'', DESCRIPTION = ''<AUTO>'', PASSWORD = ''<ENCRYPTEDPASSWORD>somepassword</ENCRYPTEDPASSWORD>'', KEYSIZE = 256, MIRRORFILE = ''\\LS2\SQLBackup\DatabaseName_Log_<DATETIME yyyymmdd_hhnnss>.sqb'', COMPRESSION = 3, THREADS = 1"', @exitcode OUTPUT, @sqlerrorcode OUTPUT and then the LS runs a scheduled job to restore the transaction logs backup by executing the command below: exec master..sqlbackup N'-sql "RESTORE LOG [DatabaseName] FROM DISK = ''E:\SQLBackup\DatabaseName_Log_*.sqb'' WITH STANDBY = ''E:\DATABASES\UNDO\UNDO_DatabaseName.DAT'', PASSWORD = ''somepassword'', MOVETO = ''E:\SQLBackup\DatabaseNameTransactionLogArchive\''"', @exitcode OUTPUT, @sqlerrorcode OUTPUT This has been happening for the past two years or so until one day I checked my logs on the LS and noticed that they are sitting there since July and have not been restored by the restore job above. On further investigation I noticed that we have a drive space issue on the PS when the transaction job was executing actually on the PS. The backup log file size on the PS is 0 locally. But if you notice the transaction backup job mention above that is executing on the PS it is suppose to mirror the same file to the LS as well. So I went to see if I can find the file on the LS and I got the file with the 17KB in size. When I tried to restore the file manually it giving me the following error: Not a SQL Backup nor native backup file: 'E:\SQLBackup\DatabaseName_Log_20080727_032000.sqb' SQL Backup exit code: 600 I ran the verify command on the transaction log file and it says: Verifying file: E:\SQLBackup\DatabaseName_Log_20080727_032000.sqb Error 570: File is not a SQL Backup file. Error 715: Backup file is not encrypted. SQL Backup exit code: 715 I checked the next transaction file and it gave the the same error, then I checked couple of more and they are ok and nothing wrong with them. I also used the SQB2MTF command-line utility and the GUI utility but this time it's saying the password is incorrect. I used both the utilities with the good transaction log and with the same password and it worked like a charm. So is there a way we can fix these corrupted transaction log files so that I can use them to restore on my LS without again having to restore a full backup of the database and start from the scratch? I will appreciate your help in this regards. Thanks gladiatr. / comments

RichardB wrote: Hi I've had a shufti around and can't see anything about this. I am logshipping beween 2 servers, using the copyto switch. However occasionally (well 3 times today) the destinati...

0 votes

How can we help you today?

Gladiatr

Comments