cancel
Showing results for 
Search instead for 
Did you mean: 

OS information after met an Disaster

Vickie
Level 6
Hi All,
Just a query came in here,
 
After facing Disaster, at the time of DR. We need to have the Server with same OS as it was earlier.
How can we get the details of OS previously there on the server.
1 ACCEPTED SOLUTION

Accepted Solutions

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

There is not need for OS to be exactly the same.

It only needs to be of the same 'OS family'.

So, if you know you had a Windows master, you can install a 'current' version, like W2008 R2. catalog restore will work.

If you had a Unix or Linux master, any supported Unix/Linux server will work.

See all of these TechNotes for general guidelines:

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

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

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.symantec.com/docs/TECH31385

 

View solution in original post

11 REPLIES 11

Nicolai
Moderator
Moderator
Partner    VIP   

By using a configuration plan and a configuration system.

http://en.wikipedia.org/wiki/Configuration_Management_(ITSM)

Alternative mail/dropbox netbackup policy configuration to a location in the world far away. 

Vickie
Level 6
Thanks Nicolai,
 
I was thinking the same, but is this the only way we can get the details ?
 
Can we do it in a way, like import the catalog media on other server and get the /usr/openv/netbackup/version file restored. Would it work anyhow ?
 

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

There is not need for OS to be exactly the same.

It only needs to be of the same 'OS family'.

So, if you know you had a Windows master, you can install a 'current' version, like W2008 R2. catalog restore will work.

If you had a Unix or Linux master, any supported Unix/Linux server will work.

See all of these TechNotes for general guidelines:

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

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

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.symantec.com/docs/TECH31385

 

Vickie
Level 6
Thanks Marianne,
 
Thanks for sharing such an important T.N, they really made the concept clear to me now.
 

Nicolai
Moderator
Moderator
Partner    VIP   

Do you want info for all client or just the master/media ?

I mean - in a real DR where all servers are gone everybody will run around and ask what server XXX ran (that what I had in mind).

I also do recommend for Windows system to run "systeminfo" once every day and pipe the information to a file that netbackup the can protect. In a DR this file can be restored and version verified.

I guess systeminfo can be mail outside the organization as well if using Windows master and media servers.

http://technet.microsoft.com/en-us/library/bb491007.aspx

mph999
Level 6
Employee Accredited

Following the expert advice aboe from the wonderful Marianne and amazing Nicolai, the answer should be in the system documentaion that is protected so it is available in the case of DR.

Ths should document evrything required to rebuild the server the way it was - OS type / version / patch level etc ...

In the case of DR for a master server, a good starting point is the nbsu -c -t output - this contains a lot of informtion that could be useful.  It could be scripted so that it is email / stored away from  the master.  

Nicolai
Moderator
Moderator
Partner    VIP   

nbsu -c -t 

+1 Good Point !!

Vickie
Level 6
Thanks all for your suggestive comments.
 

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

We still don't know what your actual requirement is...
- just OS info on NBU master?
- or info of all servers and clients in the environment?

 

Some more reading matter: 

A Guide to Site Disaster Recovery Options 
http://www.symantec.com/docs/TECH66060

DOCUMENTATION: Recovering a Master Server at a disaster recovery site from a catalog backup requires the same topology.
http://www.symantec.com/docs/TECH58358

PS: Although above TN says 'same OS', we know from TNs mentioned in my previous post that this means 'same OS family'. 

I certainly hope that you are asking this for DR preparation purposes...
If so, well done. Good documentation and DR testing is key when preparing.

Vickie
Level 6
Hi Marianne,
 
I was just looking for Master Server only.
And that's too I got to know with the help of experts like you.
Thanks once agagin.

Nicolai
Moderator
Moderator
Partner    VIP   

Please consider to mark one post as a soloution or "request split solution" if you found value in multiple posts.