Avaya Media Processing Server System Manual de usuario Pagina 144

  • Descarga
  • Añadir a mis manuales
  • Imprimir
  • Pagina
    / 188
  • Tabla de contenidos
  • SOLUCIÓN DE PROBLEMAS
  • MARCADORES
  • Valorado. / 5. Basado en revisión del cliente
Vista de pagina 143
Media Processing Server System Operator’s Guide
Page 144 # P0602484 Ver: 2.7
Backing Up and Maintaining a Mirrored System Drive
The mirrorbu script backs up mirrored systems. The following is an overview of
mirrorbu execution. For complete details, refer to the MPS Disk Mirroring
Installation, Configuration and Recovery manual.
Mirrorbu can only be run on systems that have active, synchronized mirrors.
Each filesystem (except root) is write-locked momentarily while one of its
mirrors is taken offline. Anything that attempts to write to the locked
filesystem hangs until it is unlocked, therefore, run mirrorbu during a time
when the system is least active. Once the mirror is offline, the filesystem is
unlocked (write allowable). The filesystem is not mirrored while offline.
ufsdump is executed to dump the offline mirror to tape. Filesystems are
dumped consecutively to the tape. If the tape becomes full, a prompt appears
to insert another tape. To place each filesystem dump on a separate tape,
specify the -o option on the mirrorbu command line. A prompt appears for
a new tape for every filesystem when the -o option is specified.
The mirror is brought back online when the ufsdump is complete, and mirror
resynchronization occurs automatically.
This procedure takes between 1 hour to several hours, depending on the
amount of data being backed up.
Mirrorbu dumps the mirrored system drive only. Backup the mmf
filesystem(s) separately.
If mirrorbu is invoked by a cron job, check the cron log in /var/log and the
mirrorbu log in /etc/mirrorBUdata. Also check mail for the root user.
The backup will not complete if it requires a tape change when invoked via
cron.
Preparation
Perform the following steps prior to executing mirrorbu. Some information must be
recorded for later restoration.
1. Login as root. (Execute su - ).
2. Choose a backup time when the system is least active. Since the mirror is
taken offline and dumped, it is not necessary to terminate applications.
However, there is a time when the filesystem is locked that can cause an
application write to hang. The filesystem is locked while the mirror is
taken offline, then immediately unlocked. The offline mirror is then
dumped and the mirror is taken online. Extensive writes to the unmirrored
primary slice could generate a small performance degradation when the
mirror is taken online and forced to synchronize.
3. Determine the number of tapes required. Execute df -k and add up the
usage for all the displayed system disk slices, to determine the number of
tapes required. The space allocation listed under the “used” heading is in
kbytes when the -k option is used. All system disk slices shown in the df
command output should be backed up, with the exception of swap. Swap
does not need to be backed up because it contains temporary data.
Vista de pagina 143
1 2 ... 139 140 141 142 143 144 145 146 147 148 149 ... 187 188

Comentarios a estos manuales

Sin comentarios