Comprehensive data protection for all workloads
Post Reply
crackocain
Service Provider
Posts: 240
Liked: 27 times
Joined: Dec 14, 2015 8:20 pm
Full Name: Mehmet Istanbullu
Location: Türkiye
Contact:

Feature request: VM Backup finish time in summary screen

Post by crackocain »

Hi everyone

It is very difficult to calculate the backup or replication time of one VM in a backup task that include multiple virtual machines.
For example: VM backup waits 178 hours to start.
Replication window starts at 1/1/2019 6:12:41 AM
Finished 1/1/2019 1:18:37 PM

How am i know the real backup/replication window time one VM? Because i need to know this duration.
I can take these two dates apart, but a very amateurish solution. I think this duration should be displayed on the screen.

Queued for processing at 12/24/2018 7:52:53 PM
Required backup infrastructure resources have been assigned 178:19:45
VM processing started at 1/1/2019 6:12:41 AM
VM size: 4.7 TB
Discovering replica VM 00:00
Getting VM info from vSphere 00:06
Creating VM snapshot 00:10
Preparing replica VM 00:05
Processing configuration 00:08
Creating helper snapshot 00:06
Using source proxy XX.XX.XX.XX for disk Hard disk 1 [hotadd] 00:35
Using target proxy XX.XX.XX.XX for disk Hard disk 1 [hotadd]
Hard disk 1 (81.0 GB) 733.0 MB read at 10 MB/s [CBT] 01:22
Using source proxy XX.XX.XX.XX for disk Hard disk 2 [hotadd] 00:31
Using target proxy XX.XX.XX.XX for disk Hard disk 2 [hotadd]
Hard disk 2 (600.0 GB) 7.7 GB read at 16 MB/s [CBT] 08:22
Using source proxy XX.XX.XX.XX for disk Hard disk 4 [hotadd] 00:32
Using target proxy XX.XX.XX.XX for disk Hard disk 4 [hotadd]
Hard disk 4 (3.0 TB) 285.4 GB read at 26 MB/s [CBT] 03:11:09
Using source proxy XX.XX.XX.XX for disk Hard disk 3 [hotadd] 00:33
Using target proxy XX.XX.XX.XX for disk Hard disk 3 [hotadd]
Hard disk 3 (1.1 TB) 977.4 GB read at 81 MB/s [CBT] 03:26:09
Removing VM snapshot 08:57
Deleting helper snapshot 00:13
Deleted file blocks skipped: 3.1 GB
Finalizing 00:00
Busy: Source 7% > Proxy 36% > Network 70% > Target 33%
Primary bottleneck: Network
Network traffic verification detected no corrupted blocks
Processing finished at 1/1/2019 1:18:37 PM
Mike Resseler
Product Manager
Posts: 8044
Liked: 1263 times
Joined: Feb 08, 2013 3:08 pm
Full Name: Mike Resseler
Location: Belgium
Contact:

Re: Feature request: VM Backup finish time in summary screen

Post by Mike Resseler »

Hi Crackocain,

If there are multiple VMs inside a replication job, then the amount of time needed per VM can be seen in the main log window. Make sure none of the VMs is "selected" in the statistics window. It will take that Required backup infrastructure resources have been assigned into account. Because it is part of the entire time it needed to perform the job. So what worries me here is why it needs those 178 hours+ to be honest.

I think I understand your request (you want to know how long it takes to process the VM without the waiting for resources time) but from our point of view, this is a part of the processing. If resources are not ready and not including that time (in my opinion) would give a false result? Or do you see other reasons to not include that time?

Let us know
Mike
crackocain
Service Provider
Posts: 240
Liked: 27 times
Joined: Dec 14, 2015 8:20 pm
Full Name: Mehmet Istanbullu
Location: Türkiye
Contact:

Re: Feature request: VM Backup finish time in summary screen

Post by crackocain »

Hi Mike

Actually we have 3 replication jobs, replicating different datastore. 50 VM's replicating. And 3 replication proxy for this jobs.

I start first replication cycle. That's why it wait 178 hours. Bandwidth around 50Mbits. So if i'm add more proxy it's useless. Because bandwitdh limits.

In such scenarios, the expected time for the proxy to be ready can confuse. Because always there will be a little waiting. Actually 1 hour or 20 not much different. For example if i'm add more proxy, replication cycle starts early but too many snapshot created and backup jobs take a long time, like before. Actually still waiting if I'm doubling up bandwidth. 1 hours waiting drops 30 minutes.

Thank you so much :)

If I'm not selected VM's this is looks like. 185 hours :)

Job started at 12/24/2018 7:52:21 PM
Building VMs list 00:04
VM size: 10.0 TB
Changed block tracking is enabled
Processing VM1 179:23:07
Processing VM2 185:25:38
Processing VM3 Error: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond XX:XX:XX:XX 17:52:09
All VMs have been queued for processing 00:00
1 restore point removed by retention policy from VM1_replica 14:44
1 restore point removed by retention policy from VM2_replica 00:27
Load: Source 3% > Proxy 23% > Network 84% > Target 19%
Primary bottleneck: Network
Job finished with error at 1/2/2019 12:19:42 AM
Mike Resseler
Product Manager
Posts: 8044
Liked: 1263 times
Joined: Feb 08, 2013 3:08 pm
Full Name: Mike Resseler
Location: Belgium
Contact:

Re: Feature request: VM Backup finish time in summary screen

Post by Mike Resseler »

I think, from what I can see, that your proxies are all working and don't get a cycle. You might want to check how many concurrent tasks they are allowed to handle. And also to see if they are busy with another job at the same time.
crackocain
Service Provider
Posts: 240
Liked: 27 times
Joined: Dec 14, 2015 8:20 pm
Full Name: Mehmet Istanbullu
Location: Türkiye
Contact:

Re: Feature request: VM Backup finish time in summary screen

Post by crackocain »

Yes one concurrent job for each proxy. I want it to end as soon as VM snapshot is taken.
Mike Resseler
Product Manager
Posts: 8044
Liked: 1263 times
Joined: Feb 08, 2013 3:08 pm
Full Name: Mike Resseler
Location: Belgium
Contact:

Re: Feature request: VM Backup finish time in summary screen

Post by Mike Resseler »

The snapshot will be removed when one taks is completed, so I would up the concurrent jobs to the default (I believe that is 4) and see the difference
Post Reply

Who is online

Users browsing this forum: Bing [Bot], Google [Bot] and 173 guests