09-09-2014 08:39 AM
Hello all
NBU 5200 Appliance Version: 2.5.1, Appliance Version: 2.5.1 2 appliances at same version.
scenario: i added a windows server CLIENT1(uppercase) to a test policy backup ran for 20 mins then I had to cancel it due to some other activity. then i added in another policy as client1(lower case), next day backup ran as per its schedule. backup completed but duplication fails. duplication step is via SLP. NBU 5200 to NBU 5200 replication. rest all back up images are replicated without any problem. only this one hav problem.
Hence first backup completed with a lower case name.
NBU GUI catalog shows 2 backup images dated 8th and 9th
at path /disk/databases/catalog/2 i see folder client1 in lower case -- policy name folder --then .img, .info .hdr files
GUI logs:
09/09/2014 16:56:58 - begin writing
09/09/2014 16:56:58 - end writing; write time: 0:00:00
09/09/2014 16:57:05 - Critical bpdm (pid=27075) get image properties failed: error 2060013: no more entries
09/09/2014 16:57:05 - Critical bpdm (pid=27075) Invalid image copy: error 2060013
09/09/2014 16:57:06 - Critical bpdm (pid=27075) get image properties failed: error 2060013: no more entries
09/09/2014 16:57:08 - begin writing
09/09/2014 16:58:38 - end writing; write time: 0:01:30
09/09/2014 16:58:40 - Critical bpdm (pid=27075) sts_close_handle failed: 2060022 software error
09/09/2014 16:58:46 - Error bpduplicate (pid=46840) host mediaserver backup id client_1410263734 optimized duplication failed, media write error (84).
09/09/2014 16:58:46 - Info mediaserver (pid=27075) StorageServer=PureDisk:mediaserver; Report=PDDO Stats for (mediaserver): scanned: 40698795 KB, CR sent: 22587 KB, CR sent over FC: 0 KB, dedup: 99.9%
09/09/2014 16:58:47 - Error bpduplicate (pid=46840) Duplicate of backupid client_1410263734 failed, media write error (84).
09/09/2014 16:58:47 - Error bpduplicate (pid=46840) Status = no images were successfully processed.
09-09-2014 05:34 PM
Most likey this issue: http://www.symantec.com/docs/TECH207194
2.5.1 has that issue, upgrade to at least 2.5.3.
09-09-2014 09:50 PM
Yip, agree with watsons. Just add the link for now, and then upgrade. 2.5.1 is really old.
09-11-2014 02:31 AM
That is a heck of a tech note!!
Just go into the O/S of the appliance (Support - Maintenance - P@ssw0rd - elevate)
cd to /disk/databases/catalog/2
then type:
ls -s client1 CLIENT1
Re-start NetBackup on the appliance and then see if the duplication works
But do upgrade as soon as you can
10-14-2014 03:58 AM
Mark, where I need to run ln -s client1 CLIENT1 ?
source NBU appliance or destination NBU appliance ?
10-14-2014 04:01 AM
On which ever server the client's name doesn't look right. Both servers should match
10-14-2014 06:55 AM
i ran command on both NBU appliances at specified path ln -s client1 CLIENT1 and then ls -ltr to check links unfortunately desired soft link not created.
10-14-2014 09:28 AM
post command outputs
10-15-2014 04:23 AM
client backup first time test ran with name EESDLPB008AY5.domain.net. Now configured with name eesdlpb008ay5.domain.net. backup successfully duplication not happening.
Source NBU appliance
drwx------ 4 root root 8192 Sep 10 11:38 eesdlpb008ay5.domain.net
drwx------ 2 root root 96 Oct 14 15:52 EESDLPB008AY5.domain.net
sourcebck06:/disk/databases/catalog/2 # ln -s eesdlpb008ay5.domain.net EESDLPB008AY5.domain.net
ln: creating symbolic link `EESDLPB008AY5.domain.net/eesdlpb008ay5.domain.net' to `eesdlpb008ay5.domain.net': File exists
same output on destination as well when i ran ln -s command
10-15-2014 06:25 AM
Ok your problem is that since you reported this (in sept) the UPPER CASE client name folder was created. So now you're in another funny situation. Some images would be in the lower case and some would be in the UPPER CASE. You could try copy all from UPPER to lower, and then make a link for UPPER to lower. But makes sure you can the folders up before trying this.