July 29, 2002 at 9:59 am
Working at configuring log shipping on test machines in prep for implimenting on our production SQL Server 7.0. Have fresh SQL 7 installation with SP4 as test "production" server, shipping to test standby server on Desktop Edition machine. Following instructions laid out at http://www.sql-server-performance.com/sql_server_log_shipping.asp with jobs scheduled on "production" server, shipping and restoring full database backups once a day and transaction logs every 15 minutes. Have it working on 2 test databases, Northwind and pubs, all goes well there. Now created a new database on "production" server, however the last step of the job fails when trying to restore the TestLogShip1 database on the standby server. Get error: Msg 3234, Sev 16: File 'TestLogShip1' is not a database file for database 'TestLogShip1'. [SQLSTATE 42000]
Cannot find any errors or typos, the step seems to fail when executing the stored procedure on standby machine to restore database. Any clues on what this error message means? Can't find anything in BOL or Knowledge Base......
July 29, 2002 at 10:01 am
Sounds like you've either got you bak files confused or the names for them. I think you'll get this error trying to apply a log backup from db A to db B.
Andy
July 29, 2002 at 10:16 am
Thanks for the reply Andy... Have checked and double-checked the bak naming, even created a new BU device & name and tried it again, getting same error. However the database TestLogShip1 does not exist yet on the standby server... do I have to manually get that database to exist on the standby machine before I can restore full backup there?
July 29, 2002 at 10:56 am
Should get created by the restore of the full backup. For log shipping you may need to have that part done first.
Andy
July 29, 2002 at 3:48 pm
Something else is wrong, can't locate the problem. Completely redid the 4 steps that make this work, renamed everything, created new stored procedure with new names. STILL the same error:
Msg 3234, Sev 16: File 'Test_Log_ShipBU' is not a database file for database 'Test_Log_ShipBU'. [SQLSTATE 42000]
Well, it IS the correct BAK file for the database Test_Log_ShipBU....
NT Event Viewer shows successful backup of database on production machine, BAK file gets sent to the correct place on the standby server... it's all working execpt the restore fired from the sp. Sigh....
July 30, 2002 at 11:22 am
THE ANSWER to this problem ---> is that the name used in MOVE statement of the stored procedure on the standby server must be the LOGICAL NAME. Run a query against the production server to find out the logical name of the database within the backup device. Example:
RESTORE FILELISTONLY from disk = 'd:\mssql\backup\tls1.bak'
that being the path to the backup device.
that's the solution! Thanks, fastwide
Viewing 6 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply