Re: On-line backup - /bin/tar: Error exit delayed from previous

From: Andy Shellam <andy(dot)shellam-lists(at)mailnetwork(dot)co(dot)uk>
To: "Mr(dot) Dan" <bitsandbytes88(at)hotmail(dot)com>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: On-line backup - /bin/tar: Error exit delayed from previous
Date: 2006-08-03 18:59:52
Message-ID: 44D247A8.5060201@mailnetwork.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

We occasionally get the "file changed while being read" error, usually
only once or twice a month (and we run nightly backups.) It's nothing
to be concerned about, as someone else mentioned, the WAL logs will fix
any internal inconsistencies.

Regarding the file sizes, because it's zipped (I believe) the
compression ratios can change depending on the contents of the files,
hence the differences in size, but I wouldn't have thought it be that
drastic.

Thing I would do, is on a spare machine (or same one if you've got the
space), unzip three of the files that are different sizes (e.g. 874MB,
5GB, 9GB) and then compare the sizes of the unzipped data. If it
differs greatly in the same fashion, you've got a problem.

Also just double check you're not backing up WAL logs as well (i.e.
excluding pg_xlog.)

Andy.

Mr. Dan wrote:
>
> Another thing that conerns me is that the zipped file size keeps
> changing.
> I'm backing up 10GB total. One night the backup file was 9 GB, one
> night it was 874 MB and just now, 5 GB. I'm expecting a file around
> 1.5 GB (15% of the 10GB) that's there.
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: don't forget to increase your free space map settings
>
> !DSPAM:37,44d207ac143291676420085!
>
>

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Christoph Simon 2006-08-03 19:54:35 data for 64bits on 32
Previous Message Mr. Dan 2006-08-03 14:25:39 Re: On-line backup - /bin/tar: Error exit delayed from previous errors