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, Leth2.5KViews0likes9Comments(10) allocation failed
Good day Please advise vmdk backups to data domain are failign with error code 10. (10) allocation failed 02/10/2017 20:28:27 - Info nbjm (pid=3824) starting backup job (jobid=184223) for client NRBOWEB101, policy Bosasa_VMDK, schedule Weekly 02/10/2017 20:28:27 - Info nbjm (pid=3824) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=184223, request id:{8C21EE5A-0689-4642-94D1-F51207284609}) 02/10/2017 20:28:27 - requesting resource dp-DDNDC1-FC-stu 02/10/2017 20:28:27 - requesting resource nrecnetbk111.NBU_CLIENT.MAXJOBS.NRBOWEB101 02/10/2017 20:28:28 - granted resource nrecnetbk111.NBU_CLIENT.MAXJOBS.NRBOWEB101 02/10/2017 20:28:28 - granted resource MediaID=@aaaaf;DiskVolume=NRECNETBK120_STU;DiskPool=dp-DDNDC1-FC;Path=NRECNETBK120_STU;StorageServer=DFC-bcx-ndc1-fc;MediaServer=nrecnetbk120 02/10/2017 20:28:28 - granted resource dp-DDNDC1-FC-stu 02/10/2017 20:28:33 - estimated 80196442 kbytes needed 02/10/2017 20:28:33 - Info nbjm (pid=3824) started backup (backupid=NRBOWEB101_1486751308) job for client NRBOWEB101, policy Bosasa_VMDK, schedule Weekly on storage unit dp-DDNDC1-FC-stu using backup host nrecnetbk120 02/10/2017 20:29:05 - started process bpbrm (pid=1204) 02/10/2017 20:31:18 - connecting 02/10/2017 20:31:23 - connected; connect time: 0:00:00 02/10/2017 20:33:02 - Info bptm (pid=6300) start 02/10/2017 20:37:06 - end writing 02/10/2017 20:38:30 - Error bpbrm (pid=1204) could not send server status message 02/10/2017 20:38:36 - Info bpbkar32 (pid=0) done 02/10/2017 20:38:41 - Info bpbkar32 (pid=0) done. status: 10: allocation failed 02/13/2017 08:02:43 - job 184223 was restarted as job 188135 allocation failed (10)2.7KViews0likes9CommentsNetbackup 7.7.3 Device Configuration Wizard does not find Tape Drive or Robot
I just installed Netbackup 7.7.3 on a Windows 2012 Standard x64 machine. I have a Dell ML-6000 hooked up via a fibre HBA to the system Windows is able to see both the Tape drive and the medium changer and has no driver issues according to device manager. When I run the Device Configuration Wizard it says that it can't find either the Tape drives or robot I'm not sure what next steps should be to troubleshoot this issue, any help would be appriciatedSolved2.2KViews0likes11Comments'media manager received no data for backup image' backing up USB drive
We have a Windows 2008 R2 server setup as a media server that backs up smaller clients. The server has a 2tb USB drive attached that contains all our installation software and appears as a local F: drive. Although I can browse the contents of F: in the backup policy 'Backup Selections' all attempts to backup data from the drive fail. Other ordinary local drives backup fine. 18/12/2016 00:00:58 - Info nbjm(pid=5216) starting backup job (jobid=5029922) for client deploy01.corpadds.net, policy MBFS_FS_DEPLOY01_DEV, schedule Weekly_Full 18/12/2016 00:01:00 - estimated 2258934 Kbytes needed 18/12/2016 00:01:00 - Info nbjm(pid=5216) started backup (backupid=deploy01.corpadds.net_1482019260) job for client deploy01.corpadds.net, policy MBFS_FS_DEPLOY01_DEV, schedule Weekly_Full on storage unit MKDD002_MBFS_DEPLOY01 18/12/2016 00:01:02 - started process bpbrm (4528) 18/12/2016 00:01:03 - Info bpbrm(pid=4528) deploy01.corpadds.net is the host to backup data from 18/12/2016 00:01:03 - Info bpbrm(pid=4528) reading file list from client 18/12/2016 00:01:03 - Info bpbrm(pid=4528) starting bpbkar32 on client 18/12/2016 00:01:03 - connecting 18/12/2016 00:01:03 - connected; connect time: 0:00:00 18/12/2016 00:01:06 - Info bpbkar32(pid=3640) Backup started 18/12/2016 00:01:06 - Info bptm(pid=4028) start 18/12/2016 00:01:06 - Info bptm(pid=4028) using 262144 data buffer size 18/12/2016 00:01:06 - Info bptm(pid=4028) setting receive network buffer to 1049600 bytes 18/12/2016 00:01:06 - Info bptm(pid=4028) using 30 data buffers 18/12/2016 00:01:10 - Info bptm(pid=4028) start backup 18/12/2016 00:01:10 - begin writing 18/12/2016 00:01:27 - Info bpbkar32(pid=3640) change journal NOT enabled for <F:\Support\12. Symantec> 18/12/2016 00:01:27 - Info bptm(pid=4028) waited for full buffer 1 times, delayed 1068 times 18/12/2016 00:01:27 - Info bpbkar32(pid=3640) bpbkar waited 0 times for empty buffer, delayed 0 times. 18/12/2016 00:01:27 - Info bptm(pid=4028) EXITING with status 90 <---------- 18/12/2016 00:01:31 - Error bpbrm(pid=4528) cannot send mail to [snip] 18/12/2016 00:01:31 - Info bpbkar32(pid=3640) done. status: 90: media manager received no data for backup image 18/12/2016 00:01:31 - end writing; write time: 0:00:21 media manager received no data for backup image (90) How can I make this work? We need a weekly backup of this data. The target server is running Netbackup 7.5.0.6, the master is at 7.6.1.2. But this still didn't work back when everything was at 7.5.0.6. ThanksSolved3.8KViews0likes15CommentsConfiguring VMware that protect Exchange 2010 DAG
Hi All, I have to implement same configuration as describe in this post: https://vox.veritas.com/t5/NetBackup/Configuring-GRT-based-Exchange-Backup-using-vmware-backup-policy/m-p/824660#M223697 Note that I have implement tranditional backup of exchange and it works. But for perfomance issue, I want to implement VM backup that protects exchange and disable traditional backup. I have an error 13. I'm troubleshooting... Can you help? About DAR configuration, must I use FQDN or short name? I will post job details in fex time. Tnahk for your help.Solved5.2KViews0likes21CommentsNetbackup DFSR backup very slow
Hello, we recently deployed netback 7.7.3 on windows 2012. we have a Data domain storage. Everything is configured by following the veritas and emc guides. eveything is superb except when it comes to DFSR folders. After some reading we understood "Use Journal" is not supported with dfsr. we understood we should add the backup select like Shadow Copy Components:\User Data\Distributed File System Replication\DfsrReplicatedFolders\LosAngeles Shadow Copy Components:\User Data\Distributed File System Replication\DfsrReplicatedFolders\NewYork Shadow Copy Components:\User Data\Distributed File System Replication\DfsrReplicatedFolders\Denver we have a 2 TB of data and the backup durations of full and incrimental backup are not ecceptable. I read a lot of posts from people complaining from the same issue when backing up the shadow copy components bot none was helpful. i think i missed something. your help will be much appreciated. let me know if i should provide more info.4.8KViews0likes38CommentsWeird problem with Vmware vcsa 5.5 and Netbackup 7.7.3 web plugin <cannot restore>
Dear Vox member, Trying to install the Netbackup 7.7.3 web plugin for VMware 5.5 server appliance. My normal vSphere client works fine, Restores can be done and backup status is available. The web plugin is acting weird. Backup status is fine, Master server is validated. When trying to restore via the recovery wizard and lookup machine it gives back: no entity was found EC:227 When try to restore via the instant recovery wizard. No mapping found between vCenter(s) and Master Server(s) The Master server box is empty here, while it IS available in the recovery wizard. On the master server, this is in the web log: 2,51216,439,439,269,1479119904793,2488,36,0:,87:Entering the proxy filter and the incoming request is :/nbwebservice/image/vmclientlist,2,(0|) 2,51216,439,439,270,1479119905371,2488,36,0:,55:The CWS server returned error. Error code returned :500,2,(0|) 2,51216,439,439,271,1479119905371,2488,36,0:,75:Request with URI /nbwebservice/image/vmclientlist processed successfully...,2,(0|) 2,51216,439,439,272,1479119905418,2488,44,0:,86:Entering the proxy filter and the incoming request is :/nbwebservice/server/masterlist,2,(0|) 2,51216,439,439,273,1479119905480,2488,44,0:,74:Request with URI /nbwebservice/server/masterlist processed successfully...,2,(0|) what could be wrong? where to troubleshoot? OlafSolved2.8KViews0likes5CommentsNetbackup performance issues
Hi Experts, I'm facing performance issues in my backup env. I tried to go through with tuning guides but it didn't help much. my env. netbackup master/media server version 7.7.3 1 master server [virtual machine] OS :windows 2008 standard R2 3 media servers [Dell R510, Dell 720] including 8 drives [Dell tl400] OS windows 2012 I've seen that VM backups are really slow and takes a long time to complete which always delayed the duplication [destaging to tape drive and DR site]. all clients are behind firewall, which means data pass through firewall -ofc it slow down the whole process. I am looking for some suggestions if i can improve the performance , might to implement backup vlan's or any other idea's. Thanks, dpx3.2KViews0likes20Commentsfailed BMR
NBU 7.6.0.3 i have ran BMR backups before and they were smooth. first time i encounter a problem. the usual BMR settings, "All Local Drives". an error 1 on the parent job but status 0 for the child. same BMR backup policy which has been copied over and over (of course edited accordingly) are fine. 12/8/2016 12:20:28 PM - Error bpbrm(pid=21557) BMRERR: Received BMR error: Failed to discover System. (12) 12/8/2016 12:20:28 PM - Error bpbrm(pid=21557) BMRERR: Received BMR error: BMR information discovery failed. (35) 12/8/2016 12:20:28 PM - Error bpbrm(pid=21557) BMRERR: Did not receive bmr client request from ruh1cas01, status = -1 12/8/2016 12:20:28 PM - Info bmrsavecfg(pid=0) done. status: 26: client/server handshaking failed 12/8/2016 12:20:28 PM - end writing Status 26 12/8/2016 12:20:28 PM - end Bare Metal Restore, BMR Save; elapsed time: 0:00:02 12/8/2016 12:20:28 PM - begin Bare Metal Restore, Policy Execution Manager Preprocessed Status 0 12/8/2016 2:22:11 PM - end Bare Metal Restore, Policy Execution Manager Preprocessed; elapsed time: 2:01:43 12/8/2016 2:22:11 PM - begin Bare Metal Restore, End Notify Script 12/8/2016 2:22:11 PM - Info RUNCMD(pid=7705) started 12/8/2016 2:22:11 PM - Info RUNCMD(pid=7705) exiting with status: 0 Status 0 12/8/2016 2:22:11 PM - end Bare Metal Restore, End Notify Script; elapsed time: 0:00:00 Status 1 12/8/2016 2:22:11 PM - end Parent Job; elapsed time: 2:01:46 the requested operation was partially successful(1) The job was successfully completed, but some files may have been busy or inaccessible. See the problems report or the client's logs for more details.1.3KViews0likes6Comments