Mike_3G
Level 3
Joined 13 years ago
User Profile
User Widgets
Contributions
NBU 7.5 and vmware questions
No urgent problem to be solved, just a question about VMware and definition of a client. If I create a VMware policy and automatically select all the VMs on an ESXi host, do I need a client license for each VM on that host? There is no client software installed in the VMs. But, I can see each VM listed when I execute /usr/openv/netbackup/bin/admincmd/bpplclients -allunique from the command line. I'm just wondering how this is handled. OTOH, in the Java console, when I'm connected to the Master Server and I select NetBackup Management > Host Properties > Clients, none of the VMs appear in the list. thanks, MikeSolved603Views0likes2CommentsHardware and OS refresh for media server
Currently - I have 2 media servers on RHEL 4 running NBU 7.0.1 and I want to do a hardware/OS refresh to Centos 6, followed by NBU upgrade to 7.5.0.3. The master server has already been successfully upgraded to RHEL 5.8, NBU 7.5.0.3. My questions are: 1. If I reuse the IP/hostname for the media servers, do I need to decomission them during the refresh/upgrade process? 2. Do I install NBU 7.5 (and 7.5.0.3) directly on the media server as opposed to the Master Server, where I had to install 7.0.1 prior to upgrading? Thanks, MikeSolved744Views0likes3CommentsRe: Re-configuring tape drives NBU 7.0.1
Looking at the device serial numbers helped out (# tpconfig -dl). The master server discovered 12 drives & 1 robot, which is correct. One of the media servers (which I didn't touch) showed a new drive marked DOWN (# tpautoconf -report_disc). It's serial number didn't match any of the S/Ns reported by the Master server. From the GUI, I deleted the "phantom" drive. Then I re-ran the device configuration wizard. It appears that everything is now OK. Thanks for your help. -Mike586Views0likes0CommentsRe-configuring tape drives NBU 7.0.1
Hi, I'm running NBU 7.0.1 on RHEL5. We have a Scalar i2000 tape robot with 12 drives. Last week I completed a hardware / OS refresh and after the Hot Catalog Restore most everything is working OK. But I have one tape drive that is marked "down" and I'd like to reconfigure the drives and verify the paths are correct. None of the drives were changed. This is the 1st time I've experienced this issue so I was wondering if I should just re-run the Drive configuration wizard or if there's another way to accomplish this. Mike Some more info: [root@x-bkup-01 ~]# tpautoconf -t TPAC60 IBM ULTRIUM-TD3 93GM 1210381803 -1 -1 -1 -1 /dev/nst7 - - TPAC60 IBM ULTRIUM-TD4 B7C0 1310113137 -1 -1 -1 -1 /dev/nst10 - - TPAC60 IBM ULTRIUM-TD4 B7C0 1310104177 -1 -1 -1 -1 /dev/nst11 - - TPAC60 IBM ULTRIUM-TD3 93GM 1210127918 -1 -1 -1 -1 /dev/nst6 - - TPAC60 IBM ULTRIUM-TD3 93GM 1210127931 -1 -1 -1 -1 /dev/nst9 - - TPAC60 IBM ULTRIUM-TD3 93GM 1210127910 -1 -1 -1 -1 /dev/nst8 - - TPAC60 IBM ULTRIUM-TD3 93GM 1210186652 -1 -1 -1 -1 /dev/nst3 - - TPAC60 IBM ULTRIUM-TD3 93GM 1210128000 -1 -1 -1 -1 /dev/nst1 - - TPAC60 IBM ULTRIUM-TD3 93GM 1210128204 -1 -1 -1 -1 /dev/nst0 - - TPAC60 IBM ULTRIUM-TD4 B7C0 1310112738 -1 -1 -1 -1 /dev/nst4 - - TPAC60 IBM ULTRIUM-TD3 93GM 1210184448 -1 -1 -1 -1 /dev/nst2 - - TPAC60 IBM ULTRIUM-TD4 B7C0 1310113141 -1 -1 -1 -1 /dev/nst5 - - [root@x-bkup-01 ~]# tpautoconf -r TPAC60 ADIC Scalar i2000 607A ADIC203102197_LL0 -1 -1 -1 -1 /dev/sg6 - - [root@x-bkup-01 ~]# tpautoconf -report_disc ======================= New Device (Drive) ======================= Inquiry = "IBM ULTRIUM-TD3 93GM" Serial Number = 1210381803 Drive Path = /dev/nst7 Found as TLD(0), Drive = 8Solved551Views0likes4CommentsRe: Full Catalog Backup
Thx for the replies. @revaroo - the path is not a link. The Catalog Backup completes with status (0) and files exist in the target directory, for example: -rw------- 1 root root 1719 Apr 22 14:34 Catalog_Hot_Backup_1335117966_FULL -rw------- 1 root root 1719 Apr 23 02:35 Catalog_Hot_Backup_1335161154_FULL -rw------- 1 root root 1719 Apr 23 14:56 Catalog_Hot_Backup_1335205679_FULL But before I turn off the server for the hardware replacement phase, I just want to feel like I can restore the catalog! Better safe than sorry as they say :) Mike1.6KViews0likes0CommentsFull Catalog Backup
NBU 7.0.1 running on RHEL4, and planning to upgrade hardware, OS, and NBU. I want to make sure I'm getting a good Full Catalog Backup before going ahead. I didn't do the original installation, and I don't have a lot of history to fall back on. I'm looking at our Catalog Hot Backup policy (policy type = NBU-Catalog). On the Disaster Recovery tab, the Path: is set to/usr/openv/netbackup/disaster_recovery. This seems to contradict the NBU 7.0.1 Administrator's Guide - pg.640 says not to save the info to a local disk and pg. 642 says specifically: The path for the disaster recovery information cannot be to a directory that is on the same partition as /usr/openv/netbackup. If the path is to a location on the same partition as /usr/openv/netbackup, NetBackup displays a status 20 error message. The message states that the disk path is invalid. Change the path on the Disaster Recovery tab to a directory on a different partition. The email notification that gets sent out says: Backup on client x-bkup-01 for user root by server x-bkup-01 succeeded. Policy = Catalog_Hot_Backup Schedule = Full File list --------- CATALOG_DRIVEN_BACKUP So, am I really getting successful Catalog Backups? Thanks, MikeSolved1.6KViews0likes7CommentsDual upgrade - version and OS
Hi, Our master server is currently running NBU 7.0.1 on RHEL 4. My goal is to upgrade NBU to 7.5. The compatibility list says that NBU 7.5 is not supported on RHEL4, so I'll need to upgrade the OS first. I'm going to build a new server with RHEL 5 and take the IP address of the old server. My questions are about the migration. Do I have to install 7.0.1 on the new server, or can I go right to 7.5? If so, how do I migrate over the catalog? Seems standard stuff, but it's the 1st time I've dealt with it. Thanks, MikeSolved277Views0likes2Comments