Migrating from 1 server to a new server.

Ha, The tool cannot be used on source primary servers 10.2 and up. Add that to your comments for support.

I'm not asking about disc space on the master. I'm asking if you have an MSDP configuration on your master. I will assume that you do not have

admin_bkp007 is right. This is the supported procedure to migrate the primary server. If you try this path do not use any deduplication device for the catalog backup. use a basic disk. It will do thinks easer.

I do not use backup and restore for migrations. For big environments it is time consuming. In stead I use rsync.

The problem is that I have never tried to migrate a server bigger than 10.1.1 (the primaries with the new progress database).
I will write what my steps are to migrate a 10.1.1 server and you can try it. I do not think that you will have any problems.
After all, if the old server is there, the new one will not start.

• install OS (redhat 9) on the new server.
• use the same hostname as the old primary name (with FQDN if the old one is configured with FQDN).
  Check the first entry in the nbu configuration file for the name (cat /usr/openv/netbackup/bp.conf).
• use a temporary IP  and add an entry to the /etc/hosts file
• create the same users with the same groups and home directories for web services and Postgres.
• Install the same version of NetBackup.
• check that it is working ok (java or webui) and stop netbackup services.
• take a backup of the /usr/openv of the new server (mv or tar) and delete /usr/openv.
• use rsync to copy /usr/openv for old primary to the new one. Do not check the sync errors.
• if the environment is big and have many changes or the sync is slow, run it many times in order to minimize the copy time.
• When the sync finish, stop all netbackup services of the old primary server.
• run a last rsync. At that stage no sync errors must occur.
• swap the IPs of the servers (just to have the original server up in case you need something) and fix /etc/hosts
• start netbackup on the new server and do tests.
• If everything is okay, use the new server.

I had done this procedure several times, but as I told you, with netbackup up to 10.1.1. I do not expect to have problems with 10.3, but as always, do it at your own risk.

For the media server, just install a second media server (with new name) and retire the old one