Once you have completed Oracle Hierarchical Storage Manager and StorageTek QFS Software configuration, protect your investment by backing up configuration files and related information. Carry out the following tasks:
Proceed as follows:
Log in to the file-system metadata server host as root.
In the example, the host name is samqfs1mds:
root@samqfs1mds:~#
Select a storage location for backup copies of your Oracle HSM configuration. Select an independent file system that can be mounted on the file system host.
Make sure that the selected file system does not share any physical devices with the archiving file system.
Do not store recovery point files in the file system that they are meant to protect. Do not store recovery point files on logical devices, such as partitions or LUNs, that reside on physical devices that also host the archiving file-system.
In the selected file system, create a directory to hold the configuration information. Use the command mkdir mount-point/path, where mount-point is the mount point for the selected independent file system and path is the path and name of the chosen directory.
In the example, we have created the directory /zfs1/sam_config on the independent file system /zfs1:
root@samqfs1mds:~# mkdir /zfs1/sam_config
samexplorer and Safely Store the ReportThe samexplorer is a diagnostic tool that captures and reports comprehensive configuration and status information for the Oracle HSM software and file systems. Oracle support services personnel use the output when troubleshooting. So creating a baseline samexplorer report whenever you configure or reconfigure Oracle HSM software and file systems is a good idea.
Log in to the file-system metadata server host as root.
In the example, the hostname is samqfs1mds:
root@samqfs1mds:~#
In the directory that holds your backup configuration information, create a subdirectory for samexplorer reports. Use the command mkdir mount-point/path, where mount-point is the mount point for the selected independent file system and path is the path and name of the chosen directory.
In the example, we create the directory /zfs1/sam_config/explorer:
root@samqfs1mds:~# mkdir /zfs1/sam_config/explorer root@samqfs1mds:~#
Create the samexplorer report in the selected directory. Use the command samexplorer path/hostname.YYYYMMDD.hhmmz.tar.gz, where path is the path to the chosen directory, hostname is the name of the Oracle HSM file system host, and YYYYMMDD.hhmmz is a date and time stamp.
The default file is named /tmp/SAMreport.hostname.YYYYMMDD.hhmmz.tar.gz.
In the example, we create the file samhost1.20140130.1659MST.tar.gz in the directory /zfs1/sam_config/explorer/ (note that the command below is entered as a single line—the line break is escaped by the backslash):
root@samqfs1mds:~# samexplorer \ /zfs1/sam_config/explorer/samhost1.20140130.1659MST.tar.gz Report name: /zfs1/sam_config/explorer/samhost1.20140130.1659MST.tar.gz Lines per file: 1000 Output format: tar.gz (default) Use -u for unarchived/uncompressed. Please wait............................................. Please wait............................................. Please wait...................................... The following files should now be ftp'ed to your support provider as ftp type binary. /zfs1/sam_config/explorer/samhost1.20140130.1659MST.tar.gz root@samqfs1mds:~#
Repeat this procedure whenever you significantly reconfigure your file systems.
While the samexplorer utility captures much of your Oracle HSM configuration information, for full redundancy, you should carry out the following procedure after ever major configuration effort:
Log in to the file-system host as root.
In the example, the hostname is samqfs1mds:
root@samqfs1mds:~#
In the directory that holds your backup configuration information, create a subdirectory for manual backup copies of your Oracle HSM configuration. Use the command mkdir mount-point/path, where mount-point is the mount point for the selected independent file system and path is the path and name of the chosen directory.
In the example, we are configuring recovery points for the archiving file system /hsmqfs1. So we have created the directory /zfs1/sam_config/samconfig:
root@samqfs1mds:~# mkdir /zfs1/sam_config/samconfig
root@samqfs1mds:~#
In the chosen directory, create a subdirectory for the current Oracle HSM configuration. Use the command mkdir mount-point/path/subdirectory, where mount-point is the mount point for the selected independent file system and path/subdirectory is the path and name of the chosen subdirectory.
In the example, we use the date to name the subdirectory:
root@samqfs1mds:~# mkdir /zfs1/sam_config/samconfig/20140127
root@samqfs1mds:~#
Copy the configuration files to another file system.
/etc/opt/SUNWsamfs/
mcf
archiver.cmd
defaults.conf
diskvols.conf
hosts.family-set-name
hosts.family-set-name.local
preview.cmd
recycler.cmd
releaser.cmd
rft.cmd
samfs.cmd
stager.cmd
inquiry.conf
samremote # SAM-Remote server configuration file
family-set-name # SAM-Remote client configuration file
network-attached-library # Parameters file
scripts/* # Back up all locally modified files
Back up all library catalog data, including that maintained by the historian. For each catalog, use the command /opt/SUNWsamfs/sbin/dump_cat -V catalog-file, where catalog-file is the path and name of the catalog file. Redirect the output to dump-file, in a new location.
In the example, we dump the catalog data for library1 to the file library1cat.dump in a directory on the independent NFS-mounted file system zfs1 (note that the command below is entered as a single line—the line break is escaped by the backslash):
root@samqfs1mds:~# dump_cat -V /var/opt/SUNWsamfs/catalog/library1cat \ > /zfs1/sam_config/20140513/catalogs/library1cat.dump
Copy system configuration files that were modified during Oracle HSM installation and configuration. These may include:
/etc/
syslog.conf
system
vfstab
/kernel/drv/
sgen.conf
samst.conf
samrd.conf
sd.conf
ssd.conf
st.conf
/usr/kernel/drv/dst.conf
Copy any custom shell scripts and crontab entries that you created as part of the Oracle HSM configuration to the selected subdirectory.
For example, if you created crontab entries to manage creation of recovery points and log rotation, you save a copy now.
Record the revision level of the currently installed software, including Oracle HSM, Solaris, and Solaris Cluster (if applicable), and save a copy of the information in a readme file in the chosen subdirectory.
In the chosen subdirectory, save copies of downloaded Oracle HSM, Solaris, and Solaris Cluster packages so that you can restore the software quickly, should it become necessary.
Stop here. You have backed up your configuration, and your file systems are ready to use.