Stfcuno Live DR Action Plan

SHRIRAM TRANSPORT FINANCE COMPANY
STFCUNO Database Migration to DR Site
Preplan Activity
1. Install Sql instance in the server 172.20.24.50 – Instance already Available

172.20.24.50\STFCUNO
2. Application Webconfig need to prepare for the New server in DR with required connection
strings for new instance
3. Create a virtual Ip (XXXXXXX) in NLB for STFCUNO Application in DR and get a public ip and be
prepared with Public Url same as DC
Plan of Action:
1. Application access stoppage (Stop the IIS in App servers)

2. Take the STFCUNO DATABASE Backup in the live server and copy it in safe location
3. Backup scheduled Jobs, User list and linked server list for reference Purpose
4. Take DB table count before movement
5. Check the VERITAS Replication status to secondary sites (eg: NearDR & Belapur)
6. Put DB offline from veritas cluster
7. Check Replication and Q-Marker in HP P9500 CA Replication status
8. DB Movement through HP P9500 Horcm takeover
9. Put DB online from veritas
10. Database Verification & Modification
11. App Movement through Veeam
12. Configuration changes in App
13. URL Redirection
14. Verification
1.Application access stoppage (Stop the IIS in App servers)
Stop the IIS of following STFC Application servers
SOUTH APP1 172.16.17.102
SOUTH APP2 172.16.17.103
SOUTH APP3 172.16.17.107
WEST APP1 172.16.17.104
WEST APP2 172.16.17.105
WEST APP3 172.16.17.108

2.Take the STFCUNO DATABASE Backup in the live server and copy it in safe location
Verify the Backup size and date
Check the database size.

3. Backup scheduled Jobs, User list and linked server list for Security Purpose
Take the screenshot of scheduled jobs, user list and linked server list for security purpose
Check the SQL jobs details

Get the user details

Check the Linked server details

4. Take DB table count before movement
 Take table count in UNOSOUTHWEST DB to verify after migration (get script from DEV Team)
5. Check the VERITAS Replication status to secondary sites (eg: NearDR & Belapur)
Check the VERITAS replication status

6. Put DB offline
Stop the SQL through veritas cluster service
 Offline UNOSTFC-SG
 Offline UNOSTFC-VVR
Deport the Disk Group

7. Check Replication and Q-Marker in HP P9500 CA Replication
Check Storage replication details

Check journal details (Before move confirm the Q-Marker value is same in primary and secondary)
8. DB Movement through HP P9500 Horcm takeover
Switch over the storage replication
Horctakeover –g UNOSOUTHWEST_CA –ICA112 –t 999

Horcm switch over completed.

Check the CA replication primary and secondary volume details.
Now you can able to see PJNN and SJNN swapped in JNLS (Journals) column respectively
pairdisplay –g UNOSOUTHWEST_CA –ICA112 –fxc –v jnlt
And you can verify by P-VOL and S-VOL which will change respectively.
pairdisplay –g UNOSOUTHWEST_CA –ICA112 –fxc

9. Put DB online
 Online UNOSTFC-VVR
 Online UNOSTFC-SG
10. Database Verification & Modification
Check the database size and compare before move and after moved.
Compare and Verify DB user list, user rights, jobs, linked servers and table count
Linked Server Modification as on 08/09/16
 172.16.14.152\STFCARCH ==> 172.20.24.152\STFCARCH

 172.16.16.105\SLICLIFEREP ==> 172.16.16.105\SLICLIFEREP
 172.16.16.172\STFCOMNIDOCS ==> 172.20.26.172\STFCOMNIDOCS
 172.16.16.182\SMS ==> 172.16.16.182\SMS
 172.16.16.42\STFCMOBILE12 ==> 172.20.26.42\STFCMOBILE12
 172.16.16.42\STFCMOBILE ==> 172.20.26.42\STFCMOBILE
 172.16.16.70\STFCHHT ==> 172.16.16.70\STFCHHT
 172.16.17.88\STFCREP ==> 172.20.26.65\STFCREP
 172.18.18.140\CCMS ==> 172.18.18.140\CCMS
 UNOBRS\STFCBRS ==> UNOBRS\STFCBRS
Jobs
Need to give finalized IP list support team will configure accordingly.
App Movement through Veeam

Check the replication in Veeam console whether the data get replicated to DR otherwise start the
replication job to get the latest data get updated
You can check in Jobs -> Replication tab in Veeam Console
Once the replication job completed, start the failover for the UNOSTFC Application servers to take over
DR Replica server as the primary server
This option is available in Replicas -> Ready tab in Veeam Console (do it for 6 App VMs)
Configuration changes in App
Change DC DB to DR DB in web.config file

Stfcuno Live DR Action Plan

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Stfcuno Live DR Action Plan

Uploaded by

Copyright:

Available Formats

SHRIRAM TRANSPORT FINANCE COMPANY

STFCUNO Database Migration to DR Site

1. Install Sql instance in the server 172.20.24.50 – Instance already Available

1. Application access stoppage (Stop the IIS in App servers)

1.Application access stoppage (Stop the IIS in App servers)

Stop the IIS of following STFC Application servers

SOUTH APP1 172.16.17.102

SOUTH APP2 172.16.17.103

SOUTH APP3 172.16.17.107

WEST APP1 172.16.17.104

WEST APP2 172.16.17.105

WEST APP3 172.16.17.108

Verify the Backup size and date

Check the database size.

Check the SQL jobs details

Get the user details

Check the Linked server details

4. Take DB table count before movement

Check the VERITAS replication status

Stop the SQL through veritas cluster service

Deport the Disk Group

7. Check Replication and Q-Marker in HP P9500 CA Replication

Check Storage replication details

8. DB Movement through HP P9500 Horcm takeover

Switch over the storage replication

Horctakeover –g UNOSOUTHWEST_CA –ICA112 –t 999

Horcm switch over completed.

Check the CA replication primary and secondary volume details.

pairdisplay –g UNOSOUTHWEST_CA –ICA112 –fxc –v jnlt

pairdisplay –g UNOSOUTHWEST_CA –ICA112 –fxc

10. Database Verification & Modification

Linked Server Modification as on 08/09/16

 172.16.14.152\STFCARCH ==> 172.20.24.152\STFCARCH

Need to give finalized IP list support team will configure accordingly.

App Movement through Veeam

You can check in Jobs -> Replication tab in Veeam Console

Configuration changes in App

Change DC DB to DR DB in web.config file

You might also like