Client Triggered Oracle Backups
Client Triggered Oracle Backups allows Zmanda Oracle agents to trigger the backups from client using RMAN libraries while updating details...
This article helps you understand the resolution for the “Warning: Cannot stat: No such file or directory” error.
This article is for Amanda Enterprise (AE).
Issue Symptoms
Warnings:
/-- ns.example.com /var lev 0 STRANGE
sendbackup: start [ns.example.com:/var level 0]
sendbackup: info BACKUP=/bin/tar
sendbackup: info RECOVER_CMD=/bin/gzip -dc |/bin/tar -f -...
sendbackup: info COMPRESS_SUFFIX=.gz
sendbackup: info end
I gtar: ./lib/mysql/mysql.sock: socket ignored
? gtar: ./log/dcpumon/toplog. 1157611501: Warning: Cannot stat: No such file or directory
? gtar: ./log/dcpumon/toplog. 1157611801: Warning: Cannot stat: No such file or directory
? gtar: ./log/dcpumon/toplog. 1157612101: Warning: Cannot stat: No such file or directory
? gtar: ./log/dcpumon/toplog. 1157612401: Warning: Cannot stat: No such file or directory
? gtar: ./log/dcpumon/toplog. 1157612701: Warning: Cannot stat: No such file or directory
? gtar: ./log/dcpumon/toplog. 1157613001: Warning: Cannot stat: No such file or directory
? gtar: ./log/dcpumon/toplog. 1157613301: Warning: Cannot stat: No such file or directory
I gtar: ./run/ftpd.sock: socket ignored
I gtar: ./spool/authdaemon/socket: socket ignored
? gtar: ./spool/exim/input/W/1Glh9W-0000QL-Nv-D: Warning: Cannot stat: No such file or directory
? gtar: ./spool/exim/input/W/1Glh9W-0000QL-Nv-H: Warning: Cannot stat: No such file or directory
? gtar: ./spool/exim/msglog/W/1Glh9W-0000QL-Nv: Warning: Cannot stat: No such file or directory
I Total bytes written: 350013440 (334MÃB, 60KiB/s)
sendbackup: size 341810
sendbackup: end
DUMP SUMMARY:
DUMPER STATS TAPER STATS
HOSTNAME DISK L ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
ns.example /var 0 341810 189056 55.3 95:12 33.1 0:01 131347.2
Resolution
These warnings are normal when backing up any file systems like /var. Some temporary files might be present during the planning phase but expire by the time the backup starts. This causes the warnings you see above. All these warnings can be disregarded.
