Upcoming job

VMware specific discussions

Upcoming job

Veeam Logoby marius roma » Thu Jul 21, 2016 7:23 am

A replica job uses a slow line to replicate a single VM.
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?
Regards
marius
marius roma
Expert
 
Posts: 317
Liked: 3 times
Joined: Wed Feb 01, 2012 12:04 pm
Full Name: Mario

Re: Upcoming job

Veeam Logoby foggy » Thu Jul 21, 2016 10:11 am

Mario, first of all, does this replication job use backup file as a source?
foggy
Veeam Software
 
Posts: 14752
Liked: 1083 times
Joined: Mon Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson

Re: Upcoming job

Veeam Logoby marius roma » Thu Jul 21, 2016 10:51 am

Yes, it does
marius roma
Expert
 
Posts: 317
Liked: 3 times
Joined: Wed Feb 01, 2012 12:04 pm
Full Name: Mario

Re: Upcoming job

Veeam Logoby foggy » Thu Jul 21, 2016 11:49 am

The replica restore point created at the time when job was terminated will be inconsistent (while previous replica restore points will be ok) and will be resumed during the next replication job run.
foggy
Veeam Software
 
Posts: 14752
Liked: 1083 times
Joined: Mon Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson

Re: Upcoming job

Veeam Logoby marius roma » Thu Jul 21, 2016 12:50 pm

So the good way is scheduling the replica to keep at least 2 restore points at the target site, is it correct?
Regards
Marius
marius roma
Expert
 
Posts: 317
Liked: 3 times
Joined: Wed Feb 01, 2012 12:04 pm
Full Name: Mario

Re: Upcoming job

Veeam Logoby foggy » Thu Jul 21, 2016 12:53 pm

It is always a best practice to have more than one restore point, regardless of whether it is replica or backup. With just a single restore point retention you're at risk to be left without any of them at all.
foggy
Veeam Software
 
Posts: 14752
Liked: 1083 times
Joined: Mon Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson


Return to VMware vSphere



Who is online

Users browsing this forum: No registered users and 19 guests