6 Finishing Up

Once you have completed configuration and data recovery, you should perform two last tasks:

Restoring Archiving File Systems to Normal Operation
Preserving the New Configuration Information.

Restoring Archiving File Systems to Normal Operation

If you disabled archiving and recycling, re-enable them now:

Enable Archiving
Enable Recycling.

Enable Archiving

Open the /etc/opt/SUNWsamfs/archiver.cmd file in a text editor, and scroll down to the first wait directive that you added to the file when you started recovery efforts.

In the example, we use the vi editor:

root@solaris:~# vi /etc/opt/SUNWsamfs/archiver.cmd
# Configuration file for Oracle HSM archiving file systems
#-----------------------------------------------------------------------
# General Directives
archivemeta = off
examine = noscan
#-----------------------------------------------------------------------
# Archive Set Assignments 
wait
fs = samqfs1
logfile = /var/adm/samqfs1.archive.log
all .
    1 -norelease 15m
    2 -norelease 15m
fs = samqfs2
logfile = /var/adm/samqfs2.archive.log
all .
...

To enable archiving, delete every wait directive that you added to the file when you started recovery efforts. Save the file, and close the editor.

In the example, we remove the single wait directive that we added:

root@solaris:~# vi /etc/opt/SUNWsamfs/archiver.cmd
...
#-----------------------------------------------------------------------
# Archive Set Assignments
fs = samqfs1
logfile = /var/adm/samqfs1.archive.log
all .
    1 -norelease 15m
    2 -norelease 15m
    3 -norelease 15m
fs = samqfs2
...
:wq
root@solaris:~#

Next, Enable Recycling.

Enable Recycling

Open the /etc/opt/SUNWsamfs/recycler.cmd file in a text editor, an scroll down to the first -ignore parameter that you added to the file when you started recovery efforts.

In the example, we use the vi editor:

root@solaris:~# vi /etc/opt/SUNWsamfs/recycler.cmd
# Configuration file for Oracle HSM archiving file systems
#-----------------------------------------------------------------------
logfile = /var/adm/recycler.log
no_recycle tp VOL[0-9][2-9][0-9]
library1 -hwm 95 -mingain 60 -ignore

Remove every -ignore parameter that you added when you started recovery efforts.Then save the file, and close the editor.

In the example, we have only one library in the Oracle HSM configuration, library1:

root@solaris:~# vi /etc/opt/SUNWsamfs/recycler.cmd
# Configuration file for Oracle HSM archiving file systems
#-----------------------------------------------------------------------
logfile = /var/adm/recycler.log
no_recycle tp VOL[0-9][2-9][0-9]
library1 -hwm 95 -mingain 60 -ignore
:wq
root@solaris:~#

Check the modified configuration files for errors. Use the commands archiver -lv to check the archiver.cmd file and run the initialization command sam-fsd. Correct any errors.

In the example, the configuration files are correct:

root@solaris:~# archiver -lv
Reading '/etc/opt/SUNWsamfs/archiver.cmd'.
1: #-----------------------------------------------------------------------
2: # General Directives
3: archivemeta = off
4: examine = noscan
5: #-----------------------------------------------------------------------
5: # Archive Set Assignments
7: fs = samqfs1
...
   .sort: path
root@solaris:~# sam-fsd
Trace file controls:
sam-amld      /var/opt/SUNWsamfs/trace/sam-amld
...
Would start sam-archiverd()
Would start sam-stagealld()
Would start sam-stagerd()
Would start sam-amld()
root@solaris:~#

Reconfigure the Oracle HSM software using the restored configuration files. Use the command samd config.

Archiving and recycling processes resume.
```
root@solaris:~# samd config
```
If you are recovering from a server problem or from loss or damage to one more file systems, Save the Newly Restored Oracle HSM Configuration.
Otherwise, stop here.

Preserving the New Configuration Information

If you have changed the Oracle HSM configuration in the course of recovery efforts, you should back up the configuration again now.

Save the Newly Restored Oracle HSM Configuration

Run the samexplorer command and create a SAMreport. Save it in the directory that holds your backup configuration information. 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 name is /tmp/SAMreport.hostname.YYYYMMDD.hhmmz.tar.gz. In the example, we already have a directory for saving SAMreports, /zfs1/sam_config/. So we create the report in this directory:

root@solaris:~# samexplorer /zfs1/sam_config/explorer/server1.20140430.1659MST.tar.gz
     Report name:     /zfs1/sam_config/explorer/samhost1.20140430.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.20140430.1659MST.tar.gz

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
/var/opt/SUNWsamfs/

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:
```
root@solaris:~# 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 a crontab entry to manage creation of recovery points, you would save a copy now.
Record the revision level of the currently installed software, including Oracle 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 any newly downloaded Oracle Oracle HSM, Solaris, and Solaris Cluster packages so that you can restore the software quickly, should it again become necessary.