Comments
Sort by recent activity
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...
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...
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...
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...
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...
Thank you so much Peter.
This is exactly what I was trying to achieve. I tried your example on one of my test servers and it worked perfect.
This way I can now keep full 1 weeks backup of all my databases on my Production server and mirror them to my backup server as well. Later every night I can get all my full backups transferred to tapes
Once again Thank you very much.
-Gladiatr / comments
Thank you so much Peter.
This is exactly what I was trying to achieve. I tried your example on one of my test servers and it worked perfect.
This way I can now keep full 1 weeks backup of all my da...