Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

How to trick Mirror? Expand / Collapse
Author
Message
Posted Thursday, December 12, 2013 7:09 PM
SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Sunday, April 20, 2014 5:18 PM
Points: 424, Visits: 1,544
This weekend we are moving standalone sql server (SS) (2008R2 64 bit Ent) to 2 node cluster (CS).
Current server has 34 DBs (total size is around 700 GB), all DBs are mirrored to DR server, 10 DBs- replicated to Report server. To speed up coping data from SS to CS we set up (temporally) LogShipping, i.e. Sunday night we copy/restore last TrLog backup and will recover DBs (Cluster Name/IP will be the same as for SS)
Sorry for long introduction- just to make clear my question

After we test failover we need to reconfigure Replication/Mirror from scratch- is this true?

Can we somehow trick Mirror server? Let say apply last transaction to Mirror and .. Not sure what to do to avoid complete Mirror reconfiguring (Full backup/restore/etc)- takes some time we would like to save.
Seems like Replication trick does not work- we tried in UAT (may be did something wrong?), but Mirror?

To resume: generally speaking- moving Principal (while keeping same Name/IP) to another server-
can we avoid complete Mirror reconfiguring?

Thanks
Post #1522542
Posted Sunday, December 15, 2013 3:00 PM
SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Sunday, April 20, 2014 5:18 PM
Points: 424, Visits: 1,544
Eventually found solution (implemented today in Prod)- may be somebody will also use it

1) put DB in Restricted_User mode;
2) break mirror- on Mirror side DB will be in Restoring state
3) copy/bring DB online on new Cluster server (node1)
4) do whatever needs to be done to setup DB on new Cluster server (Multi_User/Node2/failover/etc)
5) back to mirror setup- Restricted _User again/ take TrLog backup
6) restore on Mirror all (after move) TrLog backups with NoRecovery
7) reconfigure Mirror

We saved around 10h of limited time avoiding new Full backup on Principal/restore on Mirror
Post #1523067
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse