From: Steve Crawford <scrawford@pinpointresearch.com>
To: Pallav Kalva <pkalva@livedatagroup.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Archive Command Configuration
Date: Thu, 23 Mar 2006 13:21:12 -0800
Message-ID: <44231148.4040804@pinpointresearch.com> (raw)
In-Reply-To: <44230BBC.7080406@livedatagroup.com>
References: <4422FD80.5080009@livedatagroup.com>
<442304F9.4090708@pinpointresearch.com>
<44230BBC.7080406@livedatagroup.com>
> Hi Steve,
>
> Thanks! for the quick reply, I thought about rsync too, but wasnt
> sure about completely how it handles partial files. I use rsync for all
> the backups, it works fine for all the application except for our mail
> application it copies the files but at the end of the job it gives me
> message like
>
> ------------------------------------------------------------------------------------
>
> send_files failed to open //this/file/ : No such file or directory
>
> rsync error: some files could not be transferred (code 23) at main.c(1158)
> ------------------------------------------------------------------------------------
>
>
> Considering it is copying all our mail messages and it takes a lot of
> time to rsync the whole thing, there might be changes to the file or
> file gets deleted completely from time it gets the files to rsync and do
> the actual rsync.
Not to worry. I see this from time to time as well. Rsync builds a list
of files to sync and then syncs them. If a file is deleted between the
time rsync builds the list and when it tries to process that file, it
will return that error.
BTW, if you haven't done so already, check out version 2.6.7 released a
week or so ago. There are some nice enhancements to the include/exclude
code, a --prune-empty-dirs option so when your exclude options eliminate
all the files in a directory you don't end up creating an empty
directory on the target machine, and an --append option to improve
efficiency when transferring files that are only appended to, not
changed (great for logs and such).
Cheers,
Steve
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: scrawford@pinpointresearch.com, pkalva@livedatagroup.com
Subject: Re: Archive Command Configuration
In-Reply-To: <44231148.4040804@pinpointresearch.com>
References: <4422FD80.5080009@livedatagroup.com> <442304F9.4090708@pinpointresearch.com> <44230BBC.7080406@livedatagroup.com> <44231148.4040804@pinpointresearch.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox