Highlighted

Upgrade issue

I have serious problem in my customer site.


-----------------------------------------------------------------------------------

* Site infra

  Master server : AIX 5.2 (1ea)
  Media server : AIX 5.2 or AIX 5.3 (16ea) and Windows 2003 server (3ea)

-----------------------------------------------------------------------------------

Upgrade 5.1MP7 to 6.5MP6.

So, Upgrade step is nothing problem.

and Most Drive states is "PEND-TLD" when backup begun to 3~4 hour after.

I checked the tape device and robdrnum and nothing problem.

What is problem factor ?

Give some advice.

Thanks.
1 Solution

Accepted Solutions
Highlighted
Accepted Solution!

Correct. If all the media

Correct. If all the media servers have the correct license keys installed (Server, Library based tape drives, Shared Storage Option) the wizard will scan all media servers, detect the same tape drives on the media servers and configure them as shared.

View solution in original post

12 Replies
Highlighted

PEND-TLD means there's a

PEND-TLD means there's a reservation conflict somewhere.
This means you have SSO configured?
Did you upgrade master as well as all media servers? SSO does not work very well with a 6.x and 5.x mix.
Was nbpushdata done for each media server?

If all media servers have also been upgraded, I suggest you delete all devices and re-run the device config wizard to ensure all device mappings are 100% correct and that all drives are cofigured as 'Shared' for all media servers.

PEND status could be a result of one (or more) media server believing that it has exclusive access to the drive (not shared). Reconfiguring using the wizard will ensure that the drives are configured as 'shared' for all media servers.
Highlighted

thanks reply

Upgrade of the all netbackup module (master & media)
and move the media db in media server

So, delete the all device.

and device reconfigration at upgrade after.

not mixed netbackup version ...

upgrade step is not failed and not problem.

Highlighted

I'm not sure I fully


I'm not sure I fully understand the following:

move the media db in media server

I hope you mean 'nbpushdata' was done on each media server?

There is a lot more than media db that need to move off media server...

Run 'vmoprcmd -d' on each media server to ensure that they all have same view of devices.

Also run 'vmdareq' on master server to verify device reservation.
Highlighted

thanks reply

Before the upgrade step....

In media server (media db) move to master

below the command
#> bpmedia -movedb media_id -oldserver  media -newserver master

and media server list clear(delete the drive, robot) and new install(6.5MP6)

Upgrade only master server and "nbpushdata" is well done.

So, restore the media ownership at each media server.

I guess... Definitely, upgrade step is not problem....


 

Highlighted

Not what was ment

doing the bpmedia -movedb - just moved who owned the tapes.

As Marianne asked did you do the nbpushdata on each media server after?
Did you upgrade the media servers?

Highlighted

It seems as if the media

It seems as if the media servers were decommissioned and re-installed. It is definitely not the best or recommended way to upgrade.
During the re-install, were all the necessary license keys added? NBU Server, Library-based tape drives, Shared Storage.

Was the Device Config Wizard used to configure the drives? If the GUI in the Devices section was used, the drives are added as non-SSO. This means that each media server will believe that it has exclusive ownership of tape drives. I have given a couple of commands in my previous post to check/verify.

As I've suggested before - to be 100% sure that Device configuration is correct, delete all drives and robots. Then use the wizard to reconfigure. This will take about 5 minutes. Otherwise you can spend the next week trying to troubleshoot.
Highlighted

Below the upgrade

Below the upgrade procedure

1. check the available capacity (volume) / delete the log files
     (daemon stop and compress the existing module using the "tar" command)


2.  move the media db at master server
      (bpmedia -movedb -m <media_id> -newserver <master server> -oldserver <media server>)

3. delete the tape device configuration (all server)
     (tpconfig -multiple_delete -drive 0:1:2:3:4:5:6:7:8:9:X and tpconfig -multiple_delete -robot 0:1:2:3:4:5:X)

4. upgrade the master server (delete the media server list at bp.conf)

5. updating catalog DB
    (/usr/openv/netbackup/bin/nbpushdata -add)

6.  Install the media server
    (delete the media module and new install the 6.5.6)

7. Verify the catalog data
     (check the catalog data using the bpmedialist, bpimagelist and show the java console)

8. configure the ovpass and backup drive (master & media)
     (using the tpconfig command)

9. check the communicate media server and check the drive status
     (nbemmcmd -getemmserver and vmoprcmd)

10. restore the media owner
     (bpmedia -movedb -m <media_id> -newserver <each media server> -oldserver <master server>)

11. backup test

Is this procedure problem ?

Highlighted

Symantec's recommended


Symantec's recommended upgrade method is described in detail in this doc:

ftp://exftpp.symantec.com/pub/support/products/NetBackup_Enterprise_Server/290141.pdf

I do have a problem with the way that you have configure the devices -tpconfig is NOT the recommended way in a shared environment. 

The problem that you are experiencing can be a result of devices added to EMM as non-shared.
Have a look at the SSO Admin Guide:
  http://seer.entsupport.symantec.com/docs/290238.htm

As I've said before - to delete and re-scan is going to take all of 5 minutes.
It's your choice - accept or reject advice.

In a shared environment, use the WIZARD from the GUI main page:



Highlighted

Thanks to reply

I will retry the upgrade procedure at guide.
Highlighted

You cannot re-do the upgrade

You cannot re-do the upgrade if everything is already on 6.5.x. It seems that you work in a support environment where you have to assist customers. Keep the upgrade TechNote for future reference.

What I'm suggesting at this point in time is that you delete all devices and use the wizard in the GUI to scan all media servers simultaneously and add the devices as shared.

Hi Marianne, I was reading

Hi Marianne,

I was reading your post. If drives are all delete and the wizard, will it automatically configure the drives sa shared in a sso enviroment?

Highlighted
Accepted Solution!

Correct. If all the media

Correct. If all the media servers have the correct license keys installed (Server, Library based tape drives, Shared Storage Option) the wizard will scan all media servers, detect the same tape drives on the media servers and configure them as shared.

View solution in original post