I have read the various posts about DR setup just want to make sure our strategy is correct:
2 servers one is production (PR) the other is disaster (DR). Basically if the PR server fails then users will use DR.
Our DR procedure is to:
replicate the PR filestore to DR server every hour
the PR CMS/AUDIT DBs are backed up, in a disaster scenario we will restore them on DR. Before we do that we will make sure the SIA on PR is turned off otherwise clustering will occur.
if PR is down and we use DR to create reports/universes when PR is up again do we do the reverse i.e. copy the filestore from DR to PR. Backup the CMS/AUDIT DBs on DR > turn off DR SIA and restore the DBs on PR?
Currently PR is working fine so should the SIA on DR be stopped seeing it will only be used when PR is down? Is it a good practice when one server is up (PR) to shut the SIA of the other (DR) down?
when the data is restored on DR will all the security settings/permissions on folders/universes etc be the same as PR?
If possible, my recommendation is to use cold back up i.e. SIA is Shutdown. This is to prevent unsynce between filestores and CMS DB. Also, a daily back up should be enough. In my case, it takes an hour to copy filestore already (PR & DR are on different site) so it will definitely consume your bandwidth.
According to your procedure
[i]- replicate the PR filestore to DR server every hour
the PR CMS/AUDIT DBs are backed up, in a disaster scenario we will restore them on DR. Before we do that we will make sure the SIA on PR is turned off otherwise clustering will occur.[/i]
Make sure that CMS and Filestores are in sync.
* if PR is down and we use DR to create reports/universes when PR is up again do we do the reverse i.e. copy the filestore from DR to PR. Backup the CMS/AUDIT DBs on DR > turn off DR SIA and restore the DBs on PR?
You should shout down SIA on DR before restore filestores and CMS DB back to PR.
Yes, the security information is stored in CMS DB, hence they will be the same.
(BOB member since 2008-10-09)