To create a debug file when running Edge...
There are several files that sometimes produce verify errors. These files don't need to be backed up.
Note: If the path name varies for a file because of different versions of Linux, you only need to enter the file name and not the full path to exclude it.
The following should be added to /etc/edge.exclude...
When using a FSP device, i.e USB drive, the following parameters can control how the archives are named and replaced. The parameters are entered in the slot name field and are separated by a period.
| Code |
Description |
Comments/Suggestions |
| 0 |
Complete success |
|
| 1 |
Error in command usage. |
A script used to start a backup process has an illegal command or syntax |
| 2 |
Misc error |
|
| 3 |
Can't read from media |
Possible causes are bad media, drive needs cleaning, tape drive failure |
| 4 |
Can't write to media |
Possible causes are bad media, drive needs cleaning, tape drive failure |
| 5 |
Accessing File/Device - Media drive failure |
Possible bad connection or termination. Click for more info |
| 6 |
Can't read from disk |
Usually caused by bad spot on disk drive |
| 7 |
Can't write to disk |
Usually caused by bad spot on drive or drive is full |
| 8 |
Not enough memory |
Need to stop other processes to free up memory |
| 9 |
Error number no longer used |
|
| 10 |
Header block of file is bad |
Damaged file |
| 11 |
Process interrupted |
|
| 12 |
Seek error |
Make sure Device supports random access. Tape drives never support seek |
| 13 |
Verify error |
File on media doesn't match file on disk |
| 14 |
Byte verify |
File on media doesn't match file on disk |
| 15 |
Incomplete |
Process did not finish |
| 16 & 17 |
Error number no longer used |
|
| 18* |
Double buffering failed |
|
| 20 |
Can't open a tmp database |
File system may be full |
| 21 |
Can't open archive database |
Permission issue |
| 22* |
Can't run some external program |
|
| 23 |
Can't open Resource |
Check the device nodes in Resource Manager for spelling |
| 24 |
Action requires a labeled tape |
|
| 25 |
End-of-medium found unexpectedly |
|
| 26 |
Fast File restore error |
Try using normal operation |
| 27 |
Max path length of 400 characters exceeded |
|
| 28 |
File not found |
|
| 29 |
Block size error |
Check Resource Manager |
| 30* |
Low-level SCSI control failed |
|
| 31 |
Usually caused by trying to erase write protected media |
|
| 32 |
Unable to scan an autoloader |
(same as 48) |
| 33 |
Can't change media in autoloader |
|
| 34 |
No media found |
|
| 35 |
Can't sense data |
|
| 36 |
SCSI error |
Try using edge.tape -t resource name for more info |
| 37 |
Can't determine basic Device parameters |
|
| 38 |
Unable to erase media |
|
| 39 |
Unable to set Device parameters |
|
| 40 |
Unable to partition tape |
Most likely size is too big |
| 41 |
Attempted operation not supported |
|
| 42 |
Unable to use Fast File restore |
|
| 43* |
Licensing error |
|
| 44* |
Internal error |
|
| 45 |
File /usr/lib/edge/config/devices.def is missing or corrupt |
Run EDGE.TAPE to provide more info |
| 46 |
Media is write-protected |
|
| 47 |
Can't open EDGE.EMX in x-windows |
|
| 48 |
Can't scan auto changer |
(same as 32) |
| 49 |
Can't perform an append operation |
|
| 50 |
Write failure |
Most likely full file system or bad media |
| 51 |
Tried to unload media that is not removable |
|
| 52 |
Can't create a named pipe |
Make sure /usr/lib/edge/system/pipes exist |
| 53 |
Encountered failure during start-up before any data is actually transferred |
|
| 54 |
External script failed |
|
| 55 |
Can't load media on auto changer |
|
| 56 |
Remote machine could not be contacted |
Try edgemenu -ping machinename |
| 57 |
System name has changed |
|
| 58* |
Can't create token file that describes aspects of system configuration |
|
| 59* |
Can't find correct command to write to a Device
|
|
| 60 |
Error closing optical media, such as CD-R |
May be bad media |
| 61* |
Indexing error during Verify |
|
| 105 |
Archive device could not be opened |
|
| 106 |
File on hard drive could not be opened |
|
| 107 |
OS reports error that is not covered by some other error number |
|
| 108* |
Detected an internal inconsistency |
|
| 109 |
Operation error not covered by another error number |
|
| 110 |
End of medium encountered |
|
| 111* |
Double buffering detected an error |
|
| 112 |
Incorrect password for encrypted archive |
|
| 113 |
End of archive encountered |
|
| 114 |
Information warning |
Not an error |
| 115 |
Data pipeline used internally has shutdown early |
|
| 116 |
Data on archive can't be read |
|
| 117* |
Callback subsystem has reported an error |
|
| 118 |
When using pipe compression, ran out of space |
Use streaming compression instead |
| 119 |
Compress/decompress error |
May be corrupt data on archive |
| 120, 121, 123 |
Can't locate position on media |
|
| 122 |
User doesn't have permission |
|
| 124 |
Can't send data over a network |
|
| 125 |
Data filter reported an error |
|
| 126 |
Random number generator detected an error |
|
| 127 |
Unable to lock a file during backup |
|
An error 5 generated during a Backup EDGE process usually means some type of hardware problem.
SOLUTION: The corrective measures would include...
This is going to be a "Process of Elimination", starting with the obvious.
1. Be certain the tape isn't write protected.
2. Be sure of power to the drive.
3. Clean the heads on the tape drive.
4. Use a brand new tape.
5. Be logged in as 'root'.
Assuming none of the above solves the problem after performing a Master backup then we will proceed with more tests.
How much data gets written to the tape before the process fails? If there is only a few files written before the error, then it is possible nothing gets written to the tape and the files are in memory.
If, for example, you are able to write 100MB to the tape before an error, then we must see if the problem is the file or directory that displays at around 100Mb. Assuming the error is consistent at occurring at 100Mb.
6. Do a selective backup of JUST the directory where the error occurs.
If this is successful, then the file where the error occurred is not the problem. If it does fail on this same directory, take the tape drive out of the scenario. Meaning write an archive to a data file rather to the tape device.
For example: This is the file that seems to fail: /usr/meddata/html/index.html
Back it up to a file name using the following command...
tar cvbf 20 /tmp/junk.tar /usr/meddata/html.
Notice we took edge out of the picture also, in the event you have to contact a hardware vendor, they will not be able to pass it back to Backup EDGE. Also we backed up the entire directory '/usr/meddata/html' and not just the single file index.html.
If this is successful use Backup EDGE to bit level the archive.
edge TTvbf 20 /tmp/junk.tar
If this is successful, then the problem points back to the chain of hardware related to the tape drive.
Remember to remove /tmp/junk.tar. If this fails, then your problem is not specific to the tape drive, and points more to the controller or cabling (including termination).
7. If number 6 is successful, and the tape consistently dies at the same spot( ex:100Mb), then the problem points more towards the drive heads, or ribbon cable.
8. Replace the ribbon cable first. Least expensive, most overlooked.
9. Replace the tape drive
10. Replace the controller.
Remember the driver is reporting errors to the kernel. Try to get tar to fail also to convince yourself of a hardware issue.
Attempt a complete tar archive, log in as root and type:
tar -cvf /dev/rStp0
Allow this to run, if this command fails, it too will generate an error.
Business Info 