Avaya Media Processing Server 500 Hardware Installation And Maintenance page 160

Maintenance
tar xvfBp -
>/opt/vps/common/log/tarx.out)
Mon Mar 15 15:00:54 2004: a ./ 0K
Mon Mar 15 15:00:54 2004: a ./lost+found/ 0K
Mon Mar 15 15:00:54 2004: a ./sadm/ 0K
.
.
.
Mon Mar 15 15:01:06 2004: x ./crash, 0 bytes, 0 tape blocks
Mon Mar 15 15:01:06 2004: x ./crash/tb020, 0 bytes, 0 tape blocks
Mon Mar 15 15:01:06 2004: Successfully tared /var to <c0t1d0s4>
You can specify two levels of logging using the -D # option on the command line.
Clone.log
The clone.log file records debug information. The logging file is created during the backup or
recovery operation. If $VPSHOME is set, the clone.log file is stored in /opt/vps/common/log/
clone.log. Otherwise, the file is located in the /tmp directory. The following is a sample clone.log file.
Mon Mar 15 14:56:55 2004: add_to_partitions: Partition </var> will be added to the
following list
Mon Mar 15 14:56:55 2004: add_to_partitions: Partition list <>
Mon Mar 15 14:56:55 2004: add_to_partitions: Partition list updated as </var>
Mon Mar 15 14:56:55 2004: grep_dir: The direct directory under root is </var> for
partition </var>
Mon Mar 15 14:56:55 2004: add_to_partitions: Partition </var> will be added to the
following list
Mon Mar 15 14:56:55 2004: add_to_partitions: Partition list <>
Mon Mar 15 14:56:55 2004: add_to_partitions: Partition list updated as </var>
Mon Mar 15 14:56:55 2004: filter_partitions_input: Existing partitions specified </var>!
Mon Mar 15 14:56:55 2004: filter_partitions_input: Valid partitions under root </var>
Mon Mar 15 14:56:55 2004: grep_dir: The direct directory under root is </var> for
partition </var>
Mon Mar 15 14:56:55 2004: get_mount_sliceID: Slice <#4> found for partition </var>
Mon Mar 15 14:56:55 2004: tar_nonrt_sli: Backup </var> on <c0t1d0s4>
Mon Mar 15 14:56:55 2004: do_mount: Successfully mounted c0t1d0s4 to /mnt/c0t1d0s4
Mon Mar 15 14:56:55 2004: tar_nonrt_sli: Current directory:/var
Mon Mar 15 14:56:55 2004: tar_nonrt_sli: This will take a little bit while to finish
Mon Mar 15 14:56:55 2004: crt_nonroot_arch: tar cvf - . 2>/opt/vps/common/log/tarc.out|
(cd /mnt/c0t1d0s4; tar xvfBp -
>/opt/vps/common/log/tarx.out)
Mon Mar 15 15:01:00 2004: wfiledat: Successfully saved operation file</opt/vps/common/log/
tarc.out> into /opt/vps/common/log/clone.dat.
Mon Mar 15 15:01:06 2004: wfiledat: Successfully saved operation file</opt/vps/common/log/
tarx.out> into /opt/vps/common/log/clone.dat.
Mon Mar 15 15:01:06 2004: crt_nonroot_arch: Successfully tared /var to <c0t1d0s4>
Mon Mar 15 15:01:23 2004: do_umount: Successfully umount file system:/mnt/c0t1d0s4
Mon Mar 15 15:01:23 2004: tar_nonrt_sli: Taring is done for </var> on <c0t1d0s4>
Mon Mar 15 15:01:23 2004: main: Successfully backuped file system:c0t0d0 to c0t1d0. Done!
Mon Mar 15 15:01:23 2004: write_cfg: Created
/opt/vps/common/etc/clone.cfg containing backup/system drives and partitions's info.
You can set four levels of logging using the -L # option on the command line.
Saving Old Log Files
When the size of a log file exceeds 1,000 KB, the clone.pl script saves the file to file.date. If a file
called file.date exists, then the current file.date is renamed as file.date.old and the new file is saved
as file.date. New logging files are created for future use.
Avaya Media Processing Server 500 Hardware Installation and Maintenance
160
Comments? infodev@avaya.com
October 2014