Missing functionality - RESTORE LOG...WITH MOVE

Compresses, encrypts, secures and monitors SQL Server backups.

Moderators: Chris Auckland, eddie davis, Colin Millerchip, Brian Harris, james.billings, RBA, petey

Missing functionality - RESTORE LOG...WITH MOVE

Postby meastland » Fri Aug 31, 2012 5:22 pm

I believe there is a bug in version 6.5.2.21 of SQL Backup. The problem is that the WITH MOVE construct is not available to the SQL Backup implementation of the RESTORE LOG command as it is with the Native RESTORE LOG command. Consider the following log shipping scenario:

A new data file is added to the primary database.
The disk on which the file is created does not exist on the secondary database server.
When trying to restore the SQL Backup log file created after the new data file was created, an error similar to the following is generated:

SQL error 3156: SQL error 3156: File 'NewLogicalDataFile' cannot be restored to 'PrimaryPathWhichDoesNotExistOnSecondary\\NewLogicalDataFile.ndf'. Use WITH MOVE to identify a valid location for the file.

When trying to use the RESTORE LOG...WITH MOVE construct in SQL Backup, the following error is returned:

SQL Backup v6.5.1.9
Syntax error: 'MOVE' after 'WITH'

name value
exitcode 850
sqlerrorcode 0

At this point, the SQL Backup file must be converted to the native *.bak format. After the conversion, the Native RESTORE LOG...WITH MOVE command can be executed.

100 percent processed.
Processed 0 pages for database 'DatabaseName', file 'OldLogicalDataFile' on file 1.
Processed 0 pages for database 'DatabaseName', file 'NewLogicalDataFile' on file 1.
Processed 2 pages for database 'DatabaseName', file 'OldLogicalLogFile' on file 1.
RESTORE LOG successfully processed 2 pages in 0.119 seconds (0.123 MB/sec).

And SQL Backup log shipping can continue.

I realize that we are not on version 7 of SQL Backup, so please let me know if this issue is resolved in the current version. That would be sufficient reason for me to support an upgrade to my manager.
meastland
 
Posts: 37
Joined: Mon Mar 28, 2011 5:56 pm

Postby Chris Auckland » Mon Sep 03, 2012 7:01 pm

This doesn't appear to work in v7 either. The help file seems think the syntax should be supported, so I'll see what's up.
Chris
Chris Auckland
 
Posts: 757
Joined: Tue Oct 24, 2006 2:12 pm
Location: Red Gate Software Ltd.

Postby Chris Auckland » Fri Sep 07, 2012 11:39 am

Sorry for the delay.

I've confirmed this as a bug with the current and previous versions, and case SB-5388 has been raised for it. This will be fixed and available in the next update.

If you can't wait for the next update, then we might be able to send you a private patch.
Chris
Chris Auckland
 
Posts: 757
Joined: Tue Oct 24, 2006 2:12 pm
Location: Red Gate Software Ltd.

SQL Backup 6

Postby manferdmanny » Fri Sep 21, 2012 6:24 am

I consider there is a bug in version 6.5.2.21 of SQL Backup. The problem is that the with move construct is not obtainable to the SQL Backup completion of the restore LOG command as it is with the Native RESTORE LOG command. believe the following log delivery situation:

A new data file is additional to the main database.
The hard disk on which the folder is created does not exist on the minor record server.
When trying to restore the SQL Backup log file created after the new data file was shaped, an error similar to the following is produced.



Georgia gate
manferdmanny
 
Posts: 1
Joined: Fri Sep 21, 2012 6:12 am

Postby Chris Auckland » Fri Sep 21, 2012 9:10 am

That sounds the same as the problem above. The bug report SB-5388 was logged for it and should be fixed in the next update.
Chris
Chris Auckland
 
Posts: 757
Joined: Tue Oct 24, 2006 2:12 pm
Location: Red Gate Software Ltd.

Postby meastland » Tue Oct 09, 2012 5:11 pm

Chris - Any update on this? Can we expect the functionality to be included in 7.3? I am still running on version 6.5 and will likely wait for this to be addressed before upgraded to 7.x. Thanks in advance.
meastland
 
Posts: 37
Joined: Mon Mar 28, 2011 5:56 pm

Postby meastland » Tue Nov 27, 2012 10:43 pm

I have yet to hear back on this. Since I have a support contract, would I be better served by opening a formal ticket?
meastland
 
Posts: 37
Joined: Mon Mar 28, 2011 5:56 pm


Return to SQL Backup 6

Who is online

Users browsing this forum: No registered users and 1 guest