dcabro
ADSM.ORG Member
- Joined
- Mar 28, 2014
- Messages
- 37
- Reaction score
- 2
- Points
- 0
I have successfully installed & configured DP for VE (8.1.6) on Hyper-V active-active cluster.
Nodes:
1. HOST1_DM
2. HOST2_DM
3. CLUSTER_NODE
CLUSTER node is a proxy target for HOST1_DM and HOST2_DM.
There are two schedules. One that's doing all but one VM (let's call it CRITICAL) incremental backup daily. Second schedule that's doing one hour backup of that one CRITICAL VM and has only CRITICAL VM defined in schedule.
Both schedules are associated with HOST1_DM and HOST2_DM.
Since the CRITICAl VM is running on only one host, there's a failed schedule status for node not hosting the VM. Note that CRITICAL VM should be able to jump back and forth between the hosts.
The question is - how to prevent this failed status?
Can it be done in any other way?
I'd like to avoid having a task scheduler in Windows because of two things:
1. I would also have one failed schedule (unless windows scheduler can be defined in such a way that it will "know" if this CRITICAL VM is present in which case it should run the task, or if it isn't should do nothing). But still, there's this next thing:
2. I would not know if it fails - or I would have to log in to each host every day to check the status. For this reason, I'd like to have TSM central scheduler if possible.
Thanks!
Nodes:
1. HOST1_DM
2. HOST2_DM
3. CLUSTER_NODE
CLUSTER node is a proxy target for HOST1_DM and HOST2_DM.
There are two schedules. One that's doing all but one VM (let's call it CRITICAL) incremental backup daily. Second schedule that's doing one hour backup of that one CRITICAL VM and has only CRITICAL VM defined in schedule.
Both schedules are associated with HOST1_DM and HOST2_DM.
Since the CRITICAl VM is running on only one host, there's a failed schedule status for node not hosting the VM. Note that CRITICAL VM should be able to jump back and forth between the hosts.
The question is - how to prevent this failed status?
Can it be done in any other way?
I'd like to avoid having a task scheduler in Windows because of two things:
1. I would also have one failed schedule (unless windows scheduler can be defined in such a way that it will "know" if this CRITICAL VM is present in which case it should run the task, or if it isn't should do nothing). But still, there's this next thing:
2. I would not know if it fails - or I would have to log in to each host every day to check the status. For this reason, I'd like to have TSM central scheduler if possible.
Thanks!
