Moving FSA archived sub-folder to different volume in same file server.
Hi, I am running out of space in the file server and I want to move folders one by one to another volume. I can't move the Archive Point to another volume using FSA utility because of the huge size and I don't have that much space in a single volume. So I want to move some of the subfolder (Which contain placeholders) in one volume and some of the folders to another volume. Is there any way we can get this task done?
Netbackup exluding many folders form backup
Hello Team, Thanks in advance for all your help. I have Netbackup server and from it we are taking file server backup. During restoring of files, we found many files and folders are not backuped up with Netbackup. After analyzing, I found issue with NTFS permission. I have one Security groups which dont have access to that folders which I have used for backup. Now thing is I have many file servers and I dont have any details on which folder this group dont have permission. So looking for detailed backup report from Netbackup where files are folder are not included in backup due to permission issues. Please help on this. Regards, Yogesh Makwana
Prueba de proceso de Duplicacion ( Back up IP does not exist)
Buenas Tenemos una duda con el Symantec DLO console,estamos implementando el proceso de deduplicacion o Dedupe lo pusimos a correr en un perfil y repetidamente han salidos varios usuarios con error y alertas donde muesta que el Back up IP does not exist, lo que me gustaria saber es por que sale ese error si el archivo esta a la ves siendo localizado y respaldado pero cuando se modifica muestra ese error gracias y espero su ayuda, si el error les parece tedioso me pueden preguntar para aclarar
NBU 7.5.0.3 - Replication Fail(Status 84)
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=xxxxxxx-dp;Path=PureDiskVolume;StorageServer=xxxxxxbak01;MediaServer=xxxxxx-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 xxxxxxbak01(pid=13900) Using OpenStorage to replicate backup id xxxxx-nfs01xxxxx.xxxxxx.local_1368795600, media id @aaaac, storage server xxxxxx-bak01, disk volume PureDiskVolume 17/05/2013 10:34:47 - Info xxxxxxx-bak01(pid=13900) Replicating images to target storage server xxxxxxbak01, 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 xxxxxxxbak01(pid=13900) StorageServer=PureDisk:xxxxxxx-bak01; Report=PDDO Stats for (xxxxxbak01): 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 xxxxxxxnfs01.xxxxxxxx_1368795600: media write error (84) 17/05/2013 10:35:18Replicate failed for backup id xxxxnfs01.xxxxxxxx_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.