Missing functionality - RESTORE LOG...WITH MOVE
meastland
Posts: 47
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.
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.
Comments
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.
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