1) May I know what are the backup procedures for a BAO environment? Is there a recommended procedure/sequence on what to backup and restore first ?
(i) For backing up BAO, BMC recommended taking VM backup (preferably) with all the services of ASSO and BAO in stopped state. You can also zip the install directory.
(ii) When taking backup using the install folder archive method, create a copy of the entire peer directory. For example, if you installed your peer in C:/Program Files/BMC Software/BAO/CDP/, create a copy or archive of the "CDP" folder.
To return to a backup version, unarchive your backup in the original directory.
These steps assume your peer has not changed IP addresses or hostnames. Also, when returning to a backup you may need to change any external references to the peer, including but not limited to:
- The Windows service you use to start your peer
- External monitoring tools
- Information within other peers (for example, the URL a Light Activity Peer uses to connect to a Configuration Distribution Peer).
(iii) Regarding sequence of backup and restore, you need to stop all the services of all the components then the VM backup can be taken. Similarly, you can restore the VM snapshot's whenever required. Once restored, bring the components up in the following sequence – ASSO/AM/RSSO, REPO, CDP and lastly other peers.
2) If my repository server with embedded database is down, and I restore the VM to a previous working snapshot, will everything work once it is restored? As in no configuration needed?
Post restore everything should work without any additional configuration required. However make sure the snapshot should be taken with services turned off and before restoring Repo, turn off the CDP as CDP communicates with the Repository. Once Repo is restored, you can start the CDP again.
3) If the repository server is down, will processes still be continued to run? Or processes in BAO is independent whether the repository is up or down?
For BAO version prior to 7.7, Repository must be running for peers to process the workflows. Starting BAO 7.7 and above, this dependency no longer exists with introduction of ASSO/RSSO.