About the archiver.cmd File

The archiver.cmd file controls the archiver's behavior.

The archiver copies files from a file system to volumes on removable media cartridges or to disk partitions in another file system. You can tune the archiver operations to suit the types of files at your site and to suit your site's data protection needs by creating an archiver command file named /etc/opt/SUNWsamfs/archiver.cmd. You are not required to create an archiver.cmd file, but the efficiency and performance of the archiver is improved if you tune the archiver to your site.

By default, the archiver starts whenever the sam-fsd process is started and a file system is mounted.

If the archiver.cmd file does not exist, the archiver is put in a wait state. To restart the archiver, use the samcmd arrun command. If no archiver.cmd file is found after the restart, the archiver continues to run, using the following default settings:

• Archives all files to all available volumes in all configured libraries.

• Makes one copy of each file.

• Sets the archive age for all files to 4 minutes. The archive age is the amount of time since a file's last modification.

• Sets the archive interval to 10 minutes. The archive interval is the amount of time that elapses between complete archiving processes.

To tune the actions of the archiver for your site, set directives in the archiver.cmd. A directive acts like a command parameter and consist of lines of text in the archiver.cmd file. The following rules apply to the archiver.cmd file:

• Each directive line contains one or more fields separated by spaces or tabs.

• Any text that appears after the hash character (#) is treated as a comment and is not examined.

• Lines that end with a backslash character (\) are joined to the next line.

  The archiver.cmd file uses two types of directives.

  For comprehensive information about the archiver.cmd directives, see archiver.cmd(4) in Sun QFS and Sun Storage Archive Manager Reference Manual.

Whenever you make changes to the archiver.cmd file, check for syntax errors using the archiver(1M) command. This command produces a list of all options and writes a list of the volumes, file system content, and errors to the standard output file (stdout). If you encounter errors, correct them in the file and run the archiver(1M) command again to verify your corrections. The archiver does not archive any files if it finds errors in the archiver.cmd file.

Archive Directives

Archive directives specify the general archive operations and consist of two main areas in the archiver.cmd file:

• At the top of the file, global directives affect all file systems defined in your mcf file.

• The lower part of the file contains file system-specific directives. These directives must come after the global directives. For any file system, these directives override the global directives. The file-system-specific directives start with an fs= name directive that identifies the file system.

  Within a file system's directives, you can also specify archive copy directives to customize the number and frequency of the archive copies.

See Chapter 11, Archive Directives (archiver.cmd) for detailed information.

Archive Set Directives

An archive set identifies a group of files to be archived regardless of their file system. A file in a file system can be a member of only one archive set. Files in an archive set share common criteria that pertain to the size, ownership, group, or directory location.

The archive set controls the destination of the archive copy, how long the copy is kept archived, and how long the software waits before archiving the data. All files in an archive set are copied to the volumes associated with that archive set.

The directives for an archive set include:

• Assignment directives – Define archive sets.

• Copy parameters – Define how each archive set is archived.

• VSN association directives – Assign volumes to archive sets.

• VSN pools directives – Define a collection of volumes.

See Chapter 12, Archive Set Directives (archiver.cmd) for detailed information.

How to Create an archiver.cmd File Using the Command Line

• If your site has an /etc/opt/SUNWsamfs/archiver.cmd file and your system is already archiving files, do not make changes to it. Copy the file to a location where you can edit and test it. When it is verified, replace the existing file with the new one.

• If your site does not have a archiver.cmd file, you can edit the file in the /etc/opt/SUNWsamfs directory.

1. Edit the archiver.cmd file to add or change the directives that control archiving at your site.

   For information about the directives you can include in this file, see Chapter 11, Archive Directives (archiver.cmd) and Chapter 12, Archive Set Directives (archiver.cmd) for details.

2. Save and close the archiver.cmd file.
3. Verify the file for the current SAM-QFS environment.

   If you are working with a test archiver.cmd file, use the -c option with the archiver(1M) command and supply the file name.

   # archiver -lv

4. If you are working with a test file, move it to /etc/opt/SUNWsamfs/archiver.cmd.
5. Use the samd config command to propagate the file changes.

   # samd config

How to Create an archiver.cmd File Using SAM-QFS Manager

When you create or edit an archive policy for a file system within the SAM-QFS Manager interface, the archiver.cmd file is automatically created or edited.

1. On the Servers page, select the name of the server for which you want to create a policy.

   The File Systems Summary page is displayed.

2. Select the Archive Administration node in the navigation tree.

   The Archive Policies Summary page is displayed.

3. Click New.

   The New Archive Policy wizard is displayed.

4. Follow the steps in the wizard.

   For detailed instructions about using the New Archive Policy wizard, see the SAM-QFS Manager online help.

   When you save the new archive policy, it is automatically written to the archiver.cmd file.