December 12, 2013 at 7:09 pm
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
December 15, 2013 at 3:00 pm
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
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply