Quantcast
Channel: Symantec Connect - Backup and Recovery - 讨论
Viewing all articles
Browse latest Browse all 5766

NBU 7.5.0.3 - Replication Fail(Status 84)

$
0
0
我需要解决方案

Hi Forum,

 

Just wondering if the experts can help me troubleshoot the issue. I have logged a case, but it takes a long time for them to respond and it seems they arent sure how to approach this.

Here is the scenario: from Local Master.

Two master servers(Local and DR), replication setup one way(Local to DR). replication fails from local master to DR master. Status 84.

Details of error:

 

17/05/2013 10:34:38 - requesting resource LCM_STU-MSDP-Source
17/05/2013 10:34:38 - granted resource LCM_STU-MSDP-Source
17/05/2013 10:34:38 - started process RUNCMD (13884)
17/05/2013 10:34:39 - requesting resource @aaaac
17/05/2013 10:34:39 - reserving resource @aaaac
17/05/2013 10:34:39 - reserved resource @aaaac
17/05/2013 10:34:39 - granted resource MediaID=@aaaac;DiskVolume=PureDiskVolume;DiskPool=sustp-pwl-bak01-dp;Path=PureDiskVolume;StorageServer=sustp-pwl-bak01;MediaServer=sustp-pwl-bak01
17/05/2013 10:34:42 - Info bpdm(pid=13900) started           
17/05/2013 10:34:42 - started process bpdm (13900)
17/05/2013 10:34:47 - Info sustp-pwl-bak01(pid=13900) Using OpenStorage to replicate backup id sustp-pll-nfs01.tgptrading.glb.corp.local_1368795600, media id @aaaac, storage server sustp-pwl-bak01, disk volume PureDiskVolume
17/05/2013 10:34:47 - Info sustp-pwl-bak01(pid=13900) Replicating images to target storage server suslv-pwl-bak01, disk volume PureDiskVolume  
17/05/2013 10:35:18 - Error bpdm(pid=13900) wait failed: error 2060014        
17/05/2013 10:35:18 - Error bpdm(pid=13900) <async> cancel failed: error 2060001: one or more invalid arguments  
17/05/2013 10:35:18 - Error bpdm(pid=13900) copy cancel failed: error 2060001       
17/05/2013 10:35:18 - Info sustp-pwl-bak01(pid=13900) StorageServer=PureDisk:sustp-pwl-bak01; Report=PDDO Stats for (sustp-pwl-bak01): scanned: 4 KB, CR sent: 0 KB, CR sent over FC: 0 KB, dedup: 100.0%
17/05/2013 10:35:18 - Error (pid=13884) ReplicationJob::Replicate: Replication failed for backup id sustp-pll-nfs01.tgptrading.glb.corp.local_1368795600: media write error (84) 
17/05/2013 10:35:18Replicate failed for backup id sustp-pll-nfs01.tgptrading.glb.corp.local_1368795600 with status 84
17/05/2013 10:35:18 - end operation

From the DR Master:

5/17/2013 2:47:27 AM - requesting resource @aaaac
5/17/2013 2:47:27 AM - Error nbjm(pid=6492) NBU status: 2074, EMM status: Disk volume is down   
Disk volume is down(2074)
5/17/2013 2:47:27 AM - Error nbjm(pid=6492) NBU status: 2074, EMM status: Disk volume is down

When I look on the DR Master, Media and Device Mgmt > Credentials > Storage Servers > under properties or replication I get the following error.

"Internal application error. Please contact your administrator. invalid comman parameter. RDSM has encountered an issue with STS where the server was not found: getDiskVolumeInfoList"

 

I have tried to UP the disk volume through command prompt, but same issues continue. Let me know which logs might be useful for you experts reading this.

 

Thanks in advance,

 

Luis S.

 


Viewing all articles
Browse latest Browse all 5766

Trending Articles



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