11-02-2011 11:52 PM
Some of our NDMP backups of EMC VNX 5300 are failing when I enable ‘set SNAPSURE=yes’ directive for the file selections. At the same time some backups are successful with the same directive but different volumes.
02/11/2011 2:02:39 PM - requesting resource mol-nbu-01-hcart-robot-tld-0
02/11/2011 2:02:39 PM - requesting resource mol-nbu-01.NBU_CLIENT.MAXJOBS.dr_vnx5300
02/11/2011 2:02:39 PM - requesting resource mol-nbu-01.NBU_POLICY.MAXJOBS.DR_VNX5300-HomeFolders
02/11/2011 2:02:39 PM - granted resource mol-nbu-01.NBU_CLIENT.MAXJOBS.dr_vnx5300
02/11/2011 2:02:39 PM - granted resource mol-nbu-01.NBU_POLICY.MAXJOBS.DR_VNX5300-HomeFolders
02/11/2011 2:02:39 PM - granted resource 0278L4
02/11/2011 2:02:39 PM - granted resource SONY.SDZ-100.003
02/11/2011 2:02:39 PM - granted resource mol-nbu-01-hcart-robot-tld-0
02/11/2011 2:02:40 PM - estimated 223700728 Kbytes needed
02/11/2011 2:02:40 PM - started process bpbrm (452)
02/11/2011 2:02:40 PM - connecting
02/11/2011 2:02:40 PM - connected; connect time: 00:00:00
02/11/2011 2:02:41 PM - mounting 0278L4
02/11/2011 2:03:30 PM - mounted; mount time: 00:00:49
02/11/2011 2:03:40 PM - positioning 0278L4 to file 4
02/11/2011 2:07:39 PM - positioned 0278L4; position time: 00:03:59
02/11/2011 2:07:39 PM - begin writing
02/11/2011 2:09:04 PM - Error ndmpagent(pid=5404) NDMP_LOG_ERROR 0 SnapSure file system creation fails
02/11/2011 2:09:04 PM - Error ndmpagent(pid=5404) read from socket returned -1 10054 (An existing connection was forcibly closed by the remote host.
.)
02/11/2011 2:09:04 PM - Error ndmpagent(pid=5404) MOVER_HALTED unexpected reason = 4 (NDMP_MOVER_HALT_CONNECT_ERROR)
02/11/2011 2:09:04 PM - Error ndmpagent(pid=5404) NDMP backup failed, path = /root_vdm_2/fs3
02/11/2011 2:09:52 PM - end writing; write time: 00:02:13
NDMP backup failure(99)
Is This issue related with sanpshot licensing from EMC box side,Please have a look into the problem and give some solution.
11-03-2011 02:39 AM
You need to check the syslog on the EMC box to see what's going on - use server_log command on the VNX. You can't resolve that issue from the netbackup side.