Preparing for DR Detach Operations

▼To Make an Unsupported Tape Device Detach- Safe

For the Solaris 9 operating environment, tape devices that are natively supported by Sun Microsystems are suspend-safe and detach-safe. For details, refer to the st(7D) man page for a list of natively-supported drives. If a system board to be detached contains a natively-supported tape device, you can safely detach the board without suspending the device.

However, if you want to use a tape device that is not natively supported by Sun Microsystems, you can use it, but you must make it detach-safe by performing the following steps.

1.Edit the /kernel/drv/st.conf file with the ST_UNLOADABLE (0x0400) flag set in the entry. Refer to the st(7D) man page for more information.

2.After all DR configuration tasks are complete, be sure to reboot the domain so that this configuration can take effect.

You must prepare a board for DR detach operations by following the steps described below. Although the following list of tasks implies a sequence of order, strict adherence to the order is not necessary. These steps apply to boards containing I/O or non-network devices. .

1.Unmount file systems.

For example, if you are using Solstice DiskSuite metadevices, you must unmount the file system for metadevices that have a board-resident partition (for example, umount /partit).

If you have suspend-unsafe devices that manage file systems, unmount those file systems before a detach operation. If have to manually suspend unsafe devices that manage file systems, lock those file systems using the lockfs(1M) command before manually suspending the unsafe devices.

Caution – Unmounting shared file systems by using the share(1M) utility may affect NFS client systems.

2. Remove disk partitions from the swap configuration by using swap(1M).

Chapter 1 Configuring DR 9