Download - Oracle Documentation

18
18.5 Local Metadevice Administration
Local disks are usually not mirrored. However, some local file systems might
have UFS logs. If an error occurs, perform the same actions as when the entire
mirror fails, as specified in “Managing UFS Logs” on page 18-8.
If the entire root disk fails, use the instructions in “Restoring a Boot Disk from
Backup” on page 21-2.
18.6 Destructive Metadevice Actions to Avoid
The metadevice actions that are not supported in Ultra Enterprise Cluster HA
configurations include:
•
•
•
Creation of a one-way mirror in a diskset
Creation of a configuration with too few metadevice state database replicas
on the local disks
Modification of metadevice state database replicas on multihost disks,
unless there are explicit instructions to do so in this or another
SPARCcluster book.
18.7 Backing Up Multihost Data Using Solstice Backup
This section contains suggestions for using Solstice Backup to back up Ultra
Enterprise Cluster HA file systems.
Solstice Backup is designed to run each copy of the server software on a single,
licensed server. You obtain an “enabler” code and an “authorization” code,
which are associated with a single physical host. Solstice Backup expects files
to be recovered using the same physical server from which they were backed
up.
Solstice Backup has considerable data about the physical machines (host names
and host IDs) corresponding to the server and clients. Solstice Backup’s
information about the underlying physical machines on which the logical hosts
are configured affects how it stores client indexes.
Do not put the Solstice Backup /nsr database on the multihost disks. Conflicts
can arise if two different Solstice Backup servers attempt to access the same
/nsr database.
18-10
Solstice HA 1.3 User’s Guide—April 1997