Hi Everyone ,
I have one window server 2008 r2 where oracle running .
netbackup version : 7.5.0.6
Backup type : incremental backup and weekly full backup .
getting error on some drive not being backed up .
Bpcd and bpbkar log attched .
I have a problem with hotadd.
There is a way to limit the number of disk that can be added to a host?
The backup policy can limit only the number of the virtual machines that can be backupped at the same time, but I have many virtual machine with more that one disk. In this case netbackup try to add too many disks on the same media server and the backup crash. I've tried to add more controllers but the problem remains.
I would like to limit the number of disk that can be added. There is a way to do it?
Thanks,
Max
What is the expected behaviour when:
Whenever NBU master has been restarted in our environment (a VCS cluster), we see:
a. All jobs are killed so they have to restart from scratch.
b. Jobs are not killed cleanly so in particular for SAP backups, the Oracle database is left in backup mode, meaning when the backup is restarted it fails.
So I am hoping there is someway to cleanly stop the NBU master (preferably integrated into the VCS cluster) so that:
I did look in the "admin volume 1" guide and this says when shutting down NBU "make sure that no jobs are running", but this will never be the case in our environment, so for example there are 32 active jobs at the moment and we could potentially have over 100 active jobs, and in the docs, I coudn't find any guidance as to what you do if you have jobs running.
Mike
I have license keys on our NetBackup host that go back over ten years. Should I ever delete the old keys, and if so how often?
Currently I have a policy where I run a full backup three days a week and an incremental four days a week (the days are hardcoded in the schedules).
I tried setting up a test policy with the full backup to run every 2 days at 10 am. And then I also defined a incremental schedule to run every 2 days at 10 am. When the policy ran for the first time (yesterday) it ran the full backup (as expected).
I hoped to see that the incremental schedule would have then run today but it didnt.
Anyone have any ideas on how to alternate full and incrementals every other day?
Hi All,
hoping someone can point me in the right direction.
I am trying to migrate my master netbackup server from solaris on sparc to x86 linux.
I successfully exported the catalog. I installed netbackup on linux. I created the same links/paths as original. I am using exact same hostname.
I go through the catalog recover wizard, and it says it completes successfully.
But... I am missing tons of backups when I try to find them in the gui.
For instance, in the log file for the catalog recovery there is this:
20:38:48 (2.001) /netbackup_db/db/images/asfasitp02/1346000000/
20:38:48 (2.001) /netbackup_db/db/images/asfasitp02/1346000000/catstore/NETAPP-SAP-GPD-HOT_1346480190_FULL.f-list
20:38:48 (2.001) /netbackup_db/db/images/asfasitp02/1346000000/catstore/NETAPP-SAP-GPD-HOT_1346480190_FULL.f_imgHeader0
20:38:48 (2.001) /netbackup_db/db/images/asfasitp02/1346000000/catstore/NETAPP-SAP-GPD-HOT_1346480190_FULL.f_imgRecord0
20:38:49 (2.001) /netbackup_db/db/images/asfasitp02/1346000000/catstore/NETAPP-SAP-GPD-HOT_1346480190_FULL.f_imgDir0
20:38:49 (2.001) /netbackup_db/db/images/asfasitp02/1346000000/catstore/NETAPP-SAP-GPD-HOT_1346480190_FULL.f_imgFile0
20:38:49 (2.001) /netbackup_db/db/images/asfasitp02/1346000000/catstore/NETAPP-SAP-GPD-HOT_1346480190_FULL.f_imgNDMP0
20:38:49 (2.001) /netbackup_db/db/images/asfasitp02/1346000000/catstore/NETAPP-SAP-GPD-HOT_1346480190_FULL.f_imgExtraObj0
20:38:44 (2.001) /netbackup_db/db/images/asfasitp02/1338000000/catstore/NETAPP-SAP-APD-HOT_1338346755_FULL.f_imgNDMP0
20:38:44 (2.001) /netbackup_db/db/images/asfasitp02/1338000000/catstore/NETAPP-SAP-APD-HOT_1338346755_FULL.f_imgExtraObj0
20:38:44 (2.001) /netbackup_db/db/images/asfasitp02/1338000000/catstore/NETAPP-SAP-APD-HOT_1338346755_FULL.f_imgUserGroupNames0
20:38:44 (2.001) /netbackup_db/db/images/asfasitp02/1338000000/catstore/NETAPP-SAP-APD-HOT_1338346755_FULL.f_imgStrings0
But if I do an ls on the directory:
root@chazbs02 { /usr/openv/netbackup/logs/user_ops/root/logs }
> 326 $ ls /netbackup_db/db/images/asfasitp02/1338000000
ls: cannot access /netbackup_db/db/images/asfasitp02/1338000000: No such file or directory
So the log file said it was restoring, but it's not there at the end?
Here is the bottom of the log file from restore:
20:39:31 (2.001) chmod 655 /netbackup_db/db/class/NETAPP-SAP-P01-COLD to reset permissions.
20:39:31 (2.001) chmod 2750 /opt/openv/var/websvccreds/WSL to reset permissions.
20:39:31 (2.001) chmod 2750 /opt/openv/var/global/wsl/credentials/clients to reset permissions.
20:39:31 (2.001) chmod 2750 /opt/openv/var/global/wsl/credentials to reset permissions.
20:39:42 (2.001) INF - TAR EXITING WITH STATUS = 0
20:39:42 (2.001) INF - TAR RESTORED 209596 OF 209596 FILES SUCCESSFULLY
20:39:42 (2.001) INF - TAR KEPT 0 EXISTING FILES
20:39:42 (2.001) INF - TAR PARTIALLY RESTORED 0 FILES
20:39:42 (2.xxx) INF - Status = the requested operation was successfully completed.
20:40:07 INF - Database restore started
Restore started Thu Feb 12 20:40:10 2015
20:40:11 (4.001) Restoring from copy 1 of image created Fri Jan 9 14:00:32 2015 from policy Catalog-Backup
20:40:11 (4.001) TAR STARTED 31364
20:40:12 (4.001) INF - Beginning restore from server chazbs02 to client chazbs02.
20:40:14 (4.001) /opt/openv/db/staging/DARS_DATA.db
20:40:14 (4.001) /opt/openv/db/staging/DARS_INDEX.db
20:40:15 (4.001) /opt/openv/db/staging/DBM_DATA.db
20:40:15 (4.001) /opt/openv/db/staging/DBM_INDEX.db
20:40:15 (4.001) /opt/openv/db/staging/EMM_DATA.db
20:40:16 (4.001) /opt/openv/db/staging/EMM_INDEX.db
20:40:16 (4.001) /opt/openv/db/staging/JOBD_DATA.db
20:40:16 (4.001) /opt/openv/db/staging/NBDB.db
20:40:16 (4.001) /opt/openv/db/staging/NBDB.log.1
20:40:16 (4.001) /opt/openv/db/staging/SEARCH_DATA.db
20:40:16 (4.001) /opt/openv/db/staging/SEARCH_INDEX.db
20:40:17 (4.001) /opt/openv/db/staging/SLP_DATA.db
20:40:17 (4.001) /opt/openv/db/staging/SLP_INDEX.db
20:40:17 (4.001) /opt/openv/db/staging/databases.conf
20:40:17 (4.001) /opt/openv/db/staging/server.conf
20:40:17 (4.001) /opt/openv/db/staging/vxdbms.conf
20:40:17 (4.001) INF - TAR EXITING WITH STATUS = 0
20:40:17 (4.001) INF - TAR RESTORED 16 OF 16 FILES SUCCESSFULLY
20:40:17 (4.001) INF - TAR KEPT 0 EXISTING FILES
20:40:17 (4.001) INF - TAR PARTIALLY RESTORED 0 FILES
20:40:18 (4.001) Status of restore from copy 1 of image created Fri Jan 9 14:00:32 2015 = the requested operation was successfully completed
20:40:18 INF - Server status = 0
20:40:18 (4.xxx) INF - Status = the requested operation was successfully completed.
20:40:23 INF - Database recovery started
20:40:23 WRN - No database backup found in /usr/openv/db/staging for NBAZDB defined in vxdbms.conf
20:40:23 INF - Shutting down databases
20:40:24 INF - Applying transaction log: /usr/openv/db/staging/NBDB.log.1
20:40:24 INF - Applying transaction log: /usr/openv/db/staging/NBAZDB.log.1
20:40:24 INF - Applying transaction log: /usr/openv/db/staging/NBDB.log
20:40:24 INF - Moving database files from /usr/openv/db/staging
20:40:24 INF - Source /usr/openv/db/staging/EMM_DATA.db
20:40:24 INF - Destination /usr/openv/db/data/EMM_DATA.db
20:40:24 INF - Source /usr/openv/db/staging/DBM_DATA.db
20:40:24 INF - Destination /usr/openv/db/data/DBM_DATA.db
20:40:25 INF - Source /usr/openv/db/staging/DARS_DATA.db
20:40:25 INF - Destination /usr/openv/db/data/DARS_DATA.db
20:40:25 INF - Source /usr/openv/db/staging/SEARCH_DATA.db
20:40:25 INF - Destination /usr/openv/db/data/SEARCH_DATA.db
20:40:25 INF - Source /usr/openv/db/staging/JOBD_DATA.db
20:40:25 INF - Destination /usr/openv/db/data/JOBD_DATA.db
20:40:25 INF - Source /usr/openv/db/staging/SLP_DATA.db
20:40:25 INF - Destination /usr/openv/db/data/SLP_DATA.db
20:40:25 INF - Source /usr/openv/db/staging/NBDB.db
20:40:25 INF - Destination /usr/openv/db/data/NBDB.db
20:40:25 INF - Source /usr/openv/db/staging/EMM_INDEX.db
20:40:25 INF - Destination /usr/openv/db/data/EMM_INDEX.db
20:40:25 INF - Source /usr/openv/db/staging/DBM_INDEX.db
20:40:25 INF - Destination /usr/openv/db/data/DBM_INDEX.db
20:40:26 INF - Source /usr/openv/db/staging/DARS_INDEX.db
20:40:26 INF - Destination /usr/openv/db/data/DARS_INDEX.db
20:40:26 INF - Source /usr/openv/db/staging/SEARCH_INDEX.db
20:40:26 INF - Destination /usr/openv/db/data/SEARCH_INDEX.db
20:40:26 INF - Source /usr/openv/db/staging/SLP_INDEX.db
20:40:26 INF - Destination /usr/openv/db/data/SLP_INDEX.db
20:40:26 INF - Creating /usr/openv/db/data/vxdbms.conf
20:40:26 INF - Creating /usr/openv/var/global/server.conf
20:40:26 INF - Creating /usr/openv/var/global/databases.conf
20:40:26 INF - Starting up databases
20:40:31 INF - Database recovery successfully completed
20:40:31 INF - Recovery successfully completed
20:40:42 INF - Catalog recovery has completed.
Does anything look out of place? There are thousands of entires in the log of images that were restored, but they are not there.
I'm also going to attach the entire catalog restore log in case anyone can figure this out.
Hello,
Getting ready to do a Netbackup migration from v7.1.0.3 to v7.6.0.4. - with the migration moving from one Netbackup domain with servers running W2K3 joined to Active Directory Domain "X" to a new Netbackup domain with servers running W2K8R2 joined to Active Directory Domain "Y". The same storage devices (ie. tape libraries, OST devices, etc) are being used.
Familiar with the limitations of moving a Netbackup catalog to a new master server with a different name. We have gotten around this in the past - albeit the new Netbackup system had all new storage devices. Essentially - what we did is built a "net new" Netbackup environment and retired the existing environment (including storage devices) with the exception of the lone Master Server. The lone Master Server was essentially turned into a read-only catalog look-up for restoring legacy data. When one of the backup operators get a request to restore data that pre-dates the existing Netbackup system - they would go to what i call the "Legacy Master Catalog Lookup Server" to lookup the tapes needed to restore the requested the data. Once they had identified and recalled the tapes - they would simply perform an import of the tapes into the new Netbackup environment and restore the data. This has worked well for several years and allowed us to avoid having to import the old catalog and a few thousand tapes into the new Netbackup system (the legacy NB was using LTO2 drives and the new Netbackup system had new LTO4 drives - hence we didn't want to import all of the LTO2 tapes). No disk/OST existed on the orginal Netbackup system. The only caveat was that you have to essentially freeze the lone Netbackup server so no changes would ever be made to the databases/images etc. - we even virtualized the Catalog Lookup server - so we didn't have to maintain the old hardware.
With this upcoming migration - we do not have new storage devices. Currently, the new 7.6.0.4 Netbackup environment can see all of the storage devices/OST shares, etc. of the existing 7.1.0.3 Netbackup environment. We - for obviously reasons have not run any jobs on the new system - looking at doing a cut-over on a single weekend. We were originally planning on doing what we had done with the previous migration - creating a stand-a-lone NB Catalog lookup server but after reading through the Recovery Without Import - Whitepaper - it appears we might be able to leverage it to move the exsiting catalog info into the new system without having to touch the physical media. At least from what i'm reading - it warrants looking into further.
If anyone has successfully used the Recovery Without Import methodology - would greatly appreciate any insight, tips, gotchas that would help us make a decision on whether or not to use this methodology.
Thx,
Greg
Hi I have a new setup
with a physical tape library 4048 and a VTL emulated as ESL E-series and jobs to both get stuck at "mounting"
Netbackup 7.6.0.1 (windows 2012)
Below is the output I get from various commands before I configure the storage devices.
c:\Program Files\Veritas\Volmgr\bin>tpautoconf.exe -t
TPAC60 HP Ultrium 6-SCSI 23CW HU1338YDY9 1 0 0 0 Tape0 - -
TPAC60 HP Ultrium 6-SCSI 23CW HU1338YDW8 1 0 1 0 Tape1 - -
TPAC60 HP Ultrium 5-SCSI ED51 CZ134309V4 1 0 20 0 Tape2 - -
TPAC60 HP Ultrium 5-SCSI ED51 CZ134309V2 1 0 21 0 Tape3 - -
TPAC60 HP Ultrium 5-SCSI ED51 CZ134309V3 1 0 22 0 Tape4 - -
TPAC60 HP Ultrium 5-SCSI ED51 CZ134309V5 1 0 23 0 Tape5 - -
c:\Program Files\Veritas\Volmgr\bin>tpautoconf.exe -r
TPAC60 HP MSL G3 Series 8.60 MXA343Z0SD 1 0 1 1 Changer0 - -
TPAC60 HP ESL E-Series EL51 CZ13430B00 1 0 8 0 - - -
Output of scan
------------------------------------------------------------
Device Name : "Changer0"
Passthru Name: "Changer0"
Volume Header: ""
Port: 1; Bus: 0; Target: 1; LUN: 1
Inquiry : "HP MSL G3 Series 8.60"
Vendor ID : "HP "
Product ID : "MSL G3 Series "
Product Rev: "8.60"
Serial Number: "MXA343Z0SD"
WWN : ""
WWN Id Type : 0
Device Identifier: "HP MSL G3 Series MXA343Z0SD"
Device Type : SDT_CHANGER
NetBackup Robot Type: 8
Removable : Yes
Device Supports: SCSI-5
Number of Drives : 3
Number of Slots : 48
Number of Media Access Ports: 0
Drive 1 Serial Number : "HU1338YDW8"
Drive 2 Serial Number : "HU1338YDY9"
Drive 3 Serial Number : "HU1338YDY9"
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name : ""
Passthru Name: ""
Volume Header: ""
Port: 1; Bus: 0; Target: 8; LUN: 0
Inquiry : "HP ESL E-Series EL51"
Vendor ID : "HP "
Product ID : "ESL E-Series "
Product Rev: "EL51"
Serial Number: "CZ13430B00"
WWN : ""
WWN Id Type : 0
Device Identifier: "HP ESL E-Series CZ13430B00"
Device Type : SDT_CHANGER
NetBackup Robot Type: 8
Removable : Yes
Device Supports: SCSI-3
Number of Drives : 4
Number of Slots : 96
Number of Media Access Ports: 1
Flags : 0x0
Reason: 0x0
Issue I am having is that while configuring devices the drives dont show as attached to the tape library and lists as standalone.I manually try and add the drives to each robot and seems to work only that during the backup test the job is stuck at mounting for VTL and MSL library.
Couple of things I noticed..
1) In the above output of scan the 2nd changer (VTL) doesnt show any device name or pass thru name..
Under device manager this shows up as unknown medium changer even though the drivers are installed and i cant seem to get it to change.
2) While configuring the MSL 4048 library using the device config wizrd in the box where it shows "review the devices netbackup has found" the MSL has an red X sign stating unusable. When i check the properties it shows "Illegal drive type in robot."
But this is a standard MSL 4048 HP tape library with LTO6 tape drives .
I dont see any hardware related errors in event logs.
Any suggestions..for both these issues ?
Thanks
Hello,
I'm working with Storage and I'm new with NetBackup.
I have two storages that are allowed to perform replication of LUNS. I don´t have qlogic HBAs to perform the Fibre Transport Configuration.
In my environment, one media_server is remote and doesn´t exists a tape library in the remote location ( less than 100 GB of Backup Daily are generated). the other MediaServer has a tape Library.
I´m thinking with abouth the Basic Disk Format:
When a backup is performed on a Basic Disk format, it generates a file with the backup content or are created several scattered files that represent the backup that was done?
Later I can migrate this Basic Disk to Tape?
If this Basic Disk is coupled to a Media Server, rather than being linked to the Master Server in any case the Master Server database will be updated in order to allow to perform data restoration, right?
But:
1 - If a backup is performed on a MediaServer_A to the Basic Disk;
2 - So, This Basic Disk is detached from the Media Server (MediaServer_A);
3 - Cloned and Replicated using the Storage;
4 - Going mounted to another Media Server (MediaServer_B);
The MediaServer_B would be able to recognize the Basic Disk?
Could from MediaServer_B copy the data to a tape ?
Once the MediaServer_B could recognize the basic disk generated by MediaServer_A, the MasterServer NetBackup could recognize that he changed his backup media server?
To return to MediaServer_A:
1 - Remove the MediaServer_B disk;
2 - Restore the mount point Media_server_A;
3 - Remove the clone / previous snap up next window for new clone or pointer.
Have you ever seen this kind of situation before ?
Best Regards,
SledgeHammer
Good Day!
We are running Symantec Netbackup 7.6.0.3 on a Linux Red Hat 6
I wanted to inquire if our Netbackup would be able to support or backup our Synology NAS RX814 and RX415+
Any recommendation or support link I could look into is highly appreciated.
Hello Experts,
I found one file named errors on c:/programfiles/veritas/netbackup/db/errors.
I could found the below entries on the below file. This is the same time we were experiencing issue on our master server.
02/12/15 14:57:29 L00061 5 OPEN_ERROR Drive005
02/12/15 14:57:29 L00059 3 OPEN_ERROR Drive002
02/12/15 17:01:03 L00011 -1 RESERVE_ERROR Drive005 0 1 0 0
02/12/15 20:31:06 L00085 -1 RESERVE_ERROR Drive007 0 1 0 0
02/12/15 20:31:22 L00041 -1 RESERVE_ERROR Drive002 0 1 0 0
02/12/15 20:31:32 L00078 -1 RESERVE_ERROR Drive001 0 1 0 0
02/12/15 23:20:26 L00085 -1 RESERVE_ERROR Drive005 0 1 0 0
02/13/15 00:22:11 L00044 -1 RESERVE_ERROR Drive005 0 1 0 0
02/13/15 01:17:23 L00011 -1 RESERVE_ERROR Drive002 0 1 0 0
02/13/15 01:17:27 L00085 -1 RESERVE_ERROR Drive005 0 1 0 0
Could you pls let me know what is this file and what is it refering here.
Hello Experts,
We were experiencing issue in one of our master server i.e Win2008. So we moved the netbackup services to Node1. backup ran fine for 2-3 hours and later they were giving the error code 98 on the Node1. So finally we moved the netbackup services to node2 that was actual and backups were fine.
(1) There were the below event logs on node1
TLD(1) [7808] unable to read exit status from tldcd: Error number: (10060), stat = -3
TLD(1) [12200] Drive 7 (device 5) has not become ready. Last status: The requested resource is in use.
TLD(1) [13832] Drive 2 (device 2) has not become ready. Last status: The requested resource is in use.
Request for media ID L00087 is being rejected because mount requests are disabled (reason = robotic daemon going to DOWN state)
Pls help.
(2) Whenever we move netbackup services from Node1 to Node2 or vice versa we are losing the activty job logs. I mean if 10 jobs are running on node 1 and we have to move netbackup services to Node2. On node 2 we could see only the new jobs not the 10 jobs that were running on node1 same is happening on other server as well.
Pls help
Hello Experts,
Pls let me know where to find the last full/incremental backup got successfull or not? If there is no ops center and jobs details in activity monitor?
Thanks,
Environment is: Master:7.5.0.4 (Linux)
Meda server: txaust03app69 (Windows 2003 server ) (VMWare backup host)
Hi Friends,
Could you please guide me how to prepare for Netbackup certifation exam and any dumps for 7.6.x , and also exam centers , cost of exam fee..
Thanks in advance .
Hello,
We've migrated the data from Windows 2003 to 2008 (VM).
So We would like to the data backup for Windows 2008 using Veritas running in the Windows 2003.
We got the fail to backup.
Is it possible to backup the data in this situation??
Hello,
We've migrated the data from Windows 2003 to 2008 (VM).
So We would like to the data backup for Windows 2008 using Veritas running in the Windows 2003.
We got the fail to backup.
Is it possible to backup the data in this situation??
Good morning Mariane, can you help me?
I'm having trouble backing up a client that has dinamic disk.
My environment:
Master: 7.6.02 OS: Linux red. hat 6 - Veritas Cluster
Medias Servers: 07/06/02 - Linux red. hat 6
Client Windows 2003 (Virtual Machine) - Hyper-V Cluster 6.3.9 ....
I run the backup via client installed on this virtual machine and returns error 156.
The netbackup supports not do the same with backup client installed to dinamic disk ???
Thank you very much
Hi all,
How can I restart an "duplication" job that failed with status 96 (storage unit has none available)?
Thanks.
Master server is Windows 2012 R2
Two media servers windows 2012 R2
NBU 7.6.0.4
Following is the error message in /var/adm/messages
ombs_bkp tldd[10218]: [ID 320639 daemon.error] TLD(0) unavailable: initialization failed: Unable to sense robotic device
ombs_bkp tldcd[10227]: [ID 498531 daemon.error] user scsi ioctl() failed, may be timeout, errno = 5, I/O error
ombs_bkp last message repeated 1 time
ombs_bkp tldcd[10227]: [ID 406877 daemon.error] TLD(0) mode_sense ioctl() failed: I/O error
ombs_bkp tldcd[10227]: [ID 498531 daemon.error] user scsi ioctl() failed, may be timeout, errno = 5, I/O error
Following is the output of "robtest"
user scsi ioctl() failed, may be timeout, errno = 5, I/O error
user scsi ioctl() failed, may be timeout, errno = 5, I/O error
mode_sense ioctl() failed: I/O error
Robot Diagnostics also fails at every step with the following error.
Communication failure with robot control daemon.
The output of cfgadm -al is the following for the failing drive and robot.
Ap_Id Type Receptacle Occupant Condition
c0 fc-fabric connected configured unknown
c0::50014380160076e2 unavailable connected configured failing