Quantcast
Channel: Symantec Connect
Viewing all articles
Browse latest Browse all 26913

Catalog Backup take long time

$
0
0
Copy all the children of the comment that is the source of this new discussion.
ソリューションが必要です

**** Moved to new discussion from https://www-secure.symantec.com/connect/forums/catalog-backup-take-long-time ****

 

Dears,

The problem has returned again,catalog backup take more than 15 hours,also note that i incresed the SIZE_DATA_BUFFERS to 262144 and NUMBER_DATA_BUFFERS to 512,any idea?

please check the below logs from activity monitor:

 

12/8/2013 10:01:34 AM - Info nbjm(pid=5220) starting backup job (jobid=581774) for client kfhsanwk, policy Catalog_Backup2, schedule Daily  
12/8/2013 10:01:34 AM - Info nbjm(pid=5220) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=581774, request id:{3128072D-CA6F-401C-A856-8EA4EBF4316D})  
12/8/2013 10:01:34 AM - requesting resource kfhsanwk-hcart-robot-tld-0
12/8/2013 10:01:34 AM - requesting resource kfhsanwk.NBU_CLIENT.MAXJOBS.kfhsanwk
12/8/2013 10:01:34 AM - requesting resource kfhsanwk.NBU_POLICY.MAXJOBS.Catalog_Backup2
12/8/2013 10:01:34 AM - awaiting resource kfhsanwk-hcart-robot-tld-0 - FT client has no devices configured
12/8/2013 10:01:34 AM - granted resource kfhsanwk.NBU_CLIENT.MAXJOBS.kfhsanwk
12/8/2013 10:01:34 AM - granted resource kfhsanwk.NBU_POLICY.MAXJOBS.Catalog_Backup2
12/8/2013 10:01:34 AM - granted resource HO0148
12/8/2013 10:01:34 AM - granted resource HP.ULTRIUM3-SCSI.002
12/8/2013 10:01:34 AM - granted resource kfhsanwk-hcart-robot-tld-0
12/8/2013 10:01:35 AM - Info bpbrm(pid=12088) kfhsanwk is the host to backup data from     
12/8/2013 10:01:35 AM - Info bpbrm(pid=12088) reading file list from client        
12/8/2013 10:01:35 AM - estimated 0 Kbytes needed
12/8/2013 10:01:35 AM - Info nbjm(pid=5220) started backup (backupid=kfhsanwk_1386486094) job for client kfhsanwk, policy Catalog_Backup2, schedule Daily on storage unit kfhsanwk-hcart-robot-tld-0
12/8/2013 10:01:35 AM - started process bpbrm (12088)
12/8/2013 10:01:35 AM - connecting
12/8/2013 10:01:36 AM - Info bpbrm(pid=12088) starting bpbkar32 on client         
12/8/2013 10:01:36 AM - connected; connect time: 00:00:01
12/8/2013 10:01:37 AM - Info bpbkar32(pid=11080) Backup started           
12/8/2013 10:01:37 AM - Info bptm(pid=9604) start            
12/8/2013 10:01:37 AM - Info bptm(pid=9604) using 262144 data buffer size        
12/8/2013 10:01:37 AM - Info bptm(pid=9604) setting receive network buffer to 1049600 bytes      
12/8/2013 10:01:37 AM - Info bptm(pid=9604) using 512 data buffers         
12/8/2013 10:01:38 AM - Info bptm(pid=9604) start backup           
12/8/2013 10:01:39 AM - Info bptm(pid=9604) media id HO0148 mounted on drive index 2, drivepath {6,0,0,0}, drivename HP.ULTRIUM3-SCSI.002, copy 1
12/8/2013 10:01:39 AM - mounted
12/8/2013 10:01:39 AM - positioning HO0148 to file 7
12/8/2013 10:01:43 AM - positioned HO0148; position time: 00:00:04
12/8/2013 10:01:43 AM - begin writing
12/8/2013 10:38:58 PM - Info bptm(pid=9604) waited for full buffer 249240 times, delayed 2855826 times    
12/8/2013 10:38:58 PM - Info bpbkar32(pid=11080) bpbkar waited 0 times for empty buffer, delayed 0 times.   
12/8/2013 10:39:22 PM - Info bptm(pid=9604) EXITING with status 0 <----------        
12/8/2013 10:39:22 PM - Info bpbrm(pid=12088) validating image for client kfhsanwk        
12/8/2013 10:39:23 PM - Info bpbkar32(pid=11080) done. status: 0: the requested operation was successfully completed    
12/8/2013 10:39:23 PM - end writing; write time: 12:37:40
the requested operation was successfully completed(0)

9525161

Viewing all articles
Browse latest Browse all 26913

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>