Sri

Keep the old Netbackup master server up for a month or two, then have it 
virtualized. Then take a full VMDK backup of the server and recover it when 
future restores are made. Then you just pull the required tapes and import them 
into your current master server and restore it from there. Just a thought.  

Daniel Jimenez
Backup and Recovery

-----Original Message-----
From: [email protected] 
[mailto:[email protected]] On Behalf Of 
[email protected]
Sent: Tuesday, July 10, 2012 10:00 AM
To: [email protected]
Subject: Veritas-bu Digest, Vol 75, Issue 9

Send Veritas-bu mailing list submissions to
        [email protected]

To subscribe or unsubscribe via the World Wide Web, visit
        http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
or, via email, send a message with subject or body 'help' to
        [email protected]

You can reach the person managing the list at
        [email protected]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Veritas-bu digest..."


Today's Topics:

   1.  Netbackup 7.1 Migration (srikanth09)
   2. Re: Netbackup 7.1 Migration (Kalusche, Dan)
   3. Re: Netbackup 7.1 Migration (Martin, Jonathan)
   4. Re: Netbackup 7.1 Migration (Lightner, Jeff)


----------------------------------------------------------------------

Message: 1
Date: Mon, 09 Jul 2012 20:04:57 -0700
From: srikanth09 <[email protected]>
Subject: [Veritas-bu]  Netbackup 7.1 Migration
To: [email protected]
Message-ID: <[email protected]>

Thank You all for your replies. I have to change the hostname and IP address, 
there is no other option. We currently have installed the master server on a 
production server. Its not a dedicated backup server. The new server we are 
planning is a dedicated NBU master server. So the hostname will change from the 
current server :-(

I think i would go with Jeff' idea of building new server from scratch and 
importing media from old server to new server in case of restore requests. 

Can we use the option of keeping current server and as well as new server till 
the data on the current tapes expire?
Remove all the tapes from current server and keep it write protected. Stop the 
NBU services on current server. Whenever a restore request comes, stop the 
services on new server and restore data from old server. 

Thanks
Sri

+----------------------------------------------------------------------
|This was sent by [email protected] via Backup Central.
|Forward SPAM to [email protected].
+----------------------------------------------------------------------




------------------------------

Message: 2
Date: Tue, 10 Jul 2012 12:17:42 +0000
From: "Kalusche, Dan" <[email protected]>
Subject: Re: [Veritas-bu] Netbackup 7.1 Migration
To: "[email protected]"
        <[email protected]>
Message-ID:
        <[email protected]>
Content-Type: text/plain; charset="us-ascii"

I would think that keeping the current server would be an option for you.
I would have done the same if we didn't have a multitude of images saved to 
infinity...
Our old master would have been around forever, so I just did the migration...
Good Luck! 

-----Original Message-----
From: [email protected] 
[mailto:[email protected]] On Behalf Of srikanth09
Sent: Monday, July 09, 2012 10:05 PM
To: [email protected]
Subject: [Veritas-bu] Netbackup 7.1 Migration

Thank You all for your replies. I have to change the hostname and IP address, 
there is no other option. We currently have installed the master server on a 
production server. Its not a dedicated backup server. The new server we are 
planning is a dedicated NBU master server. So the hostname will change from the 
current server :-(

I think i would go with Jeff' idea of building new server from scratch and 
importing media from old server to new server in case of restore requests. 

Can we use the option of keeping current server and as well as new server till 
the data on the current tapes expire?
Remove all the tapes from current server and keep it write protected. Stop the 
NBU services on current server. Whenever a restore request comes, stop the 
services on new server and restore data from old server. 

Thanks
Sri

+----------------------------------------------------------------------
|This was sent by [email protected] via Backup Central.
|Forward SPAM to [email protected].
+----------------------------------------------------------------------


_______________________________________________
Veritas-bu maillist  -  [email protected] 
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


------------------------------

Message: 3
Date: Tue, 10 Jul 2012 08:47:19 -0400
From: "Martin, Jonathan" <[email protected]>
Subject: Re: [Veritas-bu] Netbackup 7.1 Migration
To: "Kalusche, Dan" <[email protected]>,
        <[email protected]>
Message-ID:
        <[email protected]>
Content-Type: text/plain;       charset="US-ASCII"

We used a variation on this here. We stood up a new master, then waited
1 year for 99% of our images to expire. Then we imported the old media
(SLT) on the new master and duplicated them to new media (LTO). Just
keep in mind that when you do this, you need to make sure the retentions
match on the old and new masters. If retention 10 on your old master is
infinity and retention 10 on the new master is 1 year, the images will
only be kept for 1 year on import.

Good luck!

-Jonathan

-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of
Kalusche, Dan
Sent: Tuesday, July 10, 2012 8:18 AM
To: [email protected]
Subject: Re: [Veritas-bu] Netbackup 7.1 Migration

I would think that keeping the current server would be an option for
you.
I would have done the same if we didn't have a multitude of images saved
to infinity...
Our old master would have been around forever, so I just did the
migration...
Good Luck! 

-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of
srikanth09
Sent: Monday, July 09, 2012 10:05 PM
To: [email protected]
Subject: [Veritas-bu] Netbackup 7.1 Migration

Thank You all for your replies. I have to change the hostname and IP
address, there is no other option. We currently have installed the
master server on a production server. Its not a dedicated backup server.
The new server we are planning is a dedicated NBU master server. So the
hostname will change from the current server :-(

I think i would go with Jeff' idea of building new server from scratch
and importing media from old server to new server in case of restore
requests. 

Can we use the option of keeping current server and as well as new
server till the data on the current tapes expire?
Remove all the tapes from current server and keep it write protected.
Stop the NBU services on current server. Whenever a restore request
comes, stop the services on new server and restore data from old server.


Thanks
Sri

+----------------------------------------------------------------------
|This was sent by [email protected] via Backup Central.
|Forward SPAM to [email protected].
+----------------------------------------------------------------------


_______________________________________________
Veritas-bu maillist  -  [email protected]
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
_______________________________________________
Veritas-bu maillist  -  [email protected]
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


------------------------------

Message: 4
Date: Tue, 10 Jul 2012 13:31:54 +0000
From: "Lightner, Jeff" <[email protected]>
Subject: Re: [Veritas-bu] Netbackup 7.1 Migration
To: "[email protected]"
        <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset="us-ascii"

Just to be clear - we kept the old master running so it could continue to do 
vaulting reports to recall media from offsite as they expired.   If you're not 
doing vaulting this may not be a consideration for you.

We didn't do the 1 year Jonathan suggests - our intent was to do 3 months since 
most of our monthlies expire in that time frame.  In actuality it ended up 
being more than 6 months but that was just because we were slammed.   In our 
case we wanted to make the old master a media server for the new environment 
due to disk replications/backups we did there.  (It was HP-UX and we couldn't 
do the replications to Linux owing to filesystem/volume manager used on HP-UX 
and not on Linux.)

My question would be if the existing server is a "Production" server how are 
you backing up that "Production" stuff after you switch to the new master?   
That is to say, in our case we didn't have to keep any other app running on the 
old master and were able temporarily to move the disk replication to another 
HP-UX server.  In your case however you need to be concerned with this other 
"Production" stuff.   You can't run the old master as a master for the old 
environment AND as a  client/media server for the new environment as well.





-----Original Message-----
From: [email protected] 
[mailto:[email protected]] On Behalf Of Martin, Jonathan
Sent: Tuesday, July 10, 2012 8:47 AM
To: Kalusche, Dan; [email protected]
Subject: Re: [Veritas-bu] Netbackup 7.1 Migration

We used a variation on this here. We stood up a new master, then waited
1 year for 99% of our images to expire. Then we imported the old media
(SLT) on the new master and duplicated them to new media (LTO). Just keep in 
mind that when you do this, you need to make sure the retentions match on the 
old and new masters. If retention 10 on your old master is infinity and 
retention 10 on the new master is 1 year, the images will only be kept for 1 
year on import.

Good luck!

-Jonathan

-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Kalusche, Dan
Sent: Tuesday, July 10, 2012 8:18 AM
To: [email protected]
Subject: Re: [Veritas-bu] Netbackup 7.1 Migration

I would think that keeping the current server would be an option for you.
I would have done the same if we didn't have a multitude of images saved to 
infinity...
Our old master would have been around forever, so I just did the migration...
Good Luck!

-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of
srikanth09
Sent: Monday, July 09, 2012 10:05 PM
To: [email protected]
Subject: [Veritas-bu] Netbackup 7.1 Migration

Thank You all for your replies. I have to change the hostname and IP address, 
there is no other option. We currently have installed the master server on a 
production server. Its not a dedicated backup server.
The new server we are planning is a dedicated NBU master server. So the 
hostname will change from the current server :-(

I think i would go with Jeff' idea of building new server from scratch and 
importing media from old server to new server in case of restore requests.

Can we use the option of keeping current server and as well as new server till 
the data on the current tapes expire?
Remove all the tapes from current server and keep it write protected.
Stop the NBU services on current server. Whenever a restore request comes, stop 
the services on new server and restore data from old server.


Thanks
Sri

+----------------------------------------------------------------------
|This was sent by [email protected] via Backup Central.
|Forward SPAM to [email protected].
+----------------------------------------------------------------------


_______________________________________________
Veritas-bu maillist  -  [email protected] 
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
_______________________________________________
Veritas-bu maillist  -  [email protected] 
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
_______________________________________________
Veritas-bu maillist  -  [email protected] 
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu




Athena(r), Created for the Cause(tm)
Making a Difference in the Fight Against Breast Cancer

---------------------------------
CONFIDENTIALITY NOTICE: This e-mail may contain privileged or confidential 
information and is for the sole use of the intended recipient(s). If you are 
not the intended recipient, any disclosure, copying, distribution, or use of 
the contents of this information is prohibited and may be unlawful. If you have 
received this electronic transmission in error, please reply immediately to the 
sender that you have received the message in error, and delete it. Thank you.
----------------------------------



------------------------------

_______________________________________________
Veritas-bu maillist  -  [email protected]
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


End of Veritas-bu Digest, Vol 75, Issue 9
*****************************************


_______________________________________________
Veritas-bu maillist  -  [email protected]
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Reply via email to