Hi,
Per Henrik's second comment above, If you don't have/want VC in a Cluster situation, I suggest you setup some jobs in visualcron.
We have a 'Passive' Server <running other services in addition to backup VC> in a separate facility which we push backups:
- Server Settings
- Logs
- Output Database
<for us originally every 5 now every 15 minutes> from the Primary.
It is running & has a VC License (and we monitor the VC Service). We would not *assume* we can deactivate the other license and did not want to worry about licensing / installations in the event of an issue.
We do our Firewall setup at a group level for Both the Primary and Secondary Server together.
Not Perfect, but depends what your RTO & RPO obligations are <and your Job volatility !>.
Periodically we import those jobs onto the passive side (and have most of them inactivated) though there is no need to do this pre DR (other than the necessary testing of course !).
A shared / cluster infrastructure obviously has some big Pro's (along with the complexity) but we have opted for separate as it also assists in managing the fairly frequent rollout of software updates (Windows, VisualCron, and others) allowing us to stagger changes / switch Primary if we need to.
Edited by user
2013-05-06T02:54:07Z
|
Reason: Not specified