Xerox 6180N DocuSP Common Controller System Guide - Page 41

Backup and recovery caveats - DSPERU

Page 41 highlights

Backup and Restore NOTE: To stop the system at the ok prompt, power on the controller, then press Stop and A simultaneously as soon as the screen lights. If the system is already powered on, logon as root, then enter halt to display the ok prompt. 1. Enter mount /dev/diskette /a to mount the diskette. 2. Enter sh /a/dsp_restore to launch the recovery script. 3. If multiple tapes were used during the backup, the system pauses at the end of each tape and displays a message similar to the following: Mount volume 2 then enter volume name (default: /dev/ rmt/0bn) Insert the cassettes in sequence as the system requests them. The system reboots when the recovery is complete. NOTE: The UNIX ufsrestore utility does not provide the option for estimating how a long a recovery will take. However, the normal amount of time required for recovery is approximately 3 times as long as backing up the system. Examples: • 4mm Tape, DocuSP 2.X system, very few or no customer files: 0:20 to backup, 1:00 to restore • QIC Tape, DocuSP 6180 EPS 2.X, 500 Meg customer resource files: 1:30 to backup, 4:30 to restore • 4mm Tape, DocuSP 3.X, very few or no customer files: 45 minutes to backup, 2:15 to restore Backup and recovery caveats - DSPERU Because recovery returns the system to the state that it was in when it was last backed up, certain unexpected or undesirable situations may be encountered. A list of known issues is provided below and will be updated on a continuous basis. Where available, a workaround is provided. • Accounting logs are restored to their previous values. If you use the accounting logs for your own internal billing, you need to be aware of this and make the necessary adjustments. System Guide 2-13

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140

Backup and Restore
System Guide
2-13
NOTE:
To stop the system at the ok prompt, power on the
controller, then press Stop and A simultaneously as soon
as the screen lights.
If the system is already powered on, logon as
root
, then
enter
halt
to display the ok prompt.
1. Enter
mount /dev/diskette /a
to mount the diskette.
2. Enter
sh /a/dsp_restore
to launch the recovery script.
3.
If multiple tapes were used during the backup, the system
pauses at the end of each tape and displays a message
similar to the following:
Mount volume 2 then enter volume name (default: /dev/
rmt/0bn)
Insert the cassettes in sequence as the system requests
them.
The system reboots when the recovery is complete.
NOTE:
The UNIX ufsrestore utility does not provide the
option for estimating how a long a recovery will take.
However, the normal amount of time required for recovery is
approximately 3 times as long as backing up the system.
Examples:
4mm Tape, DocuSP 2.X system, very few or no customer
files: 0:20 to backup, 1:00 to restore
QIC Tape, DocuSP 6180 EPS 2.X, 500 Meg customer
resource files: 1:30 to backup, 4:30 to restore
4mm Tape, DocuSP 3.X, very few or no customer files: 45
minutes to backup, 2:15 to restore
Backup and recovery caveats - DSPERU
Because recovery returns the system to the state that it was
in when it was last backed up, certain unexpected or
undesirable situations may be encountered. A list of known
issues is provided below and will be updated on a continuous
basis. Where available, a workaround is provided.
Accounting logs are restored to their previous values. If
you use the accounting logs for your own internal billing,
you need to be aware of this and make the necessary
adjustments.