cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted

Disk storage server is down(2106) / allocation failed(10) - Client-side deduplication enabled

Hi,

I got this error code 2106 and 10 on my backup clients over WAN when I enabled client side deduplication. But when I disabled it, backups run normally.

And when I defined client side deduplication ports 10102, 10082, 1556 on the client server, backups run normally too. Backup runs well on a 12 concurrent jobs defined in STU. But when I increased number of concurrent jobs say to 15-20, even client side dedup ports defined, I got error code 10. Does this mean it can only cater 12 concurrent jobs for client side deduplication option enabled? I have several backup policies that runs from 8:00PM to 7:00AM of the next day.

 

5/19/2016 3:45:16 PM - Info nbjm(pid=7296) starting backup job (jobid=742996) for client clientname, policy policy name, schedule Daily  
5/19/2016 3:45:16 PM - Info nbjm(pid=7296) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=742996, request id:{7A274ADB-1A3C-4F7B-BD95-B2CAA528BF32})  
5/19/2016 3:45:16 PM - requesting resource nbu4_stu
5/19/2016 3:45:16 PM - requesting resource nbu2.NBU_CLIENT.MAXJOBS.clientname
5/19/2016 3:45:16 PM - requesting resource nbu2.NBU_POLICY.MAXJOBS.policy name
5/19/2016 3:45:16 PM - Error nbjm(pid=7296) NBU status: 2106, EMM status: Storage Server is down or unavailable  
Disk storage server is down(2106)

================================================================================================================

5/19/2016 4:12:19 PM - Info nbjm(pid=11744) starting backup job (jobid=743013) for client clientname, policy policyname, schedule Daily  
5/19/2016 4:12:19 PM - Info nbjm(pid=11744) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=743013, request id:{7D9E0E5C-BE06-4B3E-8A53-46CFD2453B4D})  
5/19/2016 4:12:19 PM - requesting resource nbu4_stu
5/19/2016 4:12:19 PM - requesting resource nbu2.NBU_CLIENT.MAXJOBS.clientname
5/19/2016 4:12:19 PM - requesting resource nbu2.NBU_POLICY.MAXJOBS.policyname
5/19/2016 4:12:19 PM - granted resource nbu2.NBU_CLIENT.MAXJOBS.clientname
5/19/2016 4:12:19 PM - granted resource nbu2.NBU_POLICY.MAXJOBS.policyname
5/19/2016 4:12:19 PM - granted resource MediaID=@aaaap;DiskVolume=PureDiskVolume;DiskPool=bdownbu004_dp;Path=PureDiskVolume;StorageServer=nbu4;MediaServer=nbu4
5/19/2016 4:12:19 PM - granted resourcenbu4_stu
5/19/2016 4:12:31 PM - estimated 2371 Kbytes needed
5/19/2016 4:12:31 PM - Info nbjm(pid=11744) started backup (backupid=clientname_1463645551) job for client clientname, policy policyname, schedule Daily on storage unit nbu4_stu
5/19/2016 4:12:32 PM - started process bpbrm (9676)
5/19/2016 4:13:53 PM - Info bpbrm(pid=9676) clientname is the host to backup data from     
5/19/2016 4:13:53 PM - Info bpbrm(pid=9676) reading file list from client        
5/19/2016 4:13:53 PM - connecting
5/19/2016 4:14:19 PM - Info bpbrm(pid=9676) starting bpbkar32 on client         
5/19/2016 4:14:19 PM - connected; connect time: 00:00:26
5/19/2016 4:14:23 PM - Info bpbkar32(pid=924) Backup started           
5/19/2016 4:14:23 PM - Info bptm(pid=1756) start            
5/19/2016 4:14:23 PM - Info bptm(pid=1756) using 262144 data buffer size        
5/19/2016 4:14:23 PM - Info bptm(pid=1756) setting receive network buffer to 1049600 bytes      
5/19/2016 4:14:23 PM - Info bptm(pid=1756) using 30 data buffers         
5/19/2016 4:14:23 PM - Info bdownbu004(pid=1756) Using OpenStorage client direct to backup from client clientname to nbu4  
5/19/2016 4:20:16 PM - begin writing
5/19/2016 4:22:30 PM - Info nbu4(pid=1756) StorageServer=PureDisk:nbu4; Report=PDDO Stats for (nbu4): scanned: 1 KB, CR sent: 0 KB, CR sent over FC: 0 KB, dedup: 100.0%, cache hits: 0 (0.0%)
5/19/2016 4:22:45 PM - Error bpbrm(pid=9676) could not send server status message       
5/19/2016 4:22:59 PM - Info bpbkar32(pid=924) done. status: 10: allocation failed        
5/19/2016 4:22:59 PM - end writing; write time: 00:02:43
allocation failed(10)

Thanks

 

 

 

 

4 Replies
Highlighted

Re: Disk storage server is down(2106) / allocation failed(10) - Client-side deduplication enabled

Probably the WAN link observing bottleneck situation  when all backups running at its peak time. Try enabling "Resilency" between the Media Server and Client then try backups.

https://www.veritas.com/support/en_US/article.000072883

 

 

Highlighted

Re: Disk storage server is down(2106) / allocation failed(10) - Client-side deduplication enabled

Hi Pat,

I have tried that too resiliency ON. Some clients backup jobs are successful and some are not with error code 10 and 2106. If I tune the Maximum I/O  streams and limit it to what particular number should I set? Say If I will set a concurrent job of 20. Will this resolve the battleneck over the WAN link since client side deduplication option is ON?

Thanks

Re: Disk storage server is down(2106) / allocation failed(10) - Client-side deduplication enabled

Hello,

May I know configuration of Media Server ?

OS ? RAM ? CPU ? Storage Capacity ?

 

Highlighted

Re: Disk storage server is down(2106) / allocation failed(10) - Client-side deduplication enabled

Hi Pat,

Media server config is MSDP.

OS for master and media server is Windows Server 2008 r2

RAM is 24GB

CPU is 3.07Ghz, 2 processors @ 6 cores each proc.

Storage capacity - HP EVA - 9TB