cancel
Showing results for 
Search instead for 
Did you mean: 

It's possible to move physical master server to vm (P2V) through vm tool

Desh
Level 3

We are planing to move Physical Master server to VM.

As per vmware team suggest to using convert to vmtools this physical master server to VM Master. For this server having Tape drives and Datadomain.

Any issues from Netbackup application end.

 

3 REPLIES 3

Nicolai
Moderator
Moderator
Partner    VIP   

Data Domain should be no problem. However tape drives connections is not supported under VMware or Hyper-V.

When a Netbackup master/media server is connected to  tape drives via the hypervisor, any motion from one ESX host to another will cause the SCSI connection to be cut off, meaning you loose the tape drives connections. 

See Support for NetBackup 7.7.x and 8.x in virtual environments

https://www.veritas.com/content/support/en_US/doc/NB_70_80_VE

Thanks for inputs.

I have few more quires on this.

1. Is it  support Netbackup version 7.1.0.4 in windows master server (P2V - through vmtool) ?

2. Required any pre check before P2V ? Like hardware compartbulity and etc...

3) Kindly share if any document is there for P2V.

4) Is there any specific settings needs to be changed on the system resources after it is migrating to VM.

 5) Please share documents if you have any related to VM configuration of Netbackup Master/Media server.

 6) Also we are planning to use target our bacups to cloud gateway. Do we have any comaritbility issues with cloud gateway, Netbakcup VM.

7.) How can fix catalog inconsistance issues in netbackup.

Systems_Team
Moderator
Moderator
   VIP   

*** EDIT ***

Just realised I had forgotten to include the link to the 7.6 SCL, so have now added it Smiley Tongue

*** EDIT ***

Hi Desh,

Here are my comments / suggestions:

1. Is it support Netbackup version 7.1.0.4 in windows master server (P2V - through vmtool) ?

NetBackup is supported as a virtual master server, except for as noted by Nicolai that tape drives are not supported.  Your biggest issue is that your version of NetBackup is not supported and reached end of support life in February 2017.

2. Required any pre check before P2V ? Like hardware compartbulity and etc...

First would be that you make sure NetBackup services are COMPLETELY shut down before attempting P2V.  The server name MUST remain the same.

3) Kindly share if any document is there for P2V.

P2V is a VMware function, so I don't think you will find anything from Veritas regarding this part - only what they support.

4) Is there any specific settings needs to be changed on the system resources after it is migrating to VM.

There should be nothing specific here.  If your physical machine is currently under-resourced (eg: RAM) then you may wish to adjust that on the virtual version.

5) Please share documents if you have any related to VM configuration of Netbackup Master/Media server.

There are no specific documents related to this.  Treat it as if it was physical, but now running in a virtual environment.  Because your version is so old, and unsupported finding documentation is now very difficult.  Nicolai has already given you the statement for support in a virtual environment.  I have managed to find a copy of the Software Compatibility List for your old version (https://www.veritas.com/content/support/en_US/doc/NB_76_OSSCL).  Page 94 shows the supported versions of VSphere.

6) Also we are planning to use target our bacups to cloud gateway. Do we have any comaritbility issues with cloud gateway, Netbakcup VM.

The only issue here would be how are you getting your data to the cloud?  The version of NetBackup you have would not support cloud, whereas the later versions do.  There may be some licensing required, but as noted would not apply to your version as it is EOSL and doen't support cloud.

7.) How can fix catalog inconsistance issues in netbackup.

Normally you would run the NBCC utility (Netbackup Catalog Consistency Check) and then send the output file to Veritas support for review and next steps.  That requires being able to open a support case, which you can't do as your version is no longer supported.

Hopefully others can chime in with some more suggestions.

Hope this helps,

Steve