DOCUMENTATION: NetBackup Support for SUN Virtualization

Article:TECH65627  |  Created: 2008-01-01  |  Updated: 2011-06-24  |  Article URL http://www.symantec.com/docs/TECH65627
Article Type
Technical Solution


Environment

Issue



DOCUMENTATION: NetBackup Support for SUN Virtualization


Solution



Solaris 10 Zones Support:

Zones (containers) are isolated application execution environments that the administrator can create on a single Solaris 10 instance. Each Solaris update may add additional features and fixes so is best to be at latest update.

All NetBackup components, supported with Solaris 10 physical servers, are supported in a Solaris 10 global zone. Local zone support is limited to standard client, database agents, master server, disk media server and Bare Metal Restore client (as described in the Bare Metal Restore Administrators Guide).

Backups can be performed in individual local zones, or by backing up the entire system from the global zone.

Global Zone Backup
A NetBackup client in the global zone can be used to back up the entire system. A full restore of the global zone restores everything in the global zone and the local zones as well, as long as the respective root file systems of the local zones were included in the backup. Make sure that the databases in local zones are offline before starting the backup from the global zone.

Local Zone Backup
Clients should be configured to skip lofs file systems to avoid backing them up twice. The client and DB agent are required in local zone for hot database backups.

Systems configured with local zones can be backed up with the NetBackup Solaris 10 standard client, provided the standard client is loaded on each local zone in which a backup is desired.  On a local zone, a workaround must be performed to successfully load the NetBackup standard client. Prior to installation, the /usr/openv directory must be created and made writeable for a successful NetBackup client installation. To do this, you must use the zlogin process to become "Zone root" on the local zone. Then, you will be able to create a link from /usr/openv to a writeable location on the local zone.

Instructions: Clarification for installing NetBackup standard client software in local zones

Note: For NetBackup 6.0, this procedure is covered in the NetBackup 6.0 Release Notes/Known Issues Documentation on page 10.  There is also a reference to this procedure in the NetBackup 6.0 Release Impact Bulletin on page 119.  Both documents are referenced below.

On a server whose local zone is not using a read-only loopback device for the /usr directory, client push-install or local install is done normally. Please refer to appropriate guides for your environment

On a server that:
 
  • Does not have a master/media server on the global zone
  • Has a sparse local zone using a read-only loopback device for the /usr directory
The procedure is:
In the global zone, create /usr/openv as a symbolic link to the location in which you will be installing the software to in the local.  This will need to be done even if the global zone does NOT have that directory.

For example:
# ln -s /nonglobdir/openv /usr/openv
# ls /nonglobdir/openv
/nonglobdir/openv: No such file or directory
# ls -al /usr/openv
lrwxrwxrwx   1 root     root          10 Aug 23 15:13 /usr/openv -> /nonglobdir/openv

In the local zone, make sure that /usr/openv exists as a link.
# ls -al /usr/openv
lrwxrwxrwx   1 root     root          10 Aug 23 15:13 /usr/openv -> /nonglobdir/openv

In the local zone, make sure that the directory linked exists and is writeable.
# ls -al /nonglobdir/openv
total 32
drwxr-xr-x   9 root     bin          512 Aug 18 15:23 ./
drwxr-xr-x  18 root     bin          512 Aug 18 15:30 ../

A client "push" install or local install can now be done normally following the procedures in NetBackup documentation.

On a server that:
 
  • Has a master/media server installed on the global zone
  • Has a sparse local zone using a read-only loopback device for the /usr directory
The procedure is:
In the global zone, /usr/openv in a default installation is a link to /opt/openv.  Alternatively, the master/media server can be installed in some BASEDIR other than the default /opt, and /usr/openv be linked to /BASEDIR/openv.  In either case, verify the directory linked to by /usr/openv.

For example:
# ls -al /usr/openv
lrwxrwxrwx   1 root     other         10 Aug 18 11:39 /usr/openv -> /opt/openv/

In the local zone, create a writeable directory where the linked /usr/openv points:
# mkdir /opt/openv

A client "push" install or local install can now be done normally following the procedures in NetBackup documentation.

Also, when adding a local zone to a system with NetBackup 5.x master or media server loaded in the global zone, a Solaris 10 error notification will occur during the exporting of applications to the local zone. The following error occurs:
*** package <VRTSnetbp> was not installed:
The package <VRTSnetbp> is either not fully installed in the global zone, or the package contains a request script. Only packages that are fully installed in the global zone and that do not contain a request script can be installed when a new zone is created. If this package does not contain a request script, you can correct this problem by removing and reinstalling the package in the global zone.

The corrective workaround for this problem is to install the NetBackup client (also known as the "Standard" client) on the local zone.

NetBackup Master Server or Media Server (disk backups only) can be installed in a local zone (whole root).
 
The ICS Installer will not allow installation of any package on a local zone.  Therefore, all the packages will have to be installed manually (in order):

1) To install ICSCO and PBX:
# pkgadd -d ./infrastructure_core_services/pkgs VRTSicsco VRTSpbx

2) To install AT:
# pkgadd -d ./infrastructure_core_services/pkgs VRTSat

3) To install AZ:
# pkgadd -d ./infrastructure_core_services/pkgs VRTSaz
 

Solaris 10 Logical Domains (LDoms) Support

Solaris 10 Logical Domains (LDoms) are only available on Sun servers utilizing CMT technology. Solaris 10 LDoms provide virtual machines that run an independent operating system instance, and contain virtualized CPU, memory, storage, console, and cryptographic devices.

 
  • The LDom hypervisor is a firmware layer on the flash PROM of the server motherboard
  • Control domain - Executes Logical Domains Manager software to govern logical domain creation and assignment of physical resources
  • Service domain - Interfaces with the hypervisor on behalf of a guest domain to manage access to hardware resources, such as CPU, memory, network, disk, console, and cryptographic units
  • I/O domain - Controls direct, physical access to input/output devices, such as PCI Express cards, storage units, and network devices.
  • Guest domain - Utilizes virtual devices offered by service and I/O domains and operates under the management of the control domain

Each update to LDoms may add additional features and fixes, so it is recommended that the latest updates always be applied.

All NetBackup components supported with Solaris 10 SPARC physical servers are supported in a Solaris 10 LDoms Control Domain with the exception of Bare Metal Restore (server or client). Guest domain support is limited to standard client, database agents, master server and disk media server.

Be sure to backup the LDoms environment with the Control Domain backup:
 
  • Backup the database files in /var/opt/SUNWldm.
  • Protect the primary domain configuration with the following command:
# ldm list-constraints -x primary > primary.xml
 


Bare Metal Restore (BMR)
BMR Server is supported in Zones(Global and Local) and LDoms (Control and Guest domains).
See NetBackup 6.5 BMR Administrators Guide for BMR client support in Solaris Zones.
BMR client or boot server are not supported in LDom Guest domains.

Useful SUN Forum sites:

Zones Forum:
 http://opensolaris.org/jive/search.jspa?q=ZONES
LDoms Forum:
 http://opensolaris.org/jive/category.jspa?categoryID=115



 



Legacy ID



315561


Article URL http://www.symantec.com/docs/TECH65627


Terms of use for this information are found in Legal Notices