11-25-2014 12:54 AM
Solved! Go to Solution.
11-26-2014 06:12 AM
I see. Well it could be a bug in Netbackup client service. Please update to NBU 7.6.0.4
Here is the bug report TECHNOTE:
http://www.symantec.com/business/support/index?page=content&id=TECH223790
11-25-2014 10:03 AM
It depends on what you mean by "idle". The first step is snapshot creation. Then the backup begins. The backup is actually a seperate JOB ID. It's a "child job". The "backup" operation is the process of copying the snapshot to the destination specified in the policy. The backup step will take much longer than the snapshot step.
11-25-2014 11:13 PM
I' know the step. If i see event on vcenter, i see make and remove snapshot but job stay idle infinity until i kill process. For example, a job start on friday and on monday still running but do nothing.
11-26-2014 06:12 AM
I see. Well it could be a bug in Netbackup client service. Please update to NBU 7.6.0.4
Here is the bug report TECHNOTE:
http://www.symantec.com/business/support/index?page=content&id=TECH223790
11-27-2014 01:49 AM
11-27-2014 05:55 AM
The meida server you use as the VM backup host just needs to be up to the correct patch level with the master server.
The Netbackup appliance is just a media server. It's a good option if you need a deduplicated disk pool but it won't help you with VMWare. The main benefits are not having to configure a dedupe disk pool and better support. It comes with a monitoring service and they support the hardware too.