Video Screencast Help
Search Video Help Close Back
to help
New in the Rewards Catalog: Vouchers for "Symantec Technical Specialist" and "Symantec Certified Specialist" exams.

Migrating to New Master Server

Updated: 22 May 2010 | 9 comments
subhojit.pal's picture
0 0 Votes
Login to vote

Hi Folks,

 

OS: HP-UX 11:11

Netbackup Version: 6.5.1

 

We will be migrating the master server which is also a new master server which will also be HP-UX. However, the server name will change. What will be the best process to migrate the catalog to the new server. We are taking hot catalog backup of the server on daily basis. Will that be of any good.

Another important point is I have only 1 tape library. So, what should be the best way to work on this without causing significant outage.

 

Thanks,

 

Subhojit.

discussion Filed Under:

Comments

Stumpr's picture
20
Jan
2009
0 Votes 0
Login to vote

Hi,

What are the benefits for changing the master server's hostname?

 

Bob Stump VERITAS - "Ain't it the truth?" Incorrigible punster -- Do not incorrige

Marek Kedzierski's picture
21
Jan
2009
0 Votes 0
Login to vote

I could be very difficult, when ou go to support you will probably receive info that it's onyl supported Symantec Consulting

 

marekk

subhojit.pal's picture
21
Jan
2009
0 Votes 0
Login to vote

Thanks Marek & Bob.

 

The issue that we have is the server is primarily an Oracle database server which will function also as a netbackup server. It is a business requirement that the new server will have different name.

 

This is a pretty small environment with only 6 clients and 1 TB of data being backed up nightly.

 

Thanks,

 

Subhojit.

Stumpr's picture
21
Jan
2009
0 Votes 0
Login to vote

so change the name of the oracle server....

Bob Stump VERITAS - "Ain't it the truth?" Incorrigible punster -- Do not incorrige

Raphael Carvalho's picture
21
Jan
2009
0 Votes 0
Login to vote

http://www.adsm.org/lists/html/Veritas-bu/2000-03/msg00115.html

 

Works BUT:

1. There is no guarantee. Environment's variables are always a trouble. This process might have something you would adapt for your case so, you should not do that unless with you are REALLY confident about your knowledges on NBU's structure, your NBU environment and/or you are assisted by a Specialized NBU Consultant Professional;

3. Take streamy care on the steps, specially changing images database information and media's database information as well. Double check all commands outputs;

4. No matters how or what you do, Symantec will not support this process or any issue as a result.

Stumpr's picture
21
Jan
2009
0 Votes 0
Login to vote

Official Symantec standing on changing the master server hostname

 

Reference:

 

DOCUMENTATION: Notes on changing or modifying the Master Server's host name, in regards to the following warning: Do not change the host name of a NetBackup server. This practice is not recommended because it can be necessary to import all previously used media to the server before you can use it under the new host name.

http://support.veritas.com/docs/268696

 

Details:

Manual:    
Veritas NetBackup DataCenter (tm) 4.5 System Administrator's Guide
Veritas NetBackup Enterprise Server (tm) 5.0 System Administrator's Guide Volume II
Veritas NetBackup Enterprise Server (tm) 5.1 System Administrator's Guide Volume II
Veritas NetBackup Enterprise Server (tm) 6.0 System Administrator's Guide Volume II

Page:  N/A

Modification Type: Supplement

Modification:
The above manuals contain the following warning:

Note:  Do not change the host name of a NetBackup server.  This practice is not recommended because it can be necessary to import all previously used media to the server before you can use it under the new host name.

Changing or modifying any NetBackup server host names must be done with extreme care, whether they be Master Servers or Media Servers.

It is highly recommended that any NetBackup Server host name changes be done through Symantec's consulting services. This is due to issues such as the server host name being appended to the images in the catalog.  Simply changing the Master Server host name can cause restores to fail, connection problems with clients and having to import all media back into the catalog.

Changing or modifying the master host name is not supported by Technical Support without the assistance of a qualified Symantec Consultant on site.

Bob Stump VERITAS - "Ain't it the truth?" Incorrigible punster -- Do not incorrige

Raphael Carvalho's picture
21
Jan
2009
0 Votes 0
Login to vote

Totally agree with Bob. You should not do that by yourself.

Message Edited by Raphael Carvalho on 01-21-2009 12:19 PM

Status_Code_0's picture
21
Jan
2009
0 Votes 0
Login to vote

If you are taking cold, offline catalog backups, you could get away with doing a bprecover with the -dhost switch.

 

I've had success with it in the field, however I still had the old master sitting there powered off in case something went wrong.

 

The -dhost switch allows the catalog files to be remapped to the new master server.  Check out the 6.5 commands guide for more info bprecover.

 

I agree with Bob and Ralph though, if you have never done this it is not an easy procedure...

zippy's picture
21
Jan
2009
0 Votes 0
Login to vote

on the new server with ne name put this in youre bp.conf file

 

FORCE_RESTORE= <old master server name new master server name> 

 

I have done it many times.