Veritas-bu

[Veritas-bu] needs to move nbu database BMR to another server...

2007-03-01 12:20:35
Subject: [Veritas-bu] needs to move nbu database BMR to another server...
From: ray_schafer at symantec.com (Ray Schafer)
Date: Thu, 1 Mar 2007 09:20:35 -0800
Edwin,

(Sorry for the delayed response!)

I have a few comments for you:

Due to the integration of BMR into NBU 6.0, much of the work you had to do with 
previous versions of BMR is now gone. The BMR database is covered by the NBU 
catalog backup.  Nothing special needs to be done to handle the BMR database 
other than the normal catalog backup.  Also, the BMR database can be clustered 
with the NBU Master.  No special setup is required other then what you would do 
to cluster the NBU Master.  

The BMR Boot Server will require some special setup for clustering. Officially, 
clustering of the Boot Server component is unsupported.  You have to handle it 
on your own.  Personally, I would not cluster the boot server.  It is not a 
critical component.  You can handle recovery without it by a couple methods 
which I will discuss below.

If the Master is also a Boot Server, I wouldn't cluster it along with the 
Master. Just install it on one of the nodes of the cluster. Since your Master 
is Solaris 8, it can only be a BMR Boot server for Solaris 8 clients that are 
in its subnet.  If you have Solaris 9 or 10 clients, you cannot use a Solaris 8 
Boot Server for them.  (You could use a Solaris 10 Boot Server for Solaris 8, 
9, and 10 clients).  If you have to cover Solaris 10 or 9 clients, you might 
want to find another more suitable server in the subnet to be the Boot Server.  
If you have Solaris clients in other subnets, they will need a boot server in 
their subnets as well.  The Boot Servers are not required at backup time - the 
clients are not associated in any way with the boot servers during normal 
day-to-day backup operations.  The Boot Servers are only needed at recovery 
time, and you could substitute a CD-Based SRT instead of a Boot Server for DR.  

To recover without a Boot Server in DR, you just use CD-Based SRTs which you 
can make using the ISO image generated by the bmrsrtadm command on the 
production Boot Servers ahead of time.  In DR, you can also use these boot 
CD-Base SRTs to recover the Boot Servers themselves as BMR clients.  You can 
also install the Boot Server code on any client, and create a new SRT within 
about 10 to 15 minutes (in probably less time than it would take to recover the 
Boot Server from bare metal), and use the new Boot Server in DR instead of 
recovering the old ones.  You can also backup the SRTs to NBU, install the Boot 
Server component on a new (suitable) system, and then restore the SRT to the 
new Boot Server, and then run a command on the boot server to define the 
recovered SRT to the BMR database (if it isn't already there from the database 
restore).

The method you describe for the database replication is of concern.  You are 
replicating the database with HP Continuous Access, the catalog information is 
still in binary format stored in files and should be replicable using this 
method, but the database is a Sybase ASA database, and disk-based replication 
does not take into account data held in memory of the Sybase engine.  This is 
my concern. You can shut down the database if your backup windows allow, and 
replicate it while it is off-line.  That should work fine, but I wouldn't count 
on having a good copy of the database using disk based replication of a live 
database.

NBU 6 has the ability to backup the catalog and database hot (while running), 
and save the backups on tape or disk or stage them to disk and replicate to the 
DR site.  (Basically the catalog backup in 6.0 is much like normal backups - 
not special catalog tapes we used to need in v5 or below).  You can recover the 
database from these backups remotely and be guaranteed to have a good database 
at DR.  There is even a recovery wizard.

I have also some words of advice in hostname and clustering.  If the primary 
site has a clustered master, the database will have to be recovered on a 
clustered master at DR. (Development has, in the past, been able to take a 
customers database and convert it to make it work on a non-clustered master, 
but there are no conversion tools available that I know of right now).  Also, 
if the hostname is different at DR, you're going to have a lot of challenges to 
make it work. I would avoid this by keeping the hostnames the same in DR. So 
make sure you test the DR scenario so you know what you will have to do in a 
real DR.



-----Original Message-----
From: veritas-bu-bounces at mailman.eng.auburn.edu [mailto:veritas-bu-bounces 
at mailman.eng.auburn.edu] On Behalf Of epassarella at sorint.it
Sent: Tuesday, February 13, 2007 9:45 AM
To: Veritas-bu at mailman.eng.auburn.edu
Subject: [Veritas-bu] needs to move nbu database BMR to another server...

Hi all,


My enviroment is composed by 1 Master Server 6.0 MP4 (Solaris 8) (also BMR Main 
and Boot Server) in cluster VCS (2 nodes) and 22 Media Server 6.0 MP4 (Solaris 
8, 9 ,10). The BMR and NBU Catalog databases are situated on some LUN on an HP 
Storage (XP12K)  that are mirrored with another one to allow the second node to 
bring online the NBU services.

The Master Server has 2 acs robotics configured and shared, and early they will 
become 3.

Now we have to configure the DR site. In the DR site will be present a new 
master server 6.0 MP4 that needs to receive the catalog and bmr databases from 
the first Master Server. The Catalog and Bmr database will be replicated 
through the HP Continuos Access (Hardware asyncronous replication CA). So all 
databases when will be replicated, will be opened and mounted.

I need to know if this configuration is right...

If yes, the master server in DR site could bring up netbackup services with a 
replicated catalog (that is opened, and mounted)? And what about the BMR 
database?

I've not found any good information about this in all Documentation.

Plz let me know

Thx in Advance

Edwin


Edwin Passarella
Senior Solution Specialist - Storage & Availability
> SORINT
______________________________
Mobile: +39.348.7720322
Phone:  +39.035.697511
Fax:    +39.035.697590 
           edwin.passarella at SORINT.it

PERSONALE E CONFIDENZIALE.
Questa mail potrebbe includere materiale confidenziale, proprietario o 
altrimenti privato per l'uso esclusivo del destinatario.
Se l'avete ricevuto per errore, siete pregati di contattare chi ha inviato il 
messaggio e di cancellarne tutte le copie.
Ogni altro uso da parte vostra del messaggio ? proibito.

PERSONAL AND CONFIDENTIAL.
This message is for the designated recipient only and may contain privileged, 
proprietary, or otherwise private information.  
If you have received it in error, please notify the sender immediately  and 
delete all the copies.
Any other use of the email by you is prohibited.


_______________________________________________
Veritas-bu maillist  -  Veritas-bu at mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


<Prev in Thread] Current Thread [Next in Thread>
  • [Veritas-bu] needs to move nbu database BMR to another server..., Ray Schafer <=