Hello,
We are having an on going issue when trying to backup a large VM.
Our setup is as follows.
Master: Virtual Server 2008 R2 Netbackup 7.6.0.2
Media Server/Backup Proxy: IBM 3650 M4 with Server 2008 R2 Netbackup 7.6.0.2
ESX hosts IBM 3550M4 running ESXi5.1 (Kernal 2323236)
Storge: IBM DS3500 SAS Attached
Issue:
We have a large 2008R2 VM that is currentently using 12.78TB used out of 29.05 allocated. The server houses very large image files that are GBs in size each.
We are unable to perform a complete back up this server using SAN transport. It fails on an error 6, Here is the txt from activity monitor.
3/24/2015 1:58:00 PM - Info nbjm(pid=4484) starting backup job (jobid=423561) for client EPNSMS01, policy NewStanton_MS01_Data, schedule Weekly_Full
3/24/2015 1:58:00 PM - Info nbjm(pid=4484) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=423561, request id:{8BF9ACC0-1B65-4749-9FF0-F3EE1B6FFE3B})
3/24/2015 1:58:00 PM - requesting resource epnsbms02-hcart2-robot-tld-7
3/24/2015 1:58:00 PM - requesting resource epenbms01.NBU_CLIENT.MAXJOBS.EPNSMS01
3/24/2015 1:58:00 PM - requesting resource epenbms01.NBU_POLICY.MAXJOBS.NewStanton_MS01_Data
3/24/2015 1:58:00 PM - granted resource epenbms01.NBU_CLIENT.MAXJOBS.EPNSMS01
3/24/2015 1:58:00 PM - granted resource epenbms01.NBU_POLICY.MAXJOBS.NewStanton_MS01_Data
3/24/2015 1:58:00 PM - granted resource 045ACP
3/24/2015 1:58:00 PM - granted resource IBM.ULT3580-HH5.000
3/24/2015 1:58:00 PM - granted resource epnsbms02-hcart2-robot-tld-7
3/24/2015 1:58:00 PM - estimated 0 Kbytes needed
3/24/2015 1:58:00 PM - Info nbjm(pid=4484) started backup (backupid=EPNSMS01_1427219880) job for client EPNSMS01, policy NewStanton_MS01_Data, schedule Weekly_Full on storage unit epnsbms02-hcart2-robot-tld-7
3/24/2015 1:58:01 PM - started process bpbrm (1368)
3/24/2015 1:58:04 PM - Info bpbrm(pid=1368) EPNSMS01 is the host to backup data from
3/24/2015 1:58:04 PM - Info bpbrm(pid=1368) reading file list for client
3/24/2015 1:58:04 PM - Info bpbrm(pid=1368) starting bpbkar32 on client
3/24/2015 1:58:04 PM - Info bpbkar32(pid=1048) Backup started
3/24/2015 1:58:04 PM - connecting
3/24/2015 1:58:04 PM - connected; connect time: 0:00:00
3/24/2015 1:58:04 PM - Info bpbkar32(pid=1048) archive bit processing:<enabled>
3/24/2015 1:58:04 PM - Info bptm(pid=4504) start
3/24/2015 1:58:05 PM - Info bptm(pid=4504) using 65536 data buffer size
3/24/2015 1:58:05 PM - Info bptm(pid=4504) setting receive network buffer to 263168 bytes
3/24/2015 1:58:05 PM - Info bptm(pid=4504) using 30 data buffers
3/24/2015 1:58:06 PM - Info bptm(pid=4504) start backup
3/24/2015 1:58:06 PM - Info bptm(pid=4504) Waiting for mount of media id 045ACP (copy 1) on server epnsbms02.
3/24/2015 1:58:06 PM - mounting 045ACP
3/24/2015 1:58:46 PM - Info bptm(pid=4504) media id 045ACP mounted on drive index 0, drivepath {10,0,0,0}, drivename IBM.ULT3580-HH5.000, copy 1
3/24/2015 1:58:47 PM - mounted; mount time: 0:00:41
3/24/2015 1:58:47 PM - positioning 045ACP to file 17
3/24/2015 2:00:49 PM - positioned 045ACP; position time: 0:02:02
3/24/2015 2:00:49 PM - begin writing
3/24/2015 2:55:22 PM - Info bpbkar32(pid=1048) bpbkar waited 0 times for empty buffer, delayed 0 times.
3/24/2015 2:56:57 PM - Error bpbrm(pid=1368) could not send server status message
3/24/2015 2:56:58 PM - Critical bpbrm(pid=1368) unexpected termination of client EPNSMS01
3/24/2015 2:56:58 PM - Info bpbkar32(pid=0) done. status: 6: the backup failed to back up the requested files
3/24/2015 2:56:58 PM - end writing; write time: 0:56:09
the backup failed to back up the requested files(6)
Observations:
- It will backup if the transport method is set to NBT (takes too long to be a solution)
- We did have some succes a few weeks ago with the following settings using SAN (no longer works)
- Backing only the C drive with quiescing disabled
- Backing only the data drive with quiescing disabled
- Its not an issue with the media server seeing the datastore as other VMs backup with SAN transport without problem
I see nothing in documentation that says the VM is too big and other than the size, the configuration of the VM is no different than any other we have.
We've had multiple requests open with both VMWare and Symantec and we don't see to get any real feedback.
Anyone else have a suggestion?