Video Screencast Help
Scheduled Maintenance: Symantec Connect is scheduled to be down Saturday, April 19 from 10am to 2pm Pacific Standard Time (GMT: 5pm to 9pm) for server migration and upgrades.
Please accept our apologies in advance for any inconvenience this might cause.

Master P2V and FC Robotic's

Created: 25 Feb 2013 • Updated: 04 Mar 2013 | 11 comments
This issue has been solved. See solution.

Hi All,

Im looking at upgrading our physical 7.1.0.4 Master Servers to 7.5.0.5 then P2V.

Our VM guys have advised against a P2V and more so to a fresh build VM, im not sure how this would be feasible as our NBU binaries are on local disk but the DB is on SAN attached disk so we could RDM to the VM. Has anyone taken this approach or stuck to P2V?

I am also using NetBackup as Application Clusters on Standalone Media Servers, which require the Master Server to be the Robot control host, so this become a problem as I cant FC the robot to the VM.........anyone had this issue?

Thanks in advance.

Jay 

Operating Systems:

Comments 11 CommentsJump to latest comment

Mark_Solutions's picture

Lots of issues there!

My first advice if you cannot P2V the Master is to have a new build and do a catalog restore (do the backup to a Media Server first to make life easier and add that Media Server back in before doing the catalog restore.

For roboitcs over VMWare I wouldn't go there! You can do tape drives (though not very well) but robotics just dont map to VMWare.

I would allocate a non clustered Media Server as the robotic host if possible (and do this prior to the catalog restore as you will be using that Media Server to do the catalog backup / restore

Hope this helps

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.

Jaykullar's picture

Thanks Mark. When you say "do the backup to the media server" you mean use the media server has the backup host to backup the catalog to a disk storage unit on the media server?

Im thinking it will go alittle like this:

  • Catalog backup to media server
  • Install NBU to new master VM
  • Manually add media server into config
  • Do catalog restore to recover the entire database

Regards robotics, we have standalone media servers in a cluster with virtual storage units, the pre-req for this is to have the master as a robot control host. I've not had problems with this config using a media server as a robot control host, but support advise the master should be the control host. Obviously if I virtualise the master it cant be the robot control host.

Thanks,

Mark_Solutions's picture

I would do the backup of the catalog to tape to make things easier

So:

1. catalog backup to tape done by the media server

2. shutdown old master

3. rename new VM to same name as old master and install NBU to same location (drive letter) and patch level

4. Add in media server, configure tape library, inventory and do full catalog restore

Probably best to have already removed and tape devices etc from the Master before doing this - also make a note of the last job id (or copy the files from netbackup\db\jobs\ to copy to the new Master.

For the virtual storage units .. that is something i have not dealt with personally but if that is the only supported config then you may have to stick with a "real" master as robotics and VMWare just dont go well together - perhaps check again with support about that as clustered Media Servers are about to be dropped i believe and already only supported if upgraded from a 6.x version.

Hope this helps

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.

SOLUTION
Jaykullar's picture

Thanks for the help Mark.

The media server's are standalone, NetBackup itself isnt clustered, but installed on server's which are in a cluster, and netbackup is configured into application cluster, with a virtual storage unit, incase node 1 fails over to node 2, netbackup continues to follow the the active node.

I will try and something from support regards this, as mentioned I might have to stay with a real master. The option of VMware and AppHA seemed a better setup for DR.

Thanks.

Mark_Solutions's picture

OK - let us know how you get on and if you feel your questions have been answered dont forget to close the thread using the "Mark as solution" option

P.S keeping the NetBackup database etc on a replicated SAN drive and having a standby Master node on the DR site works nicely too ... and then there is AIR which makes life really easy!

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.

Jaykullar's picture

Will do Mark.

I was thinking of Virtualising both our Production Masters and DR Masters and adding AIR. Seems you read my mind. Its just deciding which images to AIR. Most of our estate is thousands of VM's, I will be testing AIR soon :)

Thanks,

Marianne's picture

If I may ask - why do you want to migrate the master to virtual?

Sounds like you're creating a whole lot of unnecessary headaches.

Please bear in mind that only backups to dedupe disk can be replicated with AIR.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

Jaykullar's picture

Virtual master would have given me a quicker recovery time in event of DR. However Symantec have confirmed with virtual storage units I use, best practice is to have master as the robotic control host, however its not a must, but recommended.

We have alot of clusters with large data so using application cluster storage units works well and gives us SAN backups. But in some domains we have multiple control hosts/library, so cannot have the master as the control host for multiple robots.

 

Jaykullar's picture

Just to confirm with AIR, if i AIR images from Production to DR, are the images still available in production for restore?

I need to test it to how and if it is needed in our environment, running mostly VM's, and Clusters, and SQL from staging area's there are already backups of backup of backups and alot of business continuity.

Marianne's picture

As per my previous post - ONLY backups to dedupe Storage Units can be duplicated via AIR.

No tape or basic/advanced disk.

AIR is duplication. This means original data is still available at Production.

See AIR FAQ: http://www.symantec.com/docs/TECH154323

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

Ryan-4SL's picture

The retention of images will depend on the configuration of your SLPs. The backup images will be retained on your source MSDP storage pool for as long as the SLP says they must.

AIR does not purge the source backup image from the source MSDP storage pool, it simply makes a deduplicated and optimised copy to the target MSDP storage pool and imports the image catalog information into the target NetBackup domain.