Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

path for disaster recovery when using the appliance as master server

Created: 08 Oct 2012 • Updated: 12 Oct 2012 | 8 comments
Rami Nasser's picture
This issue has been solved. See solution.

Hi All ,

firstly :I was confused where to ask this question here or in appliance forum.if it should be there so may i will ask it again there!!!

when we creating  catalog backup policy we adding the path of disaster recovery as example : d:\disaster recovery. but when using an appliance as master server what is the recommended path (i'm ruuning the admin console in linux machine) .I believe it shoulde be some where in side the appliance.please advice

Regards,

Discussion Filed Under:

Comments 8 CommentsJump to latest comment

Marianne's picture

There is no 'recommended path' other than a 'network share'. Same recommendations for Unix/Linux master will apply here.

Extract from NBU Admin Guide: 

Specify the directory where the disaster recovery information is to be saved. Do not save the
disaster recovery information to the local computer. Symantec recommends that you save the image file to a network share or a removable device.
The share must be established and available before the hot catalog backup runs.
Specify an NFS share or a UNC path (CIFS Windows share).
When indicating a UNC path, note the following:
■ A Windows master server can indicate a UNC path to a Windows computer.
■ A UNIX master server cannot indicate a UNC path to a Windows computer.
■ A UNIX master server cannot indicate a UNC path to a UNIX machine. To do so, first mount that UNC location on the master server, and then provide theUNC path to the UNIX machine.
The path for the disaster recovery information cannot be to a directory that is on the same partition as /usr/openv/netbackup. If the path is to a location on the same partition as /usr/openv/netbackup, NetBackup displays a status 20 error message. The message states that the disk path is invalid. Change the path on the Disaster Recovery tab to a directory on a different partition.
 

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

Rami Nasser's picture

thanks for you responce.the general information here are clear but you know that the appliance that acting as master server should be managed by any other client because it not working directly with the admin console,but every thing is working inside the appliance so as I understand : firstly, share option should be opended in  the appliance then as my client is linux and it working with NFS only ,so on this client we have to mount NFS share directory in the client.(ofcourse it should be created before) please correct me if wrong!!

Regards,

Marianne's picture

The Appliance is a Linux server. You can login to it same as any Linux server (use something like putty).
Management is exactly the same as any other NBU master/media server on Linux - use Java or Windows Admin Console on your desktop to manage the server.

NFS share can be mounted on the Appliance at OS level.

PS: have you attended training for NetBackup Appliances? Couple of extra steps to get to root prompt (#), but 100% possible.

I'm looking at mountpoints on our demo unit:

# df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/sda1             229G   33G  185G  15% /
udev                   24G  176K   24G   1% /dev
/dev/sda3             656G  323M  622G   1% /log
tmpfs                 4.0K     0  4.0K   0% /dev/vx
/dev/vx/dsk/nbuapp/catvol
                      931G  344M  923G   1% /cat
localhost:/lib        229G   33G  185G  15% /home/nbusers/lib
localhost:/lib64      229G   33G  185G  15% /home/nbusers/lib64
localhost:/usr/openv  229G   33G  185G  15% /home/nbusers/usr/openv
localhost:/usr/lib64  229G   33G  185G  15% /home/nbusers/usr/lib64
/dev/vx/dsk/nbuapp/advol
                      744G  281M  738G   1% /advdisk
/dev/vx/dsk/nbuapp/pdvol
                      3.0T  713M  2.9T   1% /disk
 
 
Because the catalogs are on a separate filesystem, I would simply create a folder in / and ensure that the DR-file is emailed to me on a daily basis.
This will be good enough where NFS mount is not possible.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

Rami Nasser's picture

Yes I attended  atraining for 5020 and 5220 appliances and both of them contains SUSE os and they have different shell but it is simple to use.

no problem with using the appliance and also i have a lab for testing .i believe that nfs and cifs possible for network sharing through unix and windows but i confused if there are better way to create path for disaster recovery when using appliances.or it has different way for disaster path.need best practice

Thanks

share path.png
Mark_Solutions's picture

The share you have opened in your screenshot is the software share which is used for uploading patches to the appliance only - you should not use that for anything else so i would reccomend doing a "share close" on it before continuing

I would have thought a UNC path would suffice without having to mount a file system onto the appliance

The DR Section allows you to put in the appropriate credentials for tht UNC path - so just setup a share on a server somewhere (preferably off site but with good network connection) and use a UNC path to that share and the appropriate credentials

Hope this helps

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.

Mark_Solutions's picture

A check shows that mail is enabled via the Main - Settings - Email section

The SMTP Add adds your smtp server to use

You can also add in your e-mail address to use

I have the feeling that this is also accessed in the GUI and what you need is to ensure it is setup for the "Software Admin" as that is the one used for the Catalog DR

See page 49 and prior of the 52xx Admin Guide for more info

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.

Rami Nasser's picture

thanks Mark for your support but I still have a confuse because i'm new in appliances. As i know that open share inside the appliance giving me ability to use the software preinstalled in the appliance to push netbackup software to unix clients or windows clients as it contain installation files please correct me if i,m wrong.

"UNC path would suffice without having to mount a file system onto the appliance" dou you mean simple create a directory in the root path of appliance as (/root/disasterrecovery) or by create a sharefolder in one of the server in the network and when configure the path in catalog policy i have to add \\server\share\

regarding SMTP I think this is very important to add email adress to use and i know that it may be configured through GUI ADMINCONSOLE

Thanks

please be patient for my questions that may be simple for the experts such youcrying

Mark_Solutions's picture

OK - the DR file is best kept on a alternative server rather than on the Master Server - this is because you need the DR file in the event of a disater at which time your Master may no longer exist.

So select another server somewhere (preferably off site) and create a new share on it and then in the catalog policy just use a UNC path to that share for the location of the DR file, along with any required authentication.

Fir the DR e-mail add the smtp server and email address to be used via the CLISH on the appliance (or maybe the GUI but don't have one to hand this week to double check) and the e-mail for the catalog should then work.

The "Software" share is only used for the appliance itself for uploading its patches

For NetBackup client software the appliance should have a pre-enabled shares named "install" and "inst/client" that contains the clients.

So for Windows clients from the client just go to \\appliancename\install and run the quickinstall.exe that is located in that share.

For unix clients, on the client, map a drive (nfs share) to \\appliancename\inst\client and run the unix-client-install script from that location

Once installed open the clients bp.conf and add the appliance Master name etc. as this does not get automatically populated

There are also links on the home page of the appliance web gui to access the software

Hope this helps

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.

SOLUTION