This is a discussion on tar -N won't work over nfs within the Linux Networking forums, part of the Linux Forums category; hello, i'm sorry for reposting this message but i still have no idea. perhaps someone of you has a ...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
hello,
i'm sorry for reposting this message but i still have no idea. perhaps someone of you has a solution? i have a backup-script that makes incremental backups via tar -N $date. This works locally but when I try to make a backup of a nfs-mounted remote it will always result in a full backup. when I try to set $date into the future, nothing is backed up. So it seems, the file modification time is always the mount time. Is there any way to prevent this? P.S. I am using SuSE Linux 9.0 i.e. tar 1.13 and nfs 2.2 |
|
|||
|
On Thu, 22 Apr 2004 10:46:56 +0200, Martin Müller
<me@privacy.net> wrote: > hello, > > i'm sorry for reposting this message but i still have no idea. perhaps > someone of you has a solution? > > i have a backup-script that makes incremental backups via tar -N $date. This > works locally but when I try to make a backup of a nfs-mounted remote it > will always result in a full backup. > when I try to set $date into the future, nothing is backed up. > So it seems, the file modification time is always the mount time. > Is that what "ls -l" shows on the remote files? What about "ls -lc"? Try tar --newer-mtime=$date -- Giraffe: a ruminant with a view. |
|
|||
|
On Thu, 22 Apr 2004 10:46:56 +0200, Martin Müller wrote:
> i have a backup-script that makes incremental backups via tar -N $date. This > works locally but when I try to make a backup of a nfs-mounted remote it > will always result in a full backup. rsync might do a better job of this. It's designed for this. Another option ... [on NFS client, we'll call it "otherhost"] nc -p 34567 -q1 > tarfile [then on NFS server] tar -Ncf- [opts] /path-to/files | nc otherhost 34567 You could also pipe it through tar on otherhost, if you're maintaining a mirror of the files: cd /directory/of/mirror ; nc -p 34567 -q1 | tar -x [opts] I may have missed a detail or 2. Check the nc documentation if you're interested in that nifty little tool. -- /dev/rob0 - preferred_email=i$((28*28+28))@softhome.net or put "not-spam" or "/dev/rob0" in Subject header to reply |
|
|||
|
"Bill Marcum" <bmarcum@iglou.com.urgent> schrieb im Newsbeitrag news:0qlml1-k02.ln1@don.localnet... > On Thu, 22 Apr 2004 10:46:56 +0200, Martin Müller > <me@privacy.net> wrote: > > hello, > > > > i'm sorry for reposting this message but i still have no idea. perhaps > > someone of you has a solution? > > > > i have a backup-script that makes incremental backups via tar -N $date. This > > works locally but when I try to make a backup of a nfs-mounted remote it > > will always result in a full backup. > > when I try to set $date into the future, nothing is backed up. > > So it seems, the file modification time is always the mount time. > > > Is that what "ls -l" shows on the remote files? What about "ls -lc"? ls -l shows the correct dates > Try tar --newer-mtime=$date this works! What a pitty that this option is not mentioned in the tar manpage :-( thank you for your help! > > -- > Giraffe: a ruminant with a view. |
|
|||
|
In comp.os.linux.networking, Martin Müller uttered these immortal words:
>> Try tar --newer-mtime=$date > > this works! What a pitty that this option is not mentioned in the tar > manpage :-( Are you sure? At line 145 I have: --newer-mtime DATE only store files whose contents have changed after DATE -- Andy. |
|
|||
|
On Mon, 26 Apr 2004 14:48:07 +0100, Andy Fraser wrote:
>> this works! What a pitty that this option is not mentioned in the tar >> manpage :-( > > Are you sure? At line 145 I have: I think the GNU coreutils man pages are very bad. Perhaps you're using a distro which distributes a modified version of the man page. -- /dev/rob0 - preferred_email=i$((28*28+28))@softhome.net or put "not-spam" or "/dev/rob0" in Subject header to reply |
|
|||
|
In comp.os.linux.networking, /dev/rob0 uttered these immortal words:
>>> this works! What a pitty that this option is not mentioned in the tar >>> manpage :-( >> >> Are you sure? At line 145 I have: > > I think the GNU coreutils man pages are very bad. Perhaps you're using > a distro which distributes a modified version of the man page. You're right. I'm using Debian. Sometimes it's easy to forget how good Debian's documentation. To Martin: If you can't find what you want in the man page look at the info page if there is one. -- Andy. |
|
|||
|
"Andy Fraser" <andyfraser31@hotmail.com> schrieb im Newsbeitrag news:nhgvl1-qg.ln1@news.linuxuser.org.uk... > In comp.os.linux.networking, Martin Müller uttered these immortal words: > > >> Try tar --newer-mtime=$date > > > > this works! What a pitty that this option is not mentioned in the tar > > manpage :-( > > Are you sure? At line 145 I have: I doublechecked it. In the SuSE distribution manpage this option does not exist. But I could have found it with tar --help... > > --newer-mtime DATE > only store files whose contents have changed after DATE > > -- > Andy. |