HP Archive Backup System for OpenVMS Guide to Operations
HP Archive Backup System for OpenVMS Guide to Operations HP Archive Backup System for OpenVMS Guide to Operations
Troubleshooting 12.6 RDF (Remote Device Facility) The value of the block length is specified to the underlying gtar backup engine as a blocking factor. The blocking factor is defined as a multiple of 512 bytes. The default block length passed to gtar is “-b20”. To determine an appropriate blocking factor or block length for a specific situation, follow these steps: Step 1. Divide the size of the disk (in bytes) by 99999 Step 2. Divide the resulting number by 512 Step 3. Round up to the next whole number For example, if the disk size is approximately 30,000,000,000 bytes (30 GB), use the following formula: 30,000,000,000 / 999999 / 512 = 58.59 or 59 This results in a blocking factor of “-b59”. You can modify the default block length from the GUI for Windows or UNIX save or restore request on the Agent Qualifiers window. Specify this value in the Agent Qualifiers window. Restriction: ABS will not produce the correct results if the value exceeds “-b127”. If the disk is large enough to exceed this amount, create more than one save request for that particular disk. To modify the blocking factor, use the procedure described in Table 12–2. Table 12–2 Modifying the Blocking Factor using MDMSview GUI Step Action 1. Invoke MDMSview GUI 2. Click Objects tab 12.5.6 Files Larger than 2gb 3. Select Selection Object either from the Tree or the Right panel. 4. Click on the appropriate Selection Name. 5. The attributes screen of the selected Selection Object is displayed on the right panel. 6. Enter the required Blocking Factor value in the Agent Qualifiers option's Text box. 7. Click Set Button, to update the changes made to the selected Selection Object. Restore requirement: When restoring data from a save request where the blocking factor has been modified, you must specify the same blocking factor that was specified on the save request. Otherwise, the restore request will fail due to an invalid block size on the tape. As a default, ABS uses 10240. If you are attempting to backup files larger than 2gb on a Windows or Unix system, you may received errors indicating that the file was not saved. The Windows gtar image we provide is not able to backup these files. 12.6RDF (Remote Device Facility) When errors occur with RDF (RDEV) devices, you should check your RDF setup and log files in the directories pointed to by the logical names TTI_RDEV and TTI_RDF. There are log files called RDCLIENT_.LOG and RDSERVER_.LOG. Also see the RDF documen- 12-10 Troubleshooting
Troubleshooting 12.7 Information Required When Reporting Problems taion and the chapter about Remote Devices in the ABS Guide to Operations for more information. 12.7Information Required When Reporting Problems If you report a problem to your HPsupport organization, the following information should be included. • If the problem is related to a save request: – MDMS SHOW SAVE/SELECTIONS save – MDMS SHOW ARCHIVE archive – MDMS SHOW ENVIRONMENT environment – MDMS SHOW SCHEDULE schedule – The log file of the save request • If the problem is related to a restore request: – MDMS SHOW RESTORE/SELECTIONS restore – MDMS SHOW ARCHIVE archive – MDMS SHOW ENVIRONMENT environment – MDMS SHOW SCHEDULE schedule – The log file of the restore request – The log file for a corresponding save request which saved the data – MDMS SHOW CATALOG/FILES of the data being requested in the restore request • If the problem is related to MDMS: – MDMS SHOW output of the related volumes, drives, etc – Output from OPCOM messages issued by MDMS – Pertinent information from the MDMS server log • If the problem is related to the MDMSView GUI – GUI version – Steps taken to reproduce the error – Error message(s) – MDMSView Log Screen information – Java version – MDMS Command Window information • Other information may be required, but will be addressed as needed. Troubleshooting 12–11
- Page 141: Remote Devices 8.7 RDF Error Messag
- Page 144 and 145: System Backup to Tape for Oracle Da
- Page 146 and 147: System Backup to Tape for Oracle Da
- Page 148 and 149: System Backup to Tape for Oracle Da
- Page 150 and 151: System Backup to Tape for Oracle Da
- Page 152 and 153: System Backup to Tape for Oracle Da
- Page 154 and 155: System Backup to Tape for Oracle Da
- Page 156 and 157: System Backup to Tape for Oracle Da
- Page 158 and 159: System Backup to Tape for Oracle Da
- Page 160 and 161: System Backup to Tape for Oracle Da
- Page 162 and 163: System Backup to Tape for Oracle Da
- Page 164 and 165: System Backup to Tape for Oracle Da
- Page 166 and 167: System Backup to Tape for Oracle Da
- Page 168 and 169: System Backup to Tape for Oracle Da
- Page 170 and 171: System Backup to Tape for Oracle Da
- Page 172 and 173: System Backup to Tape for Oracle Da
- Page 174 and 175: Virtual Library System (VLS) 10.3 Q
- Page 176 and 177: Architecture 11.1 The Server Proces
- Page 178 and 179: Architecture 11.2 Scheduler Interfa
- Page 180 and 181: Architecture 11.3 Catalogs Example
- Page 182 and 183: Architecture 11.4 Coordinator 11.4.
- Page 184 and 185: Troubleshooting 12.2 Media Manageme
- Page 186 and 187: Troubleshooting 12.2 Media Manageme
- Page 188 and 189: Troubleshooting 12.4 ABS Catalogs 1
- Page 190 and 191: Troubleshooting 12.5 Windows and Un
- Page 195 and 196: A Configuration Example Getting ABS
- Page 197 and 198: Configuration Example * Magazine -
- Page 199 and 200: Configuration Example Configuring s
- Page 201 and 202: Configuration Example If you comple
- Page 203 and 204: Configuration Example Assist: YES C
- Page 205 and 206: B Migrating from SLS/MDMS V2.X to A
- Page 207 and 208: Migrating from SLS/MDMS V2.X to ABS
- Page 209 and 210: Table B-1 SBK Symbols in ABS Termin
- Page 211 and 212: Migrating from SLS/MDMS V2.X to ABS
- Page 213 and 214: Migrating from SLS/MDMS V2.X to ABS
- Page 215 and 216: Migrating from SLS/MDMS V2.X to ABS
- Page 217 and 218: Migrating from SLS/MDMS V2.X to ABS
- Page 219 and 220: Migrating from SLS/MDMS V2.X to ABS
- Page 221 and 222: Migrating from SLS/MDMS V2.X to ABS
- Page 223 and 224: Migrating from SLS/MDMS V2.X to ABS
- Page 225 and 226: Migrating from SLS/MDMS V2.X to ABS
- Page 227 and 228: Migrating from SLS/MDMS V2.X to ABS
- Page 229 and 230: Migrating from SLS/MDMS V2.X to ABS
- Page 231 and 232: Migrating from SLS/MDMS V2.X to ABS
- Page 233 and 234: Migrating from SLS/MDMS V2.X to ABS
- Page 235 and 236: Migrating from SLS/MDMS V2.X to ABS
- Page 237 and 238: Migrating from SLS/MDMS V2.X to ABS
- Page 239 and 240: Migrating from SLS/MDMS V2.X to ABS
- Page 241 and 242: Migrating from SLS/MDMS V2.X to ABS
Troubleshooting<br />
12.7 In<strong>for</strong>mation Required When Reporting Problems<br />
taion and the chapter about Remote Devices in the ABS <strong>Guide</strong> <strong>to</strong> <strong>Operations</strong> <strong>for</strong> more in<strong>for</strong>mation.<br />
12.7In<strong>for</strong>mation Required When Reporting Problems<br />
If you report a problem <strong>to</strong> your <strong>HP</strong>support organization, the following in<strong>for</strong>mation should be<br />
included.<br />
• If the problem is related <strong>to</strong> a save request:<br />
– MDMS SHOW SAVE/SELECTIONS save<br />
– MDMS SHOW ARCHIVE archive<br />
– MDMS SHOW ENVIRONMENT environment<br />
– MDMS SHOW SCHEDULE schedule<br />
– The log file of the save request<br />
• If the problem is related <strong>to</strong> a res<strong>to</strong>re request:<br />
– MDMS SHOW RESTORE/SELECTIONS res<strong>to</strong>re<br />
– MDMS SHOW ARCHIVE archive<br />
– MDMS SHOW ENVIRONMENT environment<br />
– MDMS SHOW SCHEDULE schedule<br />
– The log file of the res<strong>to</strong>re request<br />
– The log file <strong>for</strong> a corresponding save request which saved the data<br />
– MDMS SHOW CATALOG/FILES of the data being requested in the res<strong>to</strong>re request<br />
• If the problem is related <strong>to</strong> MDMS:<br />
– MDMS SHOW output of the related volumes, drives, etc<br />
– Output from OPCOM messages issued by MDMS<br />
– Pertinent in<strong>for</strong>mation from the MDMS server log<br />
• If the problem is related <strong>to</strong> the MDMSView GUI<br />
– GUI version<br />
– Steps taken <strong>to</strong> reproduce the error<br />
– Error message(s)<br />
– MDMSView Log Screen in<strong>for</strong>mation<br />
– Java version<br />
– MDMS Command Window in<strong>for</strong>mation<br />
• Other in<strong>for</strong>mation may be required, but will be addressed as needed.<br />
Troubleshooting 12–11