diskvols.conf - Defines disk archive volumes for Oracle HSM environments
∕etc∕opt∕SUNWsamfs∕diskvols.conf
SUNWsamfs
A Oracle HSM file can have one or more of its archive copies written to a disk archive resource. A disk volume that represents the resource is stored in the inode of the archived file.
The disk volume configuration file, diskvols.conf,
defines the mapping between a disk volume and
the corresponding resource.
The sam-fsd daemon reads the diskvols.conf file
when the sam-fsd daemon is started. The diskvols.conf file
can be changed at any time while the sam-fsd daemon
is running. The changes take effect when the sam-fsd daemon
is restarted
or sent the signal SIGHUP.
The mappings are specified one per line. Each line consists of two
fields separated by white space. Leading white space is ignored. Everything
after a pound character (#) is ignored.
Lines can be continued by using a backslash character (\fB\) as the
last character on the line.
The syntax for this line is as follows:
disk_volume resource
where:
An alphanumeric string. The string can contain up to 31 characters.
A resource specification in one of the following formats:
This format contains the path name of the disk archive directory on the local host.
:]pathnameThis format specifies the host as the name of the disk archive server and pathname as the path name of the disk archive directory on that host.
:port]This format defines a disk volume as residing on an Oracle StorageTek 5800 Storage System. The host field contains the name or IP address and port as the port number of the Oracle StorageTek 5800 Storage System. By default, the port number is 8080.
NOTE: Extreme care must be taken when configuring disk archiving in an environment with multiple Oracle HSM servers. The diskvols.conf file for each Oracle HSM server must point to a unique set of disk volume resource specifications (disk archiving target directories). If any of these are shared between different Oracle HSM servers, then running the recycler from one Oracle HSM server will destroy the disk archive data that is being managed by the other Oracle HSM server.
The clients and endclients directives delimit this
section of the diskvols.conf file.
The client definitions section defines the trusted client systems. After the disk archiving server accepts a client connection, it verifies that the socket address belongs to a host in the trusted client definitions section. If not, the connection is refused.
The file transfer parameters which set the TCP window size and block
size are defined in the rft.cmd configuration file on the server.
These can be tuned for best performance.
This example shows two diskvols.conf files.
File 1 is a diskvols.conf file on client system earth
that defines the following:
There is one volume serial name (VSN) for a local disk archive.
There are two remote VSNs. Remote
VSN remote1 resides in ∕quidditch on the remote
server gryffindor, and remote VSN remote2 resides
in ∕quidditch on remote server ravenclaw.
There is one volume serial name (VSN) for an Oracle StorageTek 5800 Storage System.
# # This is file ∕etc∕opt∕SUNWsamfs∕diskvols.conf on local system earth # local_archive ∕DiskArchive remote1 gryffindor:∕quidditch remote2 ravenclaw:∕quidditch stk_archive stk5800 mars
File 2 is the diskvols.conf file that resides on
the server system gryffindor and ravenclaw.
Only the diskvols.conf file for
server gryffindor is shown.
# # This is file ∕etc∕opt∕SUNWsamfs∕diskvols.conf on server system gryffindor # clients earth endclients
If more than one Oracle HSM environment is sharing an Oracle StorageTek 5800 Storage System you must take extra care when configuring the diskvols.conf file. If you are running multiple connections to an Oracle StorageTek 5800 Storage System disk archive, then the disk_volume name needs to be unique across all Oracle HSM environments. For example, stk_archive_earth on one server, stk_archive_pluto on the next server, etc.
# # This is file ∕etc∕opt∕SUNWsamfs∕diskvols.conf on server earth # stk_archive_earth stk5800 mars # # This is file ∕etc∕opt∕SUNWsamfs∕diskvols.conf on server pluto # stk_archive_pluto stk5800 mars
It is important to follow this recommendation, because there is no enforcement of this restriction in the Oracle HSM software.
