2008 R2 mirroring suspended. added a new file on p, drive doesn't exist on m.

  • snomadj

    SSCarpal Tunnel

    Points: 4249

    Foolishly, I did the following:

    Added a new data file on current principal.

    On my mirror the drive letters don't match

    The new file could not be created on mirror.

    Mirror goes into suspended.

    I deleted the new file on principal and attempted to resume but the mirror still needs to create the new file before it can resume.

    I tried to use mapping & subst to trick sql into thinking we temporarily have the r:\ drive, but this didn't work.

    Any other ideas?

    Worst case I will remirror & take the lesson on the chin. But it would be nice to avoid as it's a fairly big DB over a fairly crappy line.

  • rvsc48

    SSCertifiable

    Points: 7187

    Yeah, I am afraid you will have to remove the mirroring and rebuild it.

  • Wayne Sheldon

    SSC-Addicted

    Points: 460

    Don't know if clustering will support it - but how about plugging in a USB drive, and mapping that to drive R.

    Let it re-sync and then remove it again.

  • Perry Whittle

    SSC Guru

    Points: 233784

    snomadj (8/18/2016)


    Foolishly, I did the following:

    Added a new data file on current principal.

    On my mirror the drive letters don't match

    The new file could not be created on mirror.

    Mirror goes into suspended.

    I deleted the new file on principal and attempted to resume but the mirror still needs to create the new file before it can resume.

    I tried to use mapping & subst to trick sql into thinking we temporarily have the r:\ drive, but this didn't work.

    Any other ideas?

    Worst case I will remirror & take the lesson on the chin. But it would be nice to avoid as it's a fairly big DB over a fairly crappy line.

    For future reference, You'd need to take a backup from the principal which includes the new file and restore with move to the mirror

    -----------------------------------------------------------------------------------------------------------

    [font="Tahoma"]"Ya can't make an omelette without breaking just a few eggs"[/font] 😉

  • ahtirah03

    SSC Enthusiast

    Points: 114

    Perry Whittle - Thursday, October 20, 2016 9:36 AM

    snomadj (8/18/2016)


    Foolishly, I did the following:Added a new data file on current principal. On my mirror the drive letters don't match The new file could not be created on mirror.Mirror goes into suspended. I deleted the new file on principal and attempted to resume but the mirror still needs to create the new file before it can resume.I tried to use mapping & subst to trick sql into thinking we temporarily have the r:\ drive, but this didn't work.Any other ideas?Worst case I will remirror & take the lesson on the chin. But it would be nice to avoid as it's a fairly big DB over a fairly crappy line.

    For future reference, You'd need to take a backup from the principal which includes the new file and restore with move to the mirror

    • If the paths differ:

      If the path of the mirror database differs from the path of the principal database (for instance, their drive letters differ), creating the mirror database requires that the restore operation include a MOVE clause.

      Important

      If the path names of the principal and mirror databases differ, you cannot add a file. This is because on receiving the log for the add file operation, the mirror server instance attempts to place the new file in the location used by the principal database.

      For example, the following command restores a backup of a principal database residing in C:\Program Files\Microsoft SQL Server\MSSQL.n\MSSQL\Data\ to a different location, D:\Program Files\Microsoft SQL Server\MSSQL.n\MSSQL\Data\, where the mirror database is to reside.

      RESTORE DATABASE AdventureWorks  FROM DISK='C:\AdventureWorks.bak'  WITH NORECOVERY,   MOVE 'AdventureWorks_Data' TO    'D:\Program Files\Microsoft SQL Server\MSSQL.n\MSSQL\Data\AdventureWorks_Data.mdf',   MOVE 'AdventureWorks_Log' TO    'D:\Program Files\Microsoft SQL Server\MSSQL.n\MSSQL\Data\AdventureWorks_Log.ldf'; GO

Viewing 5 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply