SooHow Cheng
asked on
Why the NetBackup has to take more than 24 hours to backing up the VM?
This is using Veritas NetBackup 8.11. We also using HP Simplivity VMware virtualization. There is a MS Windows VM server having about 700GB in size, in the report, has to take more than 24 hours to complete the snapshot and backup.
However, we checked the VMware web portal and found that the snapshot creation only took few second to complete. The snapshot removal and other jobs completed successfully shown in this VMware portal.
Just confuse why the snapshot and backup image have to take so long to complete. How is the whole process work? Where to look into to solve the problem?
Thanks in advance.
However, we checked the VMware web portal and found that the snapshot creation only took few second to complete. The snapshot removal and other jobs completed successfully shown in this VMware portal.
Just confuse why the snapshot and backup image have to take so long to complete. How is the whole process work? Where to look into to solve the problem?
client | Job Type | Job Schedule | Job State | Job Status | Job Start Time | Job End Time | Job Duration (hr) | Job Size (KB) | Job Throughput (kb/sec) |
ssinsplunkhf01 | Backup | Full_Backup | Done | 0 | 23.05.2021 12:35:53 | 24.05.2021 00:44:18 | 12:08:25 | 733843900 | 16820 |
ssinsplunkhf01 | Snapshot | - | Done | 0 | 23.05.2021 12:35:42 | 24.05.2021 00:44:38 | 12:08:56 |
Thanks in advance.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Adding to my earlier comment, why are you starting the backup during the day. Presumably this will be peak utilization time.
See if changing ti to start at 8 pm as an example and have it complete by 8 am the following day Additional benefit you will capture all the data for that day in the backup.
See if changing ti to start at 8 pm as an example and have it complete by 8 am the following day Additional benefit you will capture all the data for that day in the backup.
But 16 MB/s is not really a lot..., as far as no other jobs running at the same time...
Would be interesting if the throughput raises if you move the start time to 8:00 pm
Would be interesting if the throughput raises if you move the start time to 8:00 pm
Job throughput seems a bit low. WIth that throughout the total time of 12 hours to complete the job is expected and there is nothing unusual. I suggest starting the job at a time when nobody works. It should reduce the total time. You can also reconfigure your backups to perform only incremental backups during the week if you haven't done it already.
ASKER
Yes, is correct, no problem.
It is a 12 hour transaction.
Step one create a snapshot after recording start of job
Step two, transfer snapshot to backup storage after recording start of job
Step three complete transfer, and Mark transfer complete
Step four deleted snapshot, and Mark task complete.
Note date/time info.