David Hendrix wrote:
( If an HP-UX system loses a
filesystem due to a disk failure, it is the sys admin's job to have
monitors in place to detect and prevent extended loss/outage.
...
ADSM's job is to backup client machines, not perform SA duties.
)
While your thoughts looks good,
While your thoughts looks good,
there is another viewing perspective, too.
- your logic fails as soon as disk failure occures during
or short before DSMC INCR.
In this case, you will not be able to "know about it long before
any backup process happens".
- your conclusion also fails in installations, where
backups are scheduled for night ours but there is no
personal available in the night, or no knowledgable personal.
- ADSM INCR will not only expire files from disks in failure state,
but files from innaccessible disks in general.
Consider for example a configuration
with hundreds or thousands of OS2 clients.
You will probaly not monitor
which node locked which file system - there is normally no
need to do so because file system
locked by an application is NOT in a failure state.
In another words:
DSMC will not expire files which cannot be backed up
because they are locked during backup, but it will
expire files which are on locked file systems.
Juraj Salak
sal AT keba.co DOT at
|