03-09-2018 07:40 AM
Hi, good Mornig, I'm working for a client that needs to change the server that we are using as Master server to renew it. The thing is that the Windows team is asking us if they can change the name of the Master server to so the new server can have the name acording to the new standars. Serching about the topic of master server name change I found this:
https://www.veritas.com/support/en_US/article.100011576.html
in that articule said that adding the new master server name and deleting the old one, will be enought for Netbackup to run on the new server. But I'm not sure if that will have impact on the polices that we are megrating through the catalog backup, because the catalog backup in being megrated from the old master server.
Can someone clarify this and recomend the necesary steps to follow in this case?
Thx you all for the help! Best regards.-
03-09-2018 08:12 AM
Hello,
See below the no detailed steps to migrate the appliance to new master server:
1- Empty the appliance disks with your usually strategy;
2- Make the decommission of this appliance media server;
https://www.veritas.com/content/support/en_US/doc/99497890-126559150-0/v81612748-126559150
3- Add the appliance to the new master server;
03-15-2018 07:01 AM
Hi Silas, for what I understand if I do the migration I will lose the backups that I already made on the all disk. In my solution I do the backups on disk and the I move them to tapes. on the migration I want to move the backups that I have on disk to the new server. I also have disks on different servers that I use for the backups. will I losse those backups if I decomission the appliance? Please let me undertand this part because is really important. thanks for the help.
03-16-2018 03:30 AM
So, the customer's requirement is ' to change the server that they are using as Master server'.
Do they just want to migrate to new hardware?
If so, the process is as easy as preparing a new server with same hostname, install same NBU version to same folder structure, and recover NBU catalog.
Important that the hostname stays the same. If not, you need a certified consultant to migrate the catalogs to new server with new hostname.
The TN that you found is not going to help here - it merely explains how a backup admin managed to 'mess up' and how the changes were reversed to get NBU to function again.
Please see these docs:
Using catalog backup and recovery to transfer NetBackup catalogs between Windows master servers as part of a hardware refresh
http://www.veritas.com/docs/000041076
DOCUMENTATION: How to migrate the NetBackup catalog information from one platform to another (UNIX to Windows or vice versa), rename a Master Server, cluster an existing Master Server, or merge multiple NetBackup domains.
http://www.veritas.com/docs/000026956
12-17-2018 10:07 AM - edited 12-17-2018 10:27 AM
Hello Marianne,
Thanks for providing such useful information i also have a simillar situation where we are looking to move all data from 5220 to new 5230 appliance, all backups are disk based no tapes backups present.
So my question is if we go ahead with renaming the hostname on new 5230 appliance same as the old 5220 as part of a hardware refresh suggested in http://www.veritas.com/docs/000041076 , will all our images also be transferred to the new 5230 automatically?
We also have 3 additional media server 2012 (Disk backups) attached with 5220 master server, so thier images will also be transferred to the new 5230 appliance as well if we follow catalog recovery option mentioned?
And what if something goes wrong while migration will be able to revert changes & can still access the old 5220 appliance with all backups intact?
Thanks,
Shubham
12-17-2018 11:50 PM
Catalog recovery will ONLY recover NBU catalogs - not actual images.
I sincerely hope that you are migrating to 5240 Applainces and not 5230.
5230 reached End of Sale 2 years ago on December 31, 2016.
Herewith an article to migrage Appliance Master server:
Veritas NetBackup Appliance™ Hardware Migration Toolkit
The Veritas NetBackup Appliance™ Hardware Migration Toolkit makes it easy to perform a simple transition from older NetBackup Appliances to newer ones during hardware refresh cycles and eliminate the cost of services engagement.
With this toolkit, you can migrate the NetBackup configuration, policies, catalogs, and images from a source appliance configured as a master server or master/media server (all-in-one) to a new appliance with the same role with a few steps.
https://www.veritas.com/content/support/en_US/article.100043950.html
12-18-2018 09:29 AM
Thanks Marianne for valuable reply, but as i mentioned we are using a already unsued 5230 appliance which we brought long time back & it has extended support contract i believe, so can you tell me if this migration toolkit can acutally help us to migrate all data from 5220 to 5230 appliance, or is it only applicable for 5220 to 5240 migration?
Other question is will this toolkit also helps to migrate all attached 3 windows 2012 media servers data/images as well to the newer 5230 appliance?
If above toolkit do not help in migration can we atleast move all 3 media server images from old to new master server by decomissioning/removing media server from 5220 & adding it to the newer 5230 appliance box?
Thanks in advance.
12-18-2018 10:55 PM
I suggest you log a call with Appliance Support team about using the tool to migrate to 5230.
If you merely want to move the Windows MSDP media servers to the 5230, then the migration tool (if you get the go-ahead from Veritas) will move existing catalogs and config (which includes the media servers) to the new appliance master.
You will need to manually update Master and EMM server entries on the media servers.
Maybe a good idea to confirm with Support when you ask about migrating to 5230.
12-18-2018 11:25 PM
Thanks i literally was in touch with support for like 3-4 times, they have nothing here to assist & they are pointing towards the consulting support (Charges based service) team can assist on this.
I have been thinking about all possiblities on moving images atleast what we have on media server & we actually can leave out the images which are residing on 5220 appliance without moving it to new appliace since media servers contains huge amount of data & we need to get it transferred to the new master server.
Unfortunately you can not also replicate the images which are already backed up & not a part of the SLP's that's something i feel which has to be there.
Since i feel mostly the data which are stored in media server will remain over there since its stored in separate storage there has to be possiblity of just disconnecting those media server from old one & connecting to the new master server but unfortunately i am not getting enough information to go ahead on that.
12-19-2018 12:57 AM
Have you explicitly asked Support about the migration tool mentioned in https://www.veritas.com/content/support/en_US/article.100043950.html ?
The tool is relatively new. I suspect that not all Support staff know about the tool.
Important that you get through to 'backline' support and not allow the 'frontline' guy to be in a hurry to get the call closed.
It is ABSOLUTELY possible to replicate the images which are already backed up.
I agree - you cannot use SLPs for this, but you can extract a list of images on 5220 and use nbreplicate to script replication to new appliance.
It seems the biggest issue is to move the Windows media servers along with catalog info to new master.
This subject has come up in this forum, but I feel that the answers lacked some detail :
https://vox.veritas.com/t5/NetBackup/Move-Media-server-and-MSDP-to-new-Master-server/td-p/833508
https://vox.veritas.com/t5/NetBackup/Netbackup-8-MSDP-recovery/td-p/855973
You will probably need to import images for Windows MSDP servers on the new master if TN mentioned above is not supported for 5230. Related post:
https://vox.veritas.com/t5/NetBackup/Import-MSDP-images-from-old-server-to-new/m-p/742945
12-19-2018 10:38 AM
Hi Marianne,
Thanks for providing the details i have opened up a case with veritas again asking about the migration tool kit details,will make sure backline will provide suggestion on this time.
Apart from that i have also gone through your 2 TN suggested, but i would like to tell you that first TN is basically containing a windows server scriprt, i tried to implement it on 5220 appliance but was not succeded.
The other TN do not have complete info like how can one simply remove media server from old master server & attach it to the new one, but as you mentioned there is a way by tweaking/updating the EMM database entries to make media server visible to new master server.
If you could help me with how to perfectly use nbreplicate command with right parameters that would be great, i will also try to check the same with veritas as well.
Thanks,
Shubham
12-19-2018 10:49 AM
This is what i got from veritas upon investigating nbreplicate :-
I have taken this case for you and have taken a similar previous case for you. Please note that nbreplicate is not supported as a migration utility and cannot be used in this fashion.
https://www.veritas.com/support/en_US/doc/15263389-127350397-0/v43614636-127350397
"This command is not intended to circumvent normal NBSTSERV processing for Storage Lifecycle Policy controlled images. This command exists to redo previously successful replications. It is distinctly different from bpduplicate."
12-19-2018 11:21 PM
Please have a look at these posts:
@SYM-AJ managed to migrate images using nbreplicate and is extremely helpful in sharing his scripts.
12-23-2018 02:28 AM - edited 12-23-2018 02:29 AM
Thanks Marianne,
I have asked SYM-AJ to share the script/steps to migrate the imgaes from 5220 to 5230, awaiting for his reply.