Avinash Chandra Mandavilli
asked on
AS400 Queries
What is the difference between SAVLIB for *NONSYS, *IBM and *ALLUSR?
How do we do complete disaster recovery test? Just need sample example with steps
Why should we need to run UPTPTDINF during a complete system recovery after library QGPL has been restored
Why do we install PTF? What are the difference between cummulative, group and Hyper PTF
How do we do complete disaster recovery test? Just need sample example with steps
Why should we need to run UPTPTDINF during a complete system recovery after library QGPL has been restored
Why do we install PTF? What are the difference between cummulative, group and Hyper PTF
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I'm not Theo, but as I said above THERE IS NO ONE SIMPLE ANSWER.
It depends on how your DR process was designed and implemented. It depends on what you are and are not replicating. It may depend on your network and DNS setup. There is no way anyone can tell you how to revert to your DR system without careful inspection (and testing) of the configuration and state of each system.
For example, I have one client with a very, very simple DR setup (data-only replication). To revert to the DR system, they have to:
1) Restore a set of specific libraries and objects to the DR system from specific backups.
2) Enable a set of batch scheduled jobs (some are application-specific) on the DR system.
3) Start a number of services (some are application-specific) on the DR system.
4) Start production subsystems and print writers on the DR system.
5) Change DNS for the production system to point to the IP of the DR system.
6) Restart specific services running on other systems to force them to pick up the new IP address from DNS.
Your list will probably be different, but those are examples of some possible actions. If you don't have a written DR process, you really need to figure it out and create one. If you don't have adequate skills in-house to develop a written DR process, you should probably bring in an expert to help you.
It depends on how your DR process was designed and implemented. It depends on what you are and are not replicating. It may depend on your network and DNS setup. There is no way anyone can tell you how to revert to your DR system without careful inspection (and testing) of the configuration and state of each system.
For example, I have one client with a very, very simple DR setup (data-only replication). To revert to the DR system, they have to:
1) Restore a set of specific libraries and objects to the DR system from specific backups.
2) Enable a set of batch scheduled jobs (some are application-specific) on the DR system.
3) Start a number of services (some are application-specific) on the DR system.
4) Start production subsystems and print writers on the DR system.
5) Change DNS for the production system to point to the IP of the DR system.
6) Restart specific services running on other systems to force them to pick up the new IP address from DNS.
Your list will probably be different, but those are examples of some possible actions. If you don't have a written DR process, you really need to figure it out and create one. If you don't have adequate skills in-house to develop a written DR process, you should probably bring in an expert to help you.
I am, and agree with that :-)
ASKER
Suppose if you have HA tool in place for the systems from PROD to DR , how do follow DR to PROD if unexpected circumstances occurs to PROD ?
Regards
Avinash Chandra