Quantcast
Channel: Symantec Connect - Backup and Recovery - Discussions
Viewing all articles
Browse latest Browse all 8938

getting backup errors through checkpoint mode

$
0
0
I need a solution

Hi all ,

getting backup errors in checkpoint mode after upgrade the appliance from 1.4 to 1.4.2.(all jobs going failed).do you believe that backup in checkpoint mode will not functioning fine?

10/14/2012 9:06:32 AM - Info nbjm(pid=960) starting backup job (jobid=1573) for client ryhg2-pw-master.moe.local, policy Catalog_DR, schedule full 

10/14/2012 9:06:32 AM - Info bpbrm(pid=6328) ryhg2-pw-master.moe.local is the host to backup data from    

10/14/2012 9:06:32 AM - Info bpbrm(pid=6328) reading file list from client       

10/14/2012 9:06:32 AM - Info nbjm(pid=960) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=1573, request id:{7308C968-2F3A-4661-8DB5-142069E6B2FA}) 

10/14/2012 9:06:32 AM - requesting resource STU-RYHG2-DR

10/14/2012 9:06:32 AM - requesting resource ryhg2-pw-master.moe.local.NBU_CLIENT.MAXJOBS.ryhg2-pw-master.moe.local

10/14/2012 9:06:32 AM - requesting resource ryhg2-pw-master.moe.local.NBU_POLICY.MAXJOBS.Catalog_DR

10/14/2012 9:06:32 AM - granted resource ryhg2-pw-master.moe.local.NBU_CLIENT.MAXJOBS.ryhg2-pw-master.moe.local

10/14/2012 9:06:32 AM - granted resource ryhg2-pw-master.moe.local.NBU_POLICY.MAXJOBS.Catalog_DR

10/14/2012 9:06:32 AM - granted resource MediaID=@aaaab;DiskVolume=PureDiskVolume;DiskPool=RYHG2_DR_POOL;Path=PureDiskVolume;StorageServer=RYHG2-PL-VTL1;MediaServer=ryhg2-pw-master.moe.local

10/14/2012 9:06:32 AM - granted resource STU-RYHG2-DR

10/14/2012 9:06:32 AM - estimated 0 Kbytes needed

10/14/2012 9:06:32 AM - Info nbjm(pid=960) started backup job for client ryhg2-pw-master.moe.local, policy Catalog_DR, schedule full on storage unit STU-RYHG2-DR

10/14/2012 9:06:32 AM - started process bpbrm (6328)

10/14/2012 9:06:32 AM - connecting

10/14/2012 9:06:33 AM - Info bpbrm(pid=6328) listening for client connection        

10/14/2012 9:06:33 AM - Info bpbrm(pid=6328) INF - Client read timeout = 300     

10/14/2012 9:06:33 AM - Info bpbrm(pid=6328) accepted connection from client        

10/14/2012 9:06:33 AM - Info bpbrm(pid=6328) start bpbkar on client        

10/14/2012 9:06:33 AM - connected; connect time: 00:00:01

10/14/2012 9:06:34 AM - Info bphdb(pid=4756) Backup started          

10/14/2012 9:06:34 AM - Info bphdb(pid=3524) Backup started          

10/14/2012 9:06:34 AM - Info bptm(pid=6176) start           

10/14/2012 9:06:34 AM - Info bptm(pid=6176) using 262144 data buffer size       

10/14/2012 9:06:34 AM - Info bptm(pid=6176) setting receive network buffer to 1049600 bytes     

10/14/2012 9:06:34 AM - Info bptm(pid=6176) using 30 data buffers        

10/14/2012 9:06:37 AM - Info bptm(pid=6176) start backup          

10/14/2012 9:06:50 AM - Critical bptm(pid=6176) image open failed: error 2060012: call should be repeated   

10/14/2012 9:06:57 AM - Info bptm(pid=6176) EXITING with status 84 <----------       

10/14/2012 9:06:58 AM - Info bphdb(pid=3524) bpbkar waited 0 times for empty buffer, delayed 0 times.  

10/14/2012 9:06:58 AM - Info bphdb(pid=3524) done. status: 40         

10/14/2012 9:07:00 AM - Error bpbrm(pid=6328) could not send server status message      

10/14/2012 9:07:01 AM - end writing

10/14/2012 9:07:06 AM - Info bphdb(pid=3524) done. status: 84: media write error      

media write error(84)

 

and i saw these errors in bptm:

delete_expired_media: (-) Translating EMM_ERROR_DBServerDown(4005006) to 220 in the NetBackup context

<16> 1529:bptm:6844:ryhg2-pw-master.moe.local: PDVFS: [1] pdvfs_fcache_lookup: fd 90006 already opened for direct I/O

09:02:45.894 [6844.3216] <16> 1529:bptm:6844:ryhg2-pw-master.moe.local: PDVFS: [1] PdvfsOpen: failed for "/RYHG2-PL-VTL1#1/3/ryhg2-pw-master.moe.local/Catalog_DR/ryhg2-pw-master.moe.local_1350108154_C1_F1.img": errno=Resource device

09:02:45.894 [6844.3216] <16> 1529:bptm:6844:ryhg2-pw-master.moe.local: load_fp_cache_file error (16 Resource device) opening /RYHG2-PL-VTL1#1/3/ryhg2-pw-master.moe.local/Catalog_DR/ryhg2-pw-master.moe.local_1350108154_C1_F1.img, it will not be cached

09:02:46.300 [6844.3216] <2> io_open_disk: file ryhg2-pw-master.moe.local_1350108154_C1_F1 successfully opened

<16> 1535:bptm:4648:ryhg2-pw-master.moe.local: PDVFS: [1] pdvfs_task_ctrl: PDDO dataselection is in rollback mode

13:27:36.546 [4648.3300] <16> 1535:bptm:4648:ryhg2-pw-master.moe.local: PDVFS: [1] pdvfs_pwrite: pdvfs_task_ctrl failed

13:27:36.546 [4648.3300] <16> 1535:bptm:4648:ryhg2-pw-master.moe.local: impl_set_imh_image_prop error (11 Resource temporarily unavailable) wrote -1 while expecting 608 bytes (/RYHG2-PL-VTL1#1/3/ryhg2-pw-master.moe.local/Catalog_DR/ryhg2-pw-master.moe.local_1350124038_C1_HDR.info)

13:27:36.546 [4648.3300] <32> bp_sts_open_image: sts_create_image failed: error 2060012

13:27:36.608 [4648.3300] <32> write_disk_header: image open failed: error 2060012:

<16> 1538:bptm:2376:ryhg2-pw-master.moe.local: PDVFS: [1] pdvfs_task_ctrl: PDDO dataselection is in rollback mode

13:28:58.071 [2376.4744] <16> 1538:bptm:2376:ryhg2-pw-master.moe.local: PDVFS: [1] pdvfs_pwrite: pdvfs_task_ctrl failed

13:28:58.071 [2376.4744] <16> 1538:bptm:2376:ryhg2-pw-master.moe.local: impl_set_imh_image_prop error (11 Resource temporarily unavailable) wrote -1 while expecting 608 bytes (/RYHG2-PL-VTL1#1/3/ryhg2-pw-master.moe.local/Catalog_DR/ryhg2-pw-master.moe.local_1350124120_C1_HDR.info)

13:28:58.087 [2376.4744] <32> bp_sts_open_image: sts_create_image failed: error 2060012

13:28:58.087 [2376.4744] <32> write_disk_header: image open failed: error 2060012:

<16> 1547:bptm:6940:ryhg2-pw-master.moe.local: PDVFS: [1] pdvfs_task_ctrl: PDDO dataselection is in rollback mode

14:17:40.344 [6940.1812] <16> 1547:bptm:6940:ryhg2-pw-master.moe.local: PDVFS: [1] pdvfs_mkdir: pdvfs_task_ctrl failed

14:17:40.344 [6940.1812] <16> 1547:bptm:6940:ryhg2-pw-master.moe.local: impl_get_imh_image_prop pd_mkdir(/RYHG2-PL-VTL1#1/3/ryhg2-pw-master.moe.local/test) failed: error(-1) errno(11)

14:17:40.344 [6940.1812] <32> bp_sts_open_image: sts_create_image failed: error 2060012

14:17:40.360 [6940.1812] <32> write_disk_header: image open failed: error 2060012:


Viewing all articles
Browse latest Browse all 8938

Trending Articles



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