What are the challenges you face when working across database platforms? Take the survey
Options

Failure using logshipping

henkmeulekamphenkmeulekamp Posts: 14
edited May 10, 2006 11:31AM in SQL Backup Previous Versions
I get error message below when setting up logshipping. (4.2) I did the Logshipping wizard succesfully, and let the schedule begin next day with backups and restore. To try it out I did one manually (backup on source and restore on destination) .. It keeps failing. After I use the Restore wizard in the Sql BAckup GUI it gives the following error.

This is driving me crazy.. the database is is Loading state (was Readonly and thus good)...And it will be in this state forever... (I tried/waited whole night) . So I can delete the database again and restart all over....

Is this a known issue?


Restore ParkmobilePMS
 
Restoring ParkmobilePMS (transaction logs) from:
D:\LogShipping\LOG_ParkmobilePMS_20060510_093128.sqb

Server: Msg 3013
RESTORE LOG is terminating abnormally.
Server: Msg 3241
The media family on device 'SQLBACKUP_BA0E1D6D-B6A0-476E-A55E-540D2E35B9F5' is incorrectly formed. SQL Server cannot process
this media family.
Server: Msg 3738
Deleting database file 'D:\Microsoft SQL Server\Data\MSSQL\BACKUP\UNDO_ParkmobilePMS.DAT'.

SQL error code: 3738

Comments

  • Options
    peteypetey Posts: 2,358 New member
    Are you by any chance restoring a SQL 2005 file on to a SQL 2000 server?
    Peter Yeoh
    SQL Backup Consultant Developer
    Associate, Yohz Software
    Beyond compression - SQL Backup goodies under the hood, updated for version 8
  • Options
    Destination:
    Microsoft SQL Server 2000 - 8.00.760 (Intel X86) Dec 17 2002 14:22:05 Copyright (c) 1988-2003 Microsoft Corporation Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 4)

    Source:
    Microsoft SQL Server 2000 - 8.00.818 (Intel X86) May 31 2003 16:08:15 Copyright 1988-2003 Microsoft Corporation Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 4)

    Can this last patch be an issue?
  • Options
    peteypetey Posts: 2,358 New member
    Unlikely. Were there any errors reported when the backup file was created?

    I would suggest starting over, using native backups first i.e. make a full backup, followed by a trx log backup, then restore on to the standby server.

    Do run DBCC CHECKDB first on the production database first to ensure everything's in order.
    Peter Yeoh
    SQL Backup Consultant Developer
    Associate, Yohz Software
    Beyond compression - SQL Backup goodies under the hood, updated for version 8
Sign In or Register to comment.