ProblemDOCUMENTATION: Protecting Novell Open Enterprise Server (OES / OES2) for Linux with Veritas NetBackup 6.5 / 6.5.x / 7.0
Novell Open Enterprise Server (OES / OES2) for Linux supports the Novell Storage Services (NSS) file system type as well as the traditional Linux file systems, such as Ext3, ReiserFS and JFS. NetBackup 6.5 / 6.5.x adds some new functionality. Previously, it was necessary to also have a legacy Netware client configured on NetWare to fully protect NSS on OES/OES2 for Linux, meaning that two NetBackup Clients were utilized (one NetWare, one OES). Starting with NetBackup 6.5, NSS can be protected on OES / OES2 natively without the need for a second (NetWare) client.
However, it may be desired to still have a legacy NetWare client configured for certain functionality. This document describes the capabilities of both the new and legacy backup methods. NetBackup 7.0 does not have a NetWare client but supports NetWare 6.5 by using a NetBackup 6.x or 6.5.x Client. This is documented in the NetBackup 7.0 Operating System compatibility guide (referenced in the related documents section below)
These are the terms and abbreviations that are used in this document and what they mean for the purposes of this discussion.
OES - Novell Open Enterprise Server for Linux.
NSS - Novell Storage Services file system. Its many features and functionalities include a trustee access control model, multiple simultaneous namespace support, native Unicode, user and directory quotas, rich file attributes, multiple data stream support, event file lists, and a file salvage sub-system
SMDR - Storage Management Data Requester. Part of Novell's Storage Management Services (SMS) architecture. The SMDR is responsible for the discovery of the Target Service Agents (TSA).
SMS - Novell's Storage Management Services. The SMS architecture exposes all NSS data through the API ensuring complete protection of the file system.
TSA - Target Service Agents. Part of Novell's Storage Management Services (SMS) architecture. The
TSA provides abstractions of the backup target.
TSAFS - Target Service Agents File System
Method 1- Protecting Novell OES / OES2 for Linux and NSS using a single OES / OES 2 client:
The NetBackup Client for Linux will protect the traditional file system types on an Open Enterprise Server for Linux. The client should be installed to the OES server the same way the client is installed on any Linux machine. Refer to the installation steps in the Veritas NetBackup Installation Guide for UNIX.
Once installed, the Linux client behaves as it would on a normal SuSE Enterprise Server. The entire Linux file system should be protected by creating a policy to back up the OES server. See the Veritas NetBackup System Administrator's Guide for UNIX for more information.
The 6.5 or later OES client can backup a Novell Storage Services (NSS) volume natively. It is no longer necessary to have a separate NetWare server to backup NSS data on OES.
To protect the NSS File System via the NetBackup Linux Client, edit /etc/opt/novell/nss/nssstart.cfg (or use nsscon) to designate the following two settings:
Other benefits of using this method:
The Synthetic backup and checkpoint restart features can be utilized on OES2 servers. Additionally, LAN avoidance for faster backups is possible with the SAN Media Server or SAN Client options.
For disaster recovery notes, see the last section of this document, which applies to both backup methods.
Known issues / limitations with this method:
- eDirectory databases on OES for Linux cannot be protected at this time using NetBackup on OES natively. However, if the database is replicated to a legacy NetWare server, it can be protected by backing up that database. See the Veritas NetBackup for Novell NetWare Client System Administrator's Guide for more information.
- iFolder databases can only be backed up as a flat file system with the current SMS architecture on OES for Linux. At this time, Novell only supports a full disaster recovery of the iFolder data store as a restore method for iFolder. Please refer to your Novell documentation for more information on protecting iFolder with TSAFS on OES for Linux.
- GroupWise cannot be protected with traditional methods. There are currently 2 methods in which to backup GroupWise data with a single OES client.
Note: Disk space equal or greater to the primary storage must be allocated to store backups.
- Use Novell TSAFS on Netware server and use NetBackup client to backup Groupwise using Targets.
Note: This will send backup data over the network twice.
- If compression is used on NSS volumes, this data will be decompressed during backup before it is written to the destination. Ensure proper storage is available
- ALL_LOCAL DRIVES: Etracks 1428118 (6.5.2) 1595973 (6.5.3) 1678455 (6.5.4)
When using the ALL_LOCAL DRIVES directive the mount point of /opt/novell/nss/mnt/.pools is not skipped. If the mount point is no longer valid, the job will fail with Status 71 (none of the files in the file list exist.) Attempts to exclude this file will be unsuccessful. If this problem is seen, please contact Symantec Technical Support, referencing the above Etrack for the NetBackup version in place.
Method 2 - Protecting Novell OES / OES2 for Linux and NSS using a single OES / OES 2 client using a Netware client (Legacy method)
The NetBackup Client for Netware can be installed on a standard NetWare server in the NetBackup environment. The storage management data requester will see the TSA file system from the OES server when creating a new target on the standard NetWare server. This is where the target should reside and the policy should point. This information also applies to the NetBackup 6.0 release.
A separate NetBackup NetWare Client can be used to protect the NSS data mounted on a Linux OES server. The NetBackup Client for Netware should be installed on a standard NetWare server in the NetBackup environment. The NetWare client software can be found on the NetBackup Windows Server CD in the <cdrom>\PC_Clnt\NetWare directory. The NetWare Client can then be backed up in order to protect the NSS data. Refer to the installation steps in the Veritas Netware Client System Administrator Guide, Chapter 2.
In order for the NetWare Client to see the NSS volumes as advertised by the SMS layer, the file system TSA, TSAFS, must be running in NetWare mode. To check if TSAFS is running in NetWare mode, type:
This option lists all TSAs currently registered with SMDR and in what mode and with what options they are running. If TSAFS is not shown running in NetWare mode it will need to be unloaded and loaded again with a switch by typing:
# /opt/novell/sms/bin/smsconfig -u tsafs
# /opt/novell/sms/bin/smsconfig -l tsafs --tsaMode=netware
TSAFS can be configured to start in NetWare mode at startup by modifying the /etc/opt/novell/sms/tsafs.conf file. See your Novell documentation for more details.
Once TSAFS is advertising the NSS volumes through SMS, the NetWare Client can be used to back them up as targets. See the VERITAS NetBackup for Novell NetWare Client System Administrator's Guide for UNIX and Windows for installation and configuration instructions.
Once the NetWare Client is configured, create a target for each NSS volume.
2. Next choose <MachineName>.NetWare File System.
3. For the Target Services choose 1 and log in with the eDirectory administrator or equivalent credentials.
4. Choose the appropriate volume(s) under Available Resources. Choosing 1) NetWare server may not properly back up all of the NSS volumes mounted.
Note: The SYS "volume" that holds the /PUBLIC and /LOGIN directories is not advertised through the SMS layer. These files will be backed up as part of the traditional Linux file system as /usr/novell/sys/.
5. The Name Space Type should be 4) NFS for NSS volumes.
6. Create any inclusions or exclusions for the target as you normally would.
Create a Standard policy on the Master Server using the NetWare server as the client and the targets for the Backup Selections. These targets can be used for backup and restore the same way normal NetWare server targets are used. See the Veritas NetBackup for Novell NetWare Client System Administrator's Guide for UNIX and Windows for more information. The Open File Backup Option cannot be used on NSS volumes when mounted on OES for Linux.
Backing up Groupwise:
TSAFS also includes GroupWise backup functionality on OES Linux. This functionality does not provide object level backup and restore. TSAFS locks the GroupWise database files and ensures that a consistent snapshot of the database is backed up.
This functionality is not turned on by default when TSAFS is started on OES Linux. The option to run TSAFS in GroupWise mode is EnableGW. To check if TSAFS is running with the EnableGW option, type:
This option lists all TSAs currently registered with SMDR and in what mode and with what options they are running. If TSAFS is not shown with the EnableGW option it will need to be unloaded and loaded again with a switch by typing:
# /opt/novell/sms/bin/smsconfig -l tsafs --tsaMode=netware --EnableGW
TSAFS can be configured to start with the GroupWise option at startup by modifying the /etc/opt/novell/sms/tsafs.conf file. Refer to your Novell documentation for more details.
Once the NetWare Client is configured, create a target for GroupWise.
2. Next choose <MachineName>.GroupWise System.
3. For the Target Services choose 1 and log in with the eDirectory administrator or equivalent credentials.
4. Choose the appropriate post office(s) or domain(s) under Available Resources.
5. Choose 1) LONG for the Name Space Type.
Create a Standard policy on the Master Server, using the NetWare server as the client and the targets for the Backup Selections.
Additionally, eDirectory (formerly called NSS on the NetWare platform) and iFolder should be available to the NetWare client as targets via SMS.
Notes for Restoring NSS:
In the event of a hardware failure or other event that requires the OES server to be recovered, the replacement disk, or disks, should be partitioned identically to the original. OES should be reinstalled with the same options and services, and the NSS volumes should be created again. For this reason, it is recommended that the partition/volume geometry, names, attributes, mount points, etc. be documented and readily accessible.
Once the server is reinstalled and the operating system is operational, the NetBackup Client for Linux can be installed and used to restore the file system. NSS can be recovered to the OES server using the original targets, as long as the NSS volumes were created using the same names and sizes.
If the root partition was lost, the best approach may be to reload the operating system on an alternate boot disk and boot from that disk. Once the NetBackup Client for Linux is installed, you can restore root to its original partition. This lets you recover the root partition without risking a crash due to overwriting files being used by the operating system during the restore.
Refer to the Veritas NetBackup Troubleshooting Guide for UNIX and Windows for more information on disaster recovery.