NetBackup software is not FSM-aware. However, new technology in this release enables FSM to detect that NetBackup software is being used and to transparently exclude migrated data and the .DMATTR file from the backup set.
FSM detects a NetBackup backup or restore operation by comparing the NetBackup commands accessing FSM files to command names written in the files backupcmds and restorecmds. FSM installation places default versions of these files in the /opt/fsm/etc directory (where /opt/fsm is the full path to the FSM installation directory).
These default versions can be used to create the files backupcmds and restorecmds for use with NetBackup.
NetBackup requirements
To use NetBackup software to backup UTDM file systems the following requirements must be met:
◆ One of the following software versions must be used:
• The Veritas NetBackup Server version 5.1 (standard backups only; not on SuSE 10)
• Veritas NetBackup Server version 6.0 (standard backups only)
• Veritas NetBackup Server version 6.5 (standard backups only)
◆ Only standard backups may be run.
For example, the FlashBackup package is not supported.
◆ The file /opt/fsm/etc/backupcmds must contain the names of the NetBackup backup commands.
◆ The file /opt/fsm/etc/restorecmds must contain the names of the NetBackup restore commands.
◆ Each NetBackup client machine must have its .DMATTR files listed in the file /opt/openv/netbackup/exclude_list.
The .DMATTR file is not needed to restore files from a NetBackup backup.
Preparing to use NetBackup software
To prepare to use NetBackup software:
1. Install the NetBackup software.
2. Log in to the FSM host as root.
3. Set the FSM environment.
For information on setting the FSM environment, see“Setting the FSM environment” on page 177.
4. Add the full path for each .DMATTR file on the FSM host to the NetBackup exclude_list file:
echo "/dmattrpath" >> /opt/openv/netbackup/exclude_list
where /dmattrpath is the full path to one of the .DMATTR files on the FSM host.
Repeat this command for each .DMATTR file on the FSM host.
Example 5 on page 140provides more information.
5. Change the working directory:
cd /opt/fsm/etc
6. Copy backupcmds.default to backupcmds:
cp backupcmds.default backupcmds
7. Copy the appropriate restorecmds.default file to restorecmds:
cp restorecmds.default.platform restorecmds
where platform is one of the following operating systems for the FSM host:
• aix_solaris for AIX and Solaris
• hp_linux for HP-UX and Linux
8. Restart FSM to load the contents of backupcmds and restorecmds into the kernel:
kill.fsm rc.fsm
The core processes are stopped and restarted, and the names of the NetBackup commands are loaded into the kernel.
Example 5 Adding files to the exclude_list file
An FSM host has two UTDM file systems with the following pathnames:
◆ /mnt/utdm_fs1
◆ /mnt/utdm_fs2
Example 5 (continued) Adding files to the exclude_list file
Run the following commands to add the two .DMATTR files to the exclude_list:
echo "/mnt/utdm_fs1/.DMATTR" >> /opt/openv/netbackup/exclude_list echo "/mnt/utdm_fs2/.DMATTR" >> /opt/openv/netbackup/exclude_list
User-initiated backup and restore
User-initiated backups and restores are those that are started on a client node. These backups and restores do not check the exclude_list file. The .DMATTR files can be manually excluded from these backups. The NetBackup documentation provides more information about user-initiated backups and restores.
Note:A user-initiated restore of a .DMATTR file will fail with an error message. If the .DMATTR files are not excluded from a user-initiated backup, they must be excluded from a user-initiated restore. To do this, refer to the NetBackup documentation.
Backup with NetBackup software
After the requirements described in“NetBackup requirements” on page 139and“Preparing to use NetBackup software” on page 139 are met, a backup of a UTDM file system by using NetBackup software is the same as a backup of any other file system that uses a standard backup.
During a backup, FSM creates one or more DMAPI sessions and associates files with those sessions. A cron job is run every 10 minutes to start the utility utdm_backupcleanup to clean up those sessions.
This cron job is installed in root’s crontab when FSM is installed. This activity is transparent to file system operations.
Backup sessions may be viewed by using the FSM tool prtdmsession.
The output for a backup session takes the following form:
BACKUP filesystem PID ParentPID NBCommand where:
◆ filesystem is the name of the UTDM file system.
◆ PID is the process ID for the session.
◆ ParentPID is the parent process ID.
◆ NBCommand is the name of the NetBackup command.
For more information about using prtdmsession, see“prtdmsession”
on page 188.
Recovery with NetBackup software
After the requirements described in“NetBackup requirements” on page 139and“Preparing to use NetBackup software” on page 139 are met, recovery of a UTDM file system by using NetBackup software is the same as the recovery of any other file system.
The FSM metadata for each recovered file has the recover bit set.
When a file with the recover bit set is accessed it is automatically synchronized.
The dmattrrecoverfs tool is also started by an hourly cron job that is installed in root’s crontab. When dmattrrecoverfs is started it scans the file system for files with the recover bit set and synchronizes any it finds.
During a recovery, FSM creates one or more DMAPI sessions and associates files with those sessions. A cron job is run every 10 minutes to start the utility utdm_backupcleanup to clean up those sessions.
Recovery sessions may be viewed by using the FSM tool
prtdmsession. The output for a recovery session takes the following form:
RESTORE filesystem PID ParentPID NBCommand where:
◆ filesystem is the name of the UTDM file system.
◆ PID is the process ID for the session.
◆ ParentPID is the parent process ID.
◆ NBCommand is the name of the NetBackup command.
For more information about using prtdmsession, see“prtdmsession”
on page 188.