Hi Linus,
Thanks for the reply,
1. The datafile in question if only 1Gb
2. This is a low end server with 2Gb memory & the backup is scheduled to run at 4 AM when there is no memory resource crunch.
The corruption seems to be very inconsistent, 1 day the .tgz is fine, while the 2nd day, the .tgz file gets corrupted. Am planning to reschedule the .tgz backup to one of the local Mount points instead of the SAN Harddisk & then check the same.
You hv commented that "Not with the symptoms you have", does that mean that this may be one-of-the reasons for file corruption.
Thanks & Regards Girish
C. Linus Hicks wrote:
On Mon, 2004-12-20 at 09:10 +0530, Girish N wrote:
<snip>
The only thing that we were able to find is that one of the database file [out of 15 files] is in inconsistent state, does this mean that - a tar -czvf backup will fail if one of the file during backup is inconsistent [or corrupted?]
Not with the symptoms you have.
This is happening on one of our Redhat AS 3.0 server [we hv 10 Redhat dev servers & none of them r hvn'ng this issue]
the command used for backup is "# tar -czvf /SAN02/datatop.tgz /u02/datatop"
Two possibilities:
1. Has the datafile grown to a size that is problematic? I don't know specifically about the versions of tar and gzip in AS 3, some are limited to 2gb file size.
2. I wouldn't think this is very likely since it is only happening to one datafile, but could it possibly be a memory problem?
-- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list
