cancel
Showing results for 
Search instead for 
Did you mean: 

Netbackup Solaris Media Server to 5230 Appliance Migration

Yuvi
Level 5
Certified

Environment : Solrais 10 Master Server with 7.6.0.1 version and 7.5.0.6 Media servers with Solaris 10.

Clarification Needed

As we are going to migrate our Physical master server to Virtual master server with the same name ( Catalog Migration)

And Going to decommission our solaris media servers to Netbackup 5230 appliance .

My Concern here is after catalog migration to new server (virtual master) am going to decommision the Media servers used in old master.

Will it effects me in new infra for restores using old disk pools with new appliance and how it works.

Or while decommission my old disk pools will also be get deleted ..?

2 ACCEPTED SOLUTIONS

Accepted Solutions

RiaanBadenhorst
Level 6
Partner    VIP    Accredited Certified

Before decommisioning the media servers you have to add the master to the datadomain (install boost, configure the storage server and add the credentials). That way the master has access to the DD so it can restore anything in the diskpool. During decommission of the media servers you'll assing ownership of the images to the master. You can also add the appliance to the DD so that they can perform this function.

View solution in original post

Jaime_Vazquez
Level 6
Employee

Will you still make use of the DD storage units or will you make use of the storage that comes with the 5230?

Not sure what are the sizes of storage in play. But if the storage on the appliances is sufficient and you want to make use of it, one possible migration would be:

1. Create a storage unit on the 5230 appliance. It can be MSDP or Advanced Disk.
2. Perform 'bpduplicate' jobs to copy the backups on the DD to the appliance storage unit.
   You can make use of option to make the copy on 5230 the master copy (copy 1) when completed.
   If the storage on 5230 is MSDP, make the first image copied be a full of a typical client, by OS. do this to   cover all of the OS types being backed up.
   This will initialize the fingerprint cache for that OS type for subsequent backups.
3. Backups or duplication effort for other backups will run more efficiently as the fingerprint cache gets more into place.
4. Modify the backup policies to use the new 5230 storage unit.
5. If the DD storage will remain in use, no other action is required. But if you want to decommission them as well, kick off bpduplication jobs for all remaining images to the 5230. Once all are copied to the 5230, the images on the DD should be secondary images (copy 2). You can expire them and remove the DD units.

That's kind of an outline of one possible set of actions to take.

 

 

 

View solution in original post

5 REPLIES 5

Yuvi
Level 5
Certified

All of the media servers are connected to Datadomain storage units.

RiaanBadenhorst
Level 6
Partner    VIP    Accredited Certified

Before decommisioning the media servers you have to add the master to the datadomain (install boost, configure the storage server and add the credentials). That way the master has access to the DD so it can restore anything in the diskpool. During decommission of the media servers you'll assing ownership of the images to the master. You can also add the appliance to the DD so that they can perform this function.

Yuvi
Level 5
Certified

Thanks for your valid input , so when decommisioning disk pools will not be deleted.

 

Can i use nbdecommisson -oldserver <old Mediaserver> -newserver <new appliance configured>

Above syntax is correct ..?

so that previous images and diskpools assigned/written to old media server can access new appliance accordingly.

RiaanBadenhorst
Level 6
Partner    VIP    Accredited Certified

No the pool does not get deleted, only if that pool would have been contained on the media server itself (like an appliance or MSDP media server).

 

Yes that syntax is fine.

 

Setup the appliance to access DD first.

Jaime_Vazquez
Level 6
Employee

Will you still make use of the DD storage units or will you make use of the storage that comes with the 5230?

Not sure what are the sizes of storage in play. But if the storage on the appliances is sufficient and you want to make use of it, one possible migration would be:

1. Create a storage unit on the 5230 appliance. It can be MSDP or Advanced Disk.
2. Perform 'bpduplicate' jobs to copy the backups on the DD to the appliance storage unit.
   You can make use of option to make the copy on 5230 the master copy (copy 1) when completed.
   If the storage on 5230 is MSDP, make the first image copied be a full of a typical client, by OS. do this to   cover all of the OS types being backed up.
   This will initialize the fingerprint cache for that OS type for subsequent backups.
3. Backups or duplication effort for other backups will run more efficiently as the fingerprint cache gets more into place.
4. Modify the backup policies to use the new 5230 storage unit.
5. If the DD storage will remain in use, no other action is required. But if you want to decommission them as well, kick off bpduplication jobs for all remaining images to the 5230. Once all are copied to the 5230, the images on the DD should be secondary images (copy 2). You can expire them and remove the DD units.

That's kind of an outline of one possible set of actions to take.