NetBackup Appliance 5220 Migration
In this article we will see how the Netbackup appliance is
moved from one master sever to the other.
In this scenario the Source and the destination master
servers are both in the same domain.
The source is a windows 2008 enterprise server running
NetBackup 7.5 and the destination is a NetBackup 5220 appliance running
NetBackup 7.5.
Before starting with the migration make sure that no jobs
are running on the media server which is getting migrated.
If any please cancel all the jobs.
Verify whether the jobs are running by issuing the following
command on the Appliance
Once all the jobs are cancelled make sure that you
deactivate the policy so that no jobs run during the migration activity.
On the Media server which needs to be moved to the new
master server stop the NetBackup services.
Gz#$%%^^d1:/usr/openv/netbackup # service netbackup stop
stopping the NetBackup Service Monitor
stopping the NetBackup CloudStore Service Container
stopping the NetBackup Service Layer
stopping the NetBackup Remote Monitoring Management System
stopping the NetBackup compatibility daemon
stopping the Media Manager volume daemon
stopping the NetBackup Deduplication Engine
stopping the NetBackup Deduplication Manager
stopping the NetBackup client daemon
stopping the NetBackup network daemon
Edit the bp.conf file on the media server to reflect the new
master server.
Make sure that in the bp.conf file the first SERVER entry
should have the hostname of the Master server and in the second SERVER field
please have the name of the media server appliance which needs to be migrated.
Gz#$%%^^d1:/usr/openv/netbackup # more bp.conf
SERVER = <NEW_MASTER_SERVER_HOSTNAME>
SERVER = Gz#$%%^d1
CLIENT_NAME = Gz#$%%^^d1
USE_VXSS = PROHIBITED
VXSS_SERVICE_TYPE = INTEGRITYANDCONFIDENTIALITY
EMMSERVER = <NEW_MASTER_SERVER_HOSTNAME>
Once the bp.conf file is edited.
Please start the netbackup services on the appliance.
Gz#$%%^^d1:/usr/openv/netbackup # service netbackup start
NetBackup Authentication daemon started.
NetBackup network daemon started.
NetBackup client daemon started.
Please run the following command on the Media server
appliance to check if it is pointing to the new master server or not.
Gz#$%%^^d1:/usr/openv/netbackup/bin # ./bpclntcmd -pn
expecting response from server Newmaster.jdnet.deere.com
[1]+ Stopped ./bpclntcmd -pn
Gz#$%%^^d1:/usr/openv/netbackup/bin #
Gz#$%%^d1:/usr/openv/netbackup/bin # telnet Newmaster 13782
Trying 172.24.0.180...
Connected to Newmaster.
Now on the Newmaster (Destination Master Server) server stop
the netbackup services and add the new media server to the bp.conf file.
gzpunnbumstr1:~ # service netbackup stop
stopping the NetBackup Service Monitor
stopping the NetBackup CloudStore Service Container
stopping the NetBackup Vault daemon
stopping the NetBackup Agent Request Server
stopping the NetBackup Service Layer
On the bp.conf file add two parameters –
SERVER = Gz#$%%^^d1
MEDIA_SERVER = Gz#$%%^^d1
Once the changes are made please start the netbackup
application on the master server appliance by applying the following command –
“Service netbackup start”
The next step would be to add the Storage server.
Launch the NetBackup Administration console.
Expand Credentials and Right click on Storage Server and
select “New Storage Server”.
Once the Storage Server is created proceed with the creation
of the Disk Pool and Storage Unit.
