How can we help you today? How can we help you today?
Gladiatr
Activity overview Badges (0) Posts (8) Comments (12)

Comments

Sort by recent activity
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
  1. Community
  2. SQL Backup Previous Versions
  3. MIRRORFILE and FILEOPTIONS Parameters
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...
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
  1. Community
  2. SQL Backup Previous Versions
  3. Corrupt Copied TLog Backups
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
Total activity
29
Last activity
Member since
Following
0 users
Followed by
0 users
Votes
0
Subscriptions
9