The same VM is backed up by another job, scheduled to start after the replica job.
In the night the replica job stopped with the messages I include:
- Code: Select all
20/07/2016 15:02:57 :: Discovering replica VM
20/07/2016 15:04:43 :: Processing configuration
20/07/2016 15:06:29 :: Creating helper snapshot
20/07/2016 15:06:47 :: Using target proxy <IP Address> for disk Hard disk 1 [hotadd]
20/07/2016 15:07:41 :: Network traffic throttling is enabled
20/07/2016 15:08:34 :: Hard disk 1 (110,0 GB) 1,9 GB read at 105 KB/s
20/07/2016 20:25:42 :: Error: Stopped by job '<Backup job name>' (Backup)
20/07/2016 20:25:42 :: Busy: Source 0% > Proxy 7% > Network 99% > Target 0%
20/07/2016 20:25:42 :: Primary bottleneck: Throttling
20/07/2016 20:25:42 :: Network traffic verification detected no corrupted blocks
20/07/2016 20:25:43 :: Processing finished with errors at 20/07/2016 20:25:42
Does it mean that the replica job was stopped by the backup job?
If so, should I presume that the replica VM is in a not consistent state?
Given that the backup is more important than the replica, what should I do to make the replica terminate and leave the replica VM in a consistent state AFTER the backup is complete?