cancel
Showing results for 
Search instead for 
Did you mean: 

migration

bill0621
Level 4

http://www.symantec.com/connect/forums/netbackup-migration-0

http://www.symantec.com/connect/forums/netbackup-migrate-new-server
 

http://www.symantec.com/business/support/index?page=content&id=TECH31385

http://www.symantec.com/business/support/index?page=content&id=TECH77448

 

Hi ALL,

I am about to perform a migration from 6.5  linux to 7.1 solaris.

I have read the above links regarding the migration.I have below queries:

  1. what is the difference in recovery with import and recovery without import?( i have read the pdf but not clear)
  2. In 7.1,we have different policy hardware type.will there be a problem if i copy db/class folder from 6.5 to 7.1?
  3. why on old master  i have to add new master as a Server to all clients : Open Host Properties, select all clients (if there are many, select about 10 at a time), add new master as a SERVER to all clients.   link : http://www.symantec.com/connect/forums/netbackup-migrate-new-server
  4. first i have to install 6.5 on my new server or i have to upgrade old server to 7.1?
1 ACCEPTED SOLUTION

Accepted Solutions

RiaanBadenhorst
Level 6
Partner    VIP    Accredited Certified

1. Import refers to reading each tapes content to build the catalog. Recovery without import refers to copy the catalog across from the source and there by not having to perform the read on each tape. If this is a migration to new hardware then neither should not concern you.

 

2. & 4. Should migrate on the same version. So that means either upgrade your linux to 7.1 and then migrate to solaris, or install solaris with 6.5, and then upgrade. I would suggest the one in bold.

 

3. This is not required if you keep the same master server name which is totally possible in a unix environment.

View solution in original post

9 REPLIES 9

RiaanBadenhorst
Level 6
Partner    VIP    Accredited Certified

1. Import refers to reading each tapes content to build the catalog. Recovery without import refers to copy the catalog across from the source and there by not having to perform the read on each tape. If this is a migration to new hardware then neither should not concern you.

 

2. & 4. Should migrate on the same version. So that means either upgrade your linux to 7.1 and then migrate to solaris, or install solaris with 6.5, and then upgrade. I would suggest the one in bold.

 

3. This is not required if you keep the same master server name which is totally possible in a unix environment.

bill0621
Level 4

Thanks Rian.

For point 1.how recovery without import works.I have to run bprecover command in both cases.(with import and without import).

Marianne
Level 6
Partner    VIP    Accredited Certified

It seems that you are confusing upgrade and migrate.

6.5 to 7.1 is upgrade.

Linux to Solaris is migrate.

So, your planning for upgrade and migration will be 2 different steps.

If your current Linux hardware and OS supports 7.1, do the upgrade first and the migrate to Solaris.

If not, migrate to Solaris using same NBU version, then upgrade.

Migration between Unix/Linux operating systems is easy, as long as you keep the hostname the same, install on new hardware to same path with same NBU version and patch level.

Use this technote:

Using catalog backup and recovery to transfer NetBackup catalogs between UNIX or Linux master servers as part of a hardware refresh
http://www.symantec.com/docs/TECH77448

I don't see any need for 'Recovery without Import' in your environment.
(In the 1st post that you found, I have posted a link to Recovery without Import whitepaper. This doc explains what it is all about. Please read it - only 3 pages... If you read the entire discussion carefully, you will understand why I recommended Recovery without Import.) 

One more question - why 7.1?
Why not 7.5 or 7.6?

See NetBackup 7.x Upgrade Portal http://www.symantec.com/docs/TECH74584

bill0621
Level 4

Thanks Marianne.we have asked the client for 7.5 but they want first to go for 7.1.

In below link:

http://www.symantec.com/docs/TECH77448

Restore the catalog backup created from the old master server to the new master server.

?????How to resetore on solaris server (B) ??????

Steps which i will follow:

  1. I have to run a catalog backup on server A.(linux).Shut down server A.
  2. Install NBU 6.5 on server B(solaris).
  3. then what?

 

 

 

Marianne
Level 6
Partner    VIP    Accredited Certified

Have you actually gone through TECH77448?

Have you seen step 5 of the TN under this topic??

The following procedure should be used when replacing hardware:

There are 9 steps. Please read through entire TN and read thtough the other documentation mentioned in step 5....

bill0621
Level 4

I have read this documents 3 4 times.

Restore the catalog backup created from the old master server to the new master server.

?????How to resetore on solaris server (B) ??????  -----tHIS means catalog recovery through bprecover command?

 

Steps which i will follow:

  1. I have to run a catalog backup on server A.(linux).Shut down server A.
  2. Install NBU 6.5 on server B(solaris).
  3. ship tapes from A to B.
  4. Then run catalog recovery(wizard or bprecover command.

Am i correct with these steps?

Marianne
Level 6
Partner    VIP    Accredited Certified

Seems you need to read again...........

5. Restore the catalog backup created from the old master server to the new master server.  Details of the catalog restore process can be found in the Disaster Recovery section of the NetBackup Troubleshooting Guide.  

 

 The Troubleshooting Guide covers important steps such as installation of NBU to same path on new server, to copy the DR-file to the new server, and other important steps... 

bill0621
Level 4

catalog restore process and catalog recovery(bprecover wizard) is same ?

Marianne
Level 6
Partner    VIP    Accredited Certified

SIGH.....  Yes. It's the same.

I believe the question(s) in your opening post got answered, right?

There is enough documentation in the manuals, on Symantec web site, in this forum, etc.. that deals with catalog recovery/restore.

Keep on reading......................................