redundance server site sychronization

[Hongle Sun]

I have a question regarding the directories/ files (./siteinfo ./revisions ./views), which may need to see if they are necessary to be included, while doing the site archive for the redundancy server.

We have two identical boxes (with different IPs) built with same platform and cloverleaf 5.4, and both boxes have production site configured. One serveres as primary and the other as backup or failover box.

We came up an approach to synchronize two boxes by running a cron job daily to tar the all directories and scp to secondary one, by that we can turn manually on the secondary box when the primary one need downtime or some disaster event.

My question is: in our situation, do I need to include (./siteinfo ./revisions ./views) directories in the tar file?

Thanks

Topic

[James Cobane]

Hongle Sun,

We have a different configuration for fail-over.

[Hongle Sun]

Thanks for the reply. What does the revisions directory use for ? I checked the directory and there are lots of timestampled copies of network configure files, table files, xlate files, are they historical file? can I exclude this one beside the exe in the tar file?

[James Cobane]

The revisions directory is where a backup of the previous version of each configuration file is saved when you modify it via the IDE.  i.e. if you modify the Xlate ‘myxlate.xlt’, the IDE creates copy of the previous version in the $HCISITEDIR/revisions/Xlate directory.  This can be useful if you want to compare a configuration to the previous version, or need to troubleshoot what got changed.

Hope this helps.

Jim Cobane

Henry Ford Health

[Author]

Replies