Netbackup 7.6.1.1 vmware problems with CBT option
Master/Media : Symantec Appliance 5220 version 7.6.1.1 upgraded recently
Client: Vmware client ( ESX version 5.5 ). Vmware tools installed .
Problem description:
We are added recently several vmware clients and all of them have the same problem.
They have accelerator option enabled.
They have 3 schedules defined:
1.- first full backup with forced rescan option enabled ( with frecuency repetition of 15 weeks )
2.- Incremental backups for every day
3.- Full backup every week
First full backup ( with rescan) and following days work properly with optimization near 100% of accelerator ratio.
But suddenly one day the backup shows this message
"There is no complete backup image match with track journal, a regular full backup will be performed."
and accelerator ratio is 0%, so the backup is like a full ( so CBT is not working )
We opened a support question and they told us a workaround to solve it, but this process is manual:
1) Disable accelerator in the attributes tab
2) Run a full backup without accelerator
3) Check accelerator and run a full backup with accelerator.
4) Run incremental.
This workaround works, and next backups are doing well again with an accelerator ratio near 100%.
But we had to do two backups full for each vmware server, with much volume of backup.
But after a few weeks the problem is repeated and we got again the same message:
"There is no complete backup image match with track journal, a regular full backup will be performed." .
We are planning to add hundreds of vmware clients and if we need to apply this workaround every time is
a work very tedius.
Anybody know what is the cause of the problem and why can we to avoid these errors?
Thanks in advance,
regards.
Lola Recio.
Here is a complete trace of the backup:
03/18/2015 00:38:55 - Info nbjm (pid=9084) starting backup job (jobid=373438) for client ow-atp, policy xxxxx.VMware.dylan4.pol, schedule xxxxx.VMware.polincr
03/18/2015 00:38:55 - estimated 67241650 kbytes needed
03/18/2015 00:38:55 - Info nbjm (pid=9084) started backup (backupid=xxxxxx_1426635535) job for client xxxxx, policy xxxxx.VMware.pol, schedule xxxxx.VMware.polincr on storage unit stu_disk_dylan4 using backup host yyyy
03/18/2015 00:38:55 - started process bpbrm (pid=22923)
03/18/2015 00:38:55 - Info bpbrm (pid=22923) xxxxx is the host to backup data from
03/18/2015 00:38:55 - Info bpbrm (pid=22923) reading file list for client
03/18/2015 00:38:56 - Info bpbrm (pid=22923) accelerator enabled
03/18/2015 00:38:56 - Info bpbrm (pid=22923) There is no complete backup image match with track journal, a regular full backup will be performed.
03/18/2015 00:38:56 - Info bpbrm (pid=22923) starting bpbkar on client
03/18/2015 00:38:56 - Info bpbkar (pid=22936) Backup started
03/18/2015 00:38:56 - Info bpbrm (pid=22923) bptm pid: 22938
03/18/2015 00:38:56 - Info bptm (pid=22938) start
03/18/2015 00:38:56 - Info bptm (pid=22938) using 262144 data buffer size
03/18/2015 00:38:56 - Info bptm (pid=22938) using 128 data buffers
03/18/2015 00:38:56 - connecting
03/18/2015 00:38:56 - connected; connect time: 0:00:00
03/18/2015 00:38:57 - Info bptm (pid=22938) start backup
03/18/2015 00:39:00 - begin writing
03/18/2015 00:39:57 - Info bpbkar (pid=22936) INF - Transport Type = nbd
03/18/2015 01:03:14 - Info bpbkar (pid=22936) accelerator sent 57570284544 bytes out of 57570283008 bytes to server, optimization 0.0%
03/18/2015 01:03:14 - Info bpbkar (pid=22936) bpbkar waited 1 times for empty buffer, delayed 791 times
03/18/2015 01:03:14 - Info bptm (pid=22938) waited for full buffer 65609 times, delayed 92625 times
03/18/2015 01:03:17 - Info bptm (pid=22938) EXITING with status 0 <----------
03/18/2015 01:03:17 - Info dylan4 (pid=22938) StorageServer=PureDisk:yyyy; Report=PDDO Stats (multi-threaded stream used) for (yyyy): scanned: 56226368 KB, CR sent: 16742141 KB, CR sent over FC: 0 KB, dedup: 70.2%, cache disabled
03/18/2015 01:03:17 - Info bpbrm (pid=22923) validating image for client xxxxx
03/18/2015 01:03:18 - Info bpbkar (pid=22936) done. status: 0: the requested operation was successfully completed
03/18/2015 01:03:18 - end writing; write time: 0:24:18
the requested operation was successfully completed (0)
Symante recommend not mixing frequency and calendar based backup in the same policy. I know a lot of user are saying it work fine. But for the sake of problem resolving can you change the schedule XXXXX.VMware.polfull to calender as well.