Yeah - I'd agree with Paul here. Naming a file "core" is not smart.
There's no "fix" to this coming because, frankly, it ain't broken.
Excludes are by name only, NB can't tell a true core file from a file named
"core".
-M
-----Original Message-----
From: veritas-bu-admin < at > mailman.eng.auburn.edu
[mailto:veritas-bu-admin < at > mailman.eng.auburn.edu]On Behalf Of Paul
Keating
Sent: Wednesday, January 19, 2005 12:10 PM
To: veritas-bu < at > mailman.eng.auburn.edu
Subject: RE: [Veritas-bu] Does anyone use file excludes - careful about
using "core"
I once (in a previous life) had a restore request from a user for /tmp,
which we didn't back up for obvious enough reasons.
Anyhow, this person had been storing files in /tmp for months, untill
one fine day the system was rebooted for maintainance, and all of his
hard work dissappeared.
Sometimes it technical, and sometimes it's user education.
Paul
-----Original Message-----
From: veritas-bu-admin < at > mailman.eng.auburn.edu
[mailto:veritas-bu-admin < at > mailman.eng.auburn.edu] On Behalf Of
William David Phillips
Sent: January 19, 2005 1:59 PM
To: veritas-bu < at > mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Does anyone use file excludes -
careful about using "core"
On restoring a partition we discovered that all files and directories
named core were not backed up. It had nothing to do with the
file being
a core file. Only explicitly exclude core files with a known
path and
name unless you are certain none of your users will ever use the name
core. I don't know if this is fixed in a later release.
David
