Exchange 2010 GRT Backups Failing GRT Recovery
Hi All, I have a strange issue regarding our MS Exchange backups when it comes to the Granular processing on a certain storage type. To start off we are running: NB Master: AIX 6.1 with Netbackup 7.7.2 NB Media : 3 x AIX 6.1 with Netbackup 7.7.2 (Not used for Exchange backups) 3 x MS Windows 2012 R2withNetbackup 7.7.2 OST Pluginfor all media Servers is 3.1.5 Storage Units: 1 x MSDP Pure disk Volume (GRT Backups work when going here) 1 x HP StoreOnce 6500 running software 3.13 and using Catalyst Stores (GRT Backups fail on this storage unit) To cut a long story short, we want to move the storatge unit our exchange backups go to from the MSDP to the Open Storage platform. The backup seems to fail on the GRT segment of the backup on the Open Storage, the databasebacks upfine. As far as i can see the compatibility lists state that our StoreOnce should be on software version 3.1 and Netbackup on 7.6 or above which we meet. The detailed Status Log when backup up to MSDB says: (No error just to reiterate) 12/15/2016 12:47:02 - Info bpbrm (pid=7944) DB_BACKUP_STATUS is 0 12/15/2016 12:48:01 - Info bpbrm (pid=7944) from client server-dag-01.domain.com: TRV - Starting granular backup processing for (/Microsoft Exchange Database Availability Groups/server-dag-01\Microsoft Information Store:\server-MBX-DB2\). This may take a while... 12/15/2016 12:48:04 - end writing; write time: 0:36:29 12/15/2016 12:48:36 - Info bpbrm (pid=7944) from client server-dag-01.domain.com: TRV - Successfully finished granular backup processing for (/Microsoft Exchange Database Availability Groups/server-dag-01\Microsoft Information Store:\server-MBX-DB2\). 12/15/2016 12:48:36 - Info bpbrm (pid=7944) from client server-dag-01.domain.com: TRV - Exchange granular database changes were backed up successfully. 12/15/2016 12:48:36 - Info bptm (pid=11284) waited for full buffer 88039 times, delayed 139391 times 12/15/2016 12:48:39 - Info bptm (pid=11284) EXITING with status 0 <---------- 12/15/2016 12:48:39 - Info resnetb3 (pid=11284) StorageServer=PureDisk:mediaserver2; Report=PDDO Stats (multi-threaded stream used) for (mediaserver2): scanned: 37852441 KB, CR sent: 88611 KB, CR sent over FC: 0 KB, dedup: 99.8%, cache hits: 2209 (0.7%), rebased: 28 (0.0%) 12/15/2016 12:48:40 - Info bpbrm (pid=7944) validating image for client server-dag-01.domain.com 12/15/2016 12:48:41 - Info bpbkar32 (pid=45212) done. status: 0: the requested operation was successfully completed the requested operation was successfully completed (0) But as soon as we switch over to the StoreOnce: 12/15/2016 17:11:01 - Info bptm (pid=12956) start 12/15/2016 17:47:24 - end writing; write time: 0:37:00 12/15/2016 17:47:31 - Info bpbrm (pid=13832) DB_BACKUP_STATUS is 0 12/15/2016 17:47:50 - Info bpbrm (pid=13832) from client server-dag-01.domain.com: TRV - Starting granular backup processing for (/Microsoft Exchange Database Availability Groups/server-dag-01\Microsoft Information Store:\server-MBX-DB2\). This may take a while... 12/15/2016 17:47:54 - Info bpbrm (pid=13832) from client server-dag-01.domain.com: TRV - Granular processing failed! 12/15/2016 17:47:54 - Error bpbrm (pid=13832) from client server-dag-01.domain.com: ERR - Error encountered while attempting to get additional files for Microsoft Information Store:\server-MBX-DB2\Logs_1481821614\ 12/15/2016 17:47:54 - Error bpbrm (pid=13832) from client server-dag-01.domain.com: ERR - Exchange granular restore from this image may not work. 12/15/2016 17:47:54 - Info bpbrm (pid=13832) from client server-dag-01.domain.com: TRV - Exchange granular database changes were backed up successfully. 12/15/2016 17:47:56 - Info bptm (pid=4620) waited for full buffer 70906 times, delayed 126450 times 12/15/2016 17:48:00 - Info bptm (pid=4620) EXITING with status 0 <---------- 12/15/2016 17:48:00 - Info mediaserver2 (pid=4620) StorageServer=hp-StoreOnceCatalyst:STORAGEBKUPTIER3SS1; Report=scanned: 38748558336 Bytes, CR sent: 337319494 Bytes, dedup: 99.12% 12/15/2016 17:48:00 - Info bpbrm (pid=13832) validating image for client server-dag-01.domain.com 12/15/2016 17:48:02 - Info bpbkar32 (pid=51732) done. status: 1: the requested operation was partially successful The requested operation was partially successful (1) The only difference between these backups is the storage unit. it is the same policy with the same settings. We are just dropping the menu down and selecting a different Storage unit. To help with our investigation we have locked this test down to just 1 of our 6 media servers. Any help on this issue is greatly appreciated. Kind regards, Leth
Tape Drives show Missing Paths
Some of my tape drives are showing missing paths after a migration from one Fiber switch to another. I have validated that the zones are setup the same on the networking side (and even see the drives checked in, in the fiber database on the switches), I tried a solution from a previous post on one of the drives with the missing path(removing the drive and running tpautoconfig -a), but am not actually seeing the drive show back up after running tpautoconfig -a. Any assistance would be very helpful.bpstart/bpend notify script usage with VMware type backup
Is it possible to use bpstart_notify and bpend_notify scripts with a VMware type backup job? (single VM in the policy) From what I understand bpstart_notify runs when bpbkar starts on client. But with VMware type backup, the bpbkar process starts during the actual backup job. The need is to run something before the snapshot is taken and then run another set after the snapshot is consolidated after backp completes. I have tried the pre and post scripts in /usr/sbin/ directory but they seem to run almost at the same time ( I generated some files pre and post and they all had same file stamps). Any other pointers?Alternate method to remove SRT in LOCKED_WRITE state
# bmrsrtadm Select one of the following options: 1. Create a new Shared Resource Tree. 2. Create a new CD image based Shared Resource Tree. 3. Copy an existing Shared Resource Tree to a new location. 4. Import a Shared Resource Tree. 5. Modify an existing Shared Resource Tree. 6. Delete an existing Shared Resource Tree. 7. List Shared Resource Trees available on this server. 8. Quit. Enter your selection (1-8) [1] : 7 Name State Type Path Description ------------- ------------ ---- ------------------------------ -------------------- linuxRH67 LOCKED_WRITE NFS /nbu_bmr/SRT/linuxRH67 Redhat Linux 6.7 Select one of the following options: 1. Create a new Shared Resource Tree. 2. Create a new CD image based Shared Resource Tree. 3. Copy an existing Shared Resource Tree to a new location. 4. Import a Shared Resource Tree. 5. Modify an existing Shared Resource Tree. 6. Delete an existing Shared Resource Tree. 7. List Shared Resource Trees available on this server. 8. Quit. Enter your selection (1-8) [1] : 6 Enter the name of an existing SRT : linuxRH67 That SRT is in use and cannot be deleted until its lock is released. Select one of the following options: 1. Create a new Shared Resource Tree. 2. Create a new CD image based Shared Resource Tree. 3. Copy an existing Shared Resource Tree to a new location. 4. Import a Shared Resource Tree. 5. Modify an existing Shared Resource Tree. 6. Delete an existing Shared Resource Tree. 7. List Shared Resource Trees available on this server. 8. Quit. Enter your selection (1-8) [1] : 5 Enter the name of an existing SRT : linuxRH67 The SRT you selected is in a LOCKED state. This typically means that the SRT is busy, and you should wait for it to come unlocked before you continue. Would you like to wait for the SRT to come free? (y/n) [y] : n If you are ABSOLUTELY SURE nobody is using this SRT and this is a stale lock, you may choose to break the lock and continue. If you break the lock while somebody is using the SRT, you may corrupt the SRT. Are you ABSOLUTELY SURE you want to break the lock and continue? (y/n) [n] : y The SRT lock has been broken and the SRT has been placed into a DAMAGED state. Next, SRT recovery will be attempted. If recovery is successful you will be able to use this SRT. If recovery fails you probably will have to delete this SRT and create a new one Working ...Segmentation fault (core dumped) # ls -l drwxr-xr-x 14 root root 4096 Jul 13 10:45 linuxRH67 # mv linuxRH67 linuxRH67.old # bmrsrtadm Select one of the following options: 1. Create a new Shared Resource Tree. 2. Create a new CD image based Shared Resource Tree. 3. Copy an existing Shared Resource Tree to a new location. 4. Import a Shared Resource Tree. 5. Modify an existing Shared Resource Tree. 6. Delete an existing Shared Resource Tree. 7. List Shared Resource Trees available on this server. 8. Quit. Enter your selection (1-8) [1] : 7 Name State Type Path Description ------------- ------------ ---- ------------------------------ -------------------- linuxRH67 LOCKED_WRITE NFS /nbu_bmr/SRT/linuxRH67 Redhat Linux 6.7 Select one of the following options: 1. Create a new Shared Resource Tree. 2. Create a new CD image based Shared Resource Tree. 3. Copy an existing Shared Resource Tree to a new location. 4. Import a Shared Resource Tree. 5. Modify an existing Shared Resource Tree. 6. Delete an existing Shared Resource Tree. 7. List Shared Resource Trees available on this server. 8. Quit. Enter your selection (1-8) [1] : 5 Enter the name of an existing SRT : linuxRH67 The SRT you selected is in a LOCKED state. This typically means that the SRT is busy, and you should wait for it to come unlocked before you continue. Would you like to wait for the SRT to come free? (y/n) [y] : n If you are ABSOLUTELY SURE nobody is using this SRT and this is a stale lock, you may choose to break the lock and continue. If you break the lock while somebody is using the SRT, you may corrupt the SRT. Are you ABSOLUTELY SURE you want to break the lock and continue? (y/n) [n] : y The SRT lock has been broken and the SRT has been placed into a DAMAGED state. Next, SRT recovery will be attempted. If recovery is successful you will be able to use this SRT. If recovery fails you probably will have to delete this SRT and create a new one V-125-3 mkdir(/nbu_bmr/SRT/linuxRH67/isolinux,0755) failed: No such file or directory V-125-39 caught exception: runtime error in srtPlat.cpp:DoMkdir() [Error] V-125-267 Cannot prepare boot files for this SRT. You may choose either to leave this SRT on the server in its current state, or to delete it. Do you want to delete this SRT from the server? (y/n) : y Removing SRT "linuxRH67" from server -- please stand by ... # bmrsrtadm Select one of the following options: 1. Create a new Shared Resource Tree. 2. Create a new CD image based Shared Resource Tree. 3. Copy an existing Shared Resource Tree to a new location. 4. Import a Shared Resource Tree. 5. Modify an existing Shared Resource Tree. 6. Delete an existing Shared Resource Tree. 7. List Shared Resource Trees available on this server. 8. Quit. Enter your selection (1-8) [1] : 7 Name State Type Path Description ------------- ----- ---- ------------------------------ -------------------- Select one of the following options: 1. Create a new Shared Resource Tree. 2. Create a new CD image based Shared Resource Tree. 3. Copy an existing Shared Resource Tree to a new location. 4. Import a Shared Resource Tree. 5. Modify an existing Shared Resource Tree. 6. Delete an existing Shared Resource Tree. 7. List Shared Resource Trees available on this server. 8. Quit. Enter your selection (1-8) [1] : 8 [Info] V-125-491 No SRT changes made.
Disk Type (which is better or best practice) -Basic, Advanced, Pure disk
Hi Experts, I'm currently trying to improve backup environment in terms not to mix Basic , Advance or Pure disks for backup. I've opportunity to delete all basic , advance disks and create one MSDP pool. Is this right approach ? or how i can use if i have mixed disks type. Please assist. many thanks dpxdisable storage lifecycle policy
Hi All, i'm running NBU 7.7.2 on Windows 2012 R2. STU configured DISK-STU TAPE-STU SLP configured SLP01 which perform 1\ backup using DISK-STU (kept for 1 week) 2\ duplication using TAPE-STU (kept for 2 weeks) SLP02 which perform 1\ backup using DISK-STU (kept for 1 year) 2\ duplication using TAPE-STU (kept for 1 year) i have a VMware policy configured with with 4 clients and scheduled 1\ to run on daily basis using SLP01 2\ to run on monthly basis using SLP02 question in certain scenario, i'm force to disable SLP01 & SLP02 and eventually backup still completed. backup run using DISK-STU which defined in policy Attributes. which backup retention will it used as SLP was disable
