Restores queuing for 60+ minutes before beginning execution, Netbackup 7.5.0.3
We have just upgraded from 7.0 to 7.5.0.3 on our master and media servers. They are running on Sun Solaris version 10. Previously we had no issues with restores, but now it seems that most of our restores are remaining in a queued state after being submited fromanywhere from 30 to 60 or minutes before they begin execution. Once they begin running, they restore fine with normal transfer rates and complete successfully. Has anyone every come across this issue before and do you have any suggestions on where to look to reduce the "queued" time ? The backups seem to run as they did prior to the upgrade, it seems to only be a problem with the restores.1.6KViews2likes6CommentsNetbackup Linux Bare Metal Restore using Open Source "Relax and Recover" (ReaR)
Just wanted to update NetBackup users about a open source tool that I have been using to successfully do bare metal Linux restores using our Netbackup. We use netbackup6.5 to backup our Linux and AIX servers.On our AIX servers we use a NIM server and we do network sysback backups on a weekly basis to provide the "Bare Metal" backup functionality. Unfortunately we had not Bare Metal restore functionality for Netbackup. I found a Open Source tool called "Relax and Recover" that provided a way to restore the OS using the full backups of the Linux systems on NetBackup. The tool as an option where it will create a bootable rescue iso file that contains all the Netbackup client executables and configuration to allow you to boot up your Linux server using the iso file then issue a simple command that will mount your OS disks separately and do a bprestore of all needed files to your actual OS disks. At the end of the restore the system re-create the GRUB information on the boot disk. The "mkerscue" is process can be ran any time with the Linux system is up and I just store that iso file on a separate server. The Netbackup code on the "Relax and Recover" was lacking some functionality that I wanted. Working with the developers they have accepted enhancements I made to the Netbackup (NBU) code. I added the functionality of excluding files and/or volume groups in the restore. I wanted this because I want to mainly use this to restore the OS only. I also added the functionality to restore from a point in time. They accepted the changes in SVN trunk 250. It will probably be in the next release of the product which should come out in one month's time. The web site for the product is: http://rear.sourceforge.net. They have a very useful program that has a very active supportive user base. The developers were very responsive and helpful to me to get the enhancements to the Netbackup interface in place. The program itself is just a big collection of bash shell scripts. This made adding the enhancements "doable' for a UNIX administrator such as myself. It is nice to be able to do a bare metal restoreto ourNetbackup backed up Linux servers without the need to do some type of clonzilla, "ghost" type backup which requires a system downtime..6.4KViews3likes17CommentsUnable to restore oracle DB backup
Hello, We are facing a strange issue, we have a backup appliance 5220 @ NB7.6. We are configured a DB backup using oracle intelligent policy and we are used dedupe pool as destination. Backups are success, but when we try to restore DB datafilesit fails. But we are able to restore SP file and control file. And if we use advanced disk or tapefor backupthe restore is success with datafiles. Wea re facing issues only when we use dedupe pool (pure disk). IF we use dedupe pool in inelligent backup policy, I Could see it swicthes to RMAN non snapshot proxy backup. See the logs below. 1179) INF - TYPE 'SBT_TAPE' 08/12/2015 21:54:58 - Info bphdb (pid=11179) INF - PARMS 'SBT_LIBRARY=/usr/openv/netbackup/bin/libobk.so64'; 08/12/2015 21:54:58 - Info bphdb (pid=11179) INF - SEND 'NB_ORA_CLIENT=svuphtquesttst,NB_ORA_SID=tqlive,NB_ORA_SERV=192.168.50.102,NB_ORA_POLICY=oracle_tqlive_test,NB_ORA_PARENT_JOBID=617139,NB_ORA_SCHED=Full,NB_ORA_PC_SCHED=Full,NB_ORA_PC_STREAMS=4'; 08/12/2015 21:54:58 - Info bphdb (pid=11179) INF - # DEDUPE storage unit was detected - switching to a non-snapshot proxy backup 08/12/2015 21:54:58 - Info bphdb (pid=11179) INF - BACKUP 08/12/2015 21:54:58 - Info bphdb (pid=11179) INF - INCREMENTAL LEVEL=0 PROXY And during restore I could see below error in dbclient log: 6:36:38 (621835.xxx) Found (11) files in (4) images for Restore Job ID 621835.xxx> 16:37:05.620 [8103] <4> logCommFile: <16:36:38 (621835.004) Restoring from copy 1 of image created Fri Aug 14 12:55:07 2015 from policy oracle_tqlive_test> 16:37:05.620 [8103] <4> logCommFile: <16:36:38 (621835.004) TAR STARTED 8212> 16:37:05.620 [8103] <4> logCommFile: <16:36:54 (621835.004) INF - Beginning restore from server svuphnetbcp to client svuphtquesttst.> 16:37:05.620 [8103] <4> logCommFile: <16:36:54 (621835.004) Read access to .AtTrIbUtEs.7 was denied> 16:37:05.620 [8103] <4> logCommFile: <16:36:54 (621835.004) Read access to .LoNg_VaLuEs.4 was denied> 16:37:05.620 [8103] <4> logCommFile: <16:36:54 (621835.004) Skipping to next file header...> 16:37:05.620 [8103] <4> logCommFile: <16:36:54 (621835.004) INF - TAR EXITING WITH STATUS = 3> 16:37:05.620 [8103] <4> logCommFile: <16:36:54 (621835.004) INF - TAR RESTORED 0 OF 2 FILES SUCCESSFULLY> And client tar log reports invalid tar header found. Please help on this issue. Regards, Anish698Views1like1CommentDissimilar BMR Win 2008 R2 boot fail
Hi! Performing a dissimilar BMR on the same server with the new disk results in an error loading the OS. I use the boot CD disk, then create a new configuration and mapping volume. Restoring from a new configuration with disabled restore system disks/volumes only. It goes without error. At the end of recovery the server reboots and task in console hangs on the point finalizing. OS does not boot and is not defined. Displays error system disk. If i boot from the installation disk Windovs, and try thebootrec.exe / rebuildbkd there is a error - not found a system. Version 7.5.0.7 netbackup. Master and media on Linux SUSE. Where I make a mistake?585Views0likes3CommentsBMR restore.
Hey i enrolled a Client on19th June. and first save ran on 20th June.Full backup is schedule to run Full on Monday and Tue-SunDifferential.. BMR is enabled for this. Now i have to do BMR restore for first backup (20th June data). is it possible to restore from first backup which is differential by Schedule? Below is more details of backup. Client Name Date Time Policy Backup Type Retention Scheduled ABCD 6/20/2014 1:09:28 AM A_eMON02.ms1 Differential 3 weeks Incr ABCD 6/21/2014 12:41:07 AM A_eMON02.ms1 Differential 3 weeks Incr ABCD 6/22/2014 12:40:00 AM A_eMON02.ms1 Differential 3 weeks Incr ABCD 6/23/2014 12:40:00 AM A_eMON02.ms1 Differential 3 weeks Incr ABCD 6/24/2014 12:40:00 AM A_eMON02.ms1 Full_Monday 3 weeks FullSolved1.6KViews0likes14CommentsError bptm(pid=5832) error requesting media, TpErrno = Robot operation failed
Hi, I have been having big problem with one of our Media Servers. We had an un-related problem with the OS, and had to rebuild the server. I've finally got our backups working again, but am unable to Vault images to tape. Robtest is able to successfully move tapes from slots to drives and visa versa, but no images are mounted to tape. Our backup procedure is as follows: Backup to Disk > Vault to ON site and OFF site copies > Set ON site copy to primary and delete the disk backup on Image Cleanup. Here is the full Vault job status report: 20/12/2013 20:06:46 - begin Duplicate 20/12/2013 20:07:13 - requesting resource backup4-dlt2-robot-tld-2 20/12/2013 20:07:13 - requesting resource backup4-dlt2-robot-tld-2 20/12/2013 20:07:13 - granted resource ON2348 20/12/2013 20:07:13 - granted resource QUANTUM.DLT-S4.006 20/12/2013 20:07:13 - granted resource backup4-dlt2-robot-tld-2 20/12/2013 20:07:13 - granted resource OF2562 20/12/2013 20:07:13 - granted resource QUANTUM.DLT-S4.009 20/12/2013 20:07:13 - granted resource backup4-dlt2-robot-tld-2 20/12/2013 20:07:16 - started process bptm (5800) 20/12/2013 20:07:23 - started process bpdm (5920) 20/12/2013 20:07:26 - started process bptm (5800) 20/12/2013 20:07:26 - mounting ON2348 20/12/2013 20:07:44 - begin reading 20/12/2013 20:18:57 - Error bptm(pid=5800) error requesting media, TpErrno = Mount canceled, device daemon is terminating 20/12/2013 20:18:57 - Warning bptm(pid=5800) media id ON2348 load operation reported an error 20/12/2013 20:18:57 - current media ON2348 complete, requesting next resource Any 20/12/2013 20:19:01 - Error nbjm(pid=8264) NBU status: 98, EMM status: The media server reported a system error 20/12/2013 20:19:11 - Error nbjm(pid=8264) nbrb status: LTID reset media server resources 20/12/2013 20:19:29 - Error bptm(pid=5800) INF - error requesting media (tpreq) (98), cannot continue with copy 2 20/12/2013 20:20:23 - Error bpduplicate(pid=8380) host backup4 backup id doradb04_1386981799 read failed, termination requested by administrator (150). 20/12/2013 20:20:23 - Error bpduplicate(pid=8380) host backup4 backupid doradb04_1386981799 write failed, error requesting media (tpreq) (98). 20/12/2013 20:21:17 - Error bpduplicate(pid=8380) Duplicate of backupid doradb04_1386981799 failed, error requesting media (tpreq) (98). 20/12/2013 20:21:18 - started process bptm (5832) 20/12/2013 20:21:18 - requesting resource backup4-dlt2-robot-tld-2 20/12/2013 20:21:18 - granted resource ON2348 20/12/2013 20:21:18 - granted resource QUANTUM.DLT-S4.007 20/12/2013 20:21:18 - granted resource backup4-dlt2-robot-tld-2 20/12/2013 20:21:20 - requesting resource backup4-dlt2-robot-tld-2 20/12/2013 20:21:20 - granted resource OF2562 20/12/2013 20:21:20 - granted resource QUANTUM.DLT-S4.008 20/12/2013 20:21:20 - granted resource backup4-dlt2-robot-tld-2 20/12/2013 20:21:24 - started process bpdm (4524) 20/12/2013 20:21:27 - started process bptm (5832) 20/12/2013 20:21:27 - mounting ON2348 20/12/2013 20:21:45 - begin reading 20/12/2013 20:21:50 - Error bptm(pid=5832) error requesting media, TpErrno = Robot operation failed 20/12/2013 20:21:50 - Warning bptm(pid=5832) media id ON2348 load operation reported an error 20/12/2013 20:21:51 - current media ON2348 complete, requesting next resource Any 20/12/2013 20:22:13 - started process bptm (5832) 20/12/2013 20:22:13 - mounting ON2348 20/12/2013 20:22:13 - granted resource ON2348 20/12/2013 20:22:13 - granted resource QUANTUM.DLT-S4.006 20/12/2013 20:22:13 - granted resource backup4-dlt2-robot-tld-2 20/12/2013 20:37:37 - Error bptm(pid=5832) error requesting media, TpErrno = Robot operation failed 20/12/2013 20:37:38 - Warning bptm(pid=5832) media id ON2348 load operation reported an error 20/12/2013 20:37:38 - current media ON2348 complete, requesting next resource Any 20/12/2013 20:37:44 - granted resource ON2348 20/12/2013 20:37:44 - granted resource QUANTUM.DLT-S4.009 20/12/2013 20:37:44 - granted resource backup4-dlt2-robot-tld-2 20/12/2013 20:37:46 - started process bptm (5832) 20/12/2013 20:37:46 - mounting ON2348 20/12/2013 20:53:12 - Error bptm(pid=5832) error requesting media, TpErrno = Robot operation failed 20/12/2013 20:53:12 - Warning bptm(pid=5832) media id ON2348 load operation reported an error 20/12/2013 20:53:12 - current media ON2348 complete, requesting next resource Any 20/12/2013 20:53:19 - granted resource ON2064 20/12/2013 20:53:19 - granted resource QUANTUM.DLT-S4.007 20/12/2013 20:53:19 - granted resource backup4-dlt2-robot-tld-2 20/12/2013 20:53:20 - started process bptm (5832) 20/12/2013 20:53:20 - mounting ON2064 20/12/2013 20:54:48 - started process bptm (5832) 20/12/2013 20:54:48 - mounting OF2562 20/12/2013 21:10:14 - Error bptm(pid=5832) error requesting media, TpErrno = Robot operation failed 20/12/2013 21:10:14 - Warning bptm(pid=5832) media id OF2562 load operation reported an error 20/12/2013 21:10:15 - current media OF2562 complete, requesting next resource Any 20/12/2013 21:10:21 - granted resource OF2562 20/12/2013 21:10:21 - granted resource QUANTUM.DLT-S4.006 20/12/2013 21:10:21 - granted resource backup4-dlt2-robot-tld-2 20/12/2013 21:10:23 - started process bptm (5832) 20/12/2013 21:10:23 - mounting OF2562 20/12/2013 21:24:16 - Error bptm(pid=5832) FREEZING media id OF2562, Medium identifiers do not match 20/12/2013 21:24:16 - Warning bptm(pid=5832) media id OF2562 load operation reported an error 20/12/2013 21:24:17 - current media OF2562 complete, requesting next resource Any 20/12/2013 21:45:53 - started process bptm (5832) 20/12/2013 21:45:53 - mounting OF2142 20/12/2013 21:45:53 - granted resource OF2142 20/12/2013 21:45:53 - granted resource QUANTUM.DLT-S4.009 20/12/2013 21:45:53 - granted resource backup4-dlt2-robot-tld-2 20/12/2013 22:01:19 - Error bptm(pid=5832) error requesting media, TpErrno = Robot operation failed 20/12/2013 22:01:19 - Warning bptm(pid=5832) media id OF2142 load operation reported an error 20/12/2013 22:01:20 - current media OF2142 complete, requesting next resource Any 20/12/2013 22:01:26 - started process bptm (5832) 20/12/2013 22:01:26 - mounting OF2142 20/12/2013 22:01:26 - granted resource OF2142 20/12/2013 22:01:26 - granted resource QUANTUM.DLT-S4.008 20/12/2013 22:01:26 - granted resource backup4-dlt2-robot-tld-2 I am able to inventory the robot successfully, and the robot is capable of emptying tapes from the media access port, and placing them in slots. We are using NetBackup 6.5.6. Up until last week the full procedure worked perfectly, so our OS, library and NetBackup version are all definitely cross-compatible. Any help would be gratefully received!Solved11KViews2likes9CommentsMajor Data loss situations - OSX Mavericks + WD drive software + external Hard drives
Please be aware that there are serious data loss issues ongoing with Mac OSX Maverics and Western Digital drive sofware. Both the Apple support and WD forums have mutiple customer reports of total external drive data loss. The data loss is not limited to systems activly using the WD software and drives, other vendor external hard drives are being lost. Personally I just lost 1TB of Time machine backups on a Iomega external drive. I did have a WD myBook for a while about 2 years ago but was not aware the WD drive software was still active on this machine. Current advice from Western Digital is to uninstall the WD drive software before going to Mavericks. Uninstaller is here ..... http://support.wdc.com/product/download.asp?groupid=126&sid=214&lang=en This situation as already caused a lot of digital pain, loss of data and as a techincal person makes me sad in so many ways. Clive467Views2likes0Comments