Avaya Logo

Previous Topic

Next Topic

Book Contents

Book Index

Disk Mirroring feature

Type of feature

Disk mirroring is an optional feature. Because this feature requires two hard disk drives, it is only available on Avaya IR systems running on the Sun Fire 280R, Sun Fire V240, or equivalent hardware platforms.

About the disk mirroring feature

Disk mirroring helps to ensure data security and availability by providing a completely redundant set of data. A redundant set of data greatly reduces the risk of data loss due to a hard disk drive or system failure. If one hard disk drive is disabled or removed, the Avaya IR system can boot automatically from the other hard disk.

Note:
If the system reboots after a hard disk drive has failed or has been removed and the drive has not been properly detached (using the mirror_admin command), it will come up in single user mode. In single user mode, the system will only allow a single login from the console. To restore the system to multi-user mode, log in as root, enter mirror_admin detach at the command prompt, and reboot the system.

The disk mirroring feature is provided by the Solstice DiskSuite 4.2.1 functionality of the Solaris operating system. Only full disk mirroring is supported; partial mirroring of a hard disk drive is not supported.

The following table shows the mirrors, submirrors, directories, and partition sizes that are set up by default on complete (hardware and software) systems purchased from Avaya:

Note:
For software-only solutions, these partitions are not set up by default. If you want to use Disk Mirroring on a system in which you have acquired the hardware on your own, you must first verify that your system is partitioned as sown in the following table (so you can use the AVdm functionality), or you must use the Sun DiskSuite 4.2.1 tools to enable Disk Mirroring. For more information about the DiskSuite tools, see the Sun Product Documentation website for DiskSuite.

Mirror

Primary submirror

Secondary submirror

Directory

Partition size in MB for 35-49 GB drives

Partition size in MB for 50+ GB drives

d0

d01 (c1t0d0s0)

d02 (c1t0d0s0)

/

10240

20480

d1

d11 (c1t0d0s1)

d12 (c1t1d0s1)

swap

2048

2048

d3

d31 (c1t0d0s3)

d32 (c1t1d0s3)

/voice1

5120

10240

d4

d41 (c1t0d0s4)

d42 (c1t1d004)

 

10

10

d5

d51 (c1t0d0s5)

d52 (c1t1d0s5)

/unused1

5120

10240

d6

d61 (c1t0d0s6)

d62 (c1t1d0s6)

/unused2

5120

10240

d7

d71 (c1t0d0s7)

d72 (c1t1d0s7)

/export

free

free

After disk mirroring is set up, the partitioning of the Solaris file system should not be changed.

The status of the disk mirroring configuration is checked daily. The system attempts to fix any problems that are found. If a problem cannot be fixed, the system raises a CGEN043 alarm and sends a message to the following log file: /vs/mirror/elog.

Hardware requirements

Two hard disk drives that have the same size and geography are required for disk mirroring.

Software requirements

The disk mirroring feature is installed using the Disk Mirroring package (AVdm). For more information, see Disk Mirroring package.

Setup considerations

If you bought a complete system (both hardware and software) from Avaya, then Disk Mirroring is automatically installed and enabled by default. You need not do anything.

If you bought the software-only solution, and you are installing it on a Sun Fire 280R or Sun Fire V240 system, the Disk Mirroring software is copied to the /exports/optional_features directory automatically as part of the installation process. However, it is not automatically installed. If you want to enable Disk Mirroring, you must enable it manually. For the procedure, see Enabling Disk Mirroring.

© 2006 Avaya Inc. All Rights Reserved.