similar to: rsync files with mtime

Hello List, How would i rsync all files which are older than X-Days? I am missing some kind of -mtime option. Since this is quite common for backups i am wondering how you are doing this kind of stuff. Thanks, Mario

I'm trying to clone a volume in a storage pool and I'm following the steps described here: http://libvirt.org/docs/libvirt-appdev-guide-python/en-US/html/libvirt_application_development_guide_using_python-Storage_Pools-Cloning.html My code looks like: destXML = """ <volume>

Hello I am making backup of a Plesk Debian server to /backup using Rsync. My questioin is how can I preserve the ctime, mtime, and atime of original files? Thanks

Hi Everyone, The following feature request was received by a Debian user; could you comment on it? I think this seems reasonable, but perhaps should be enabled only conditionally (as if the argument parser isn't stressed enough). Thanks, Justin On Fri, Jul 23, 2004 at 05:09:09PM -0300, Pedro Zorzenon Neto wrote: > Package: rsync > Version: 2.6.2-2 > Severity: wishlist > Tags:

https://bugzilla.samba.org/show_bug.cgi?id=13735 Bug ID: 13735 Summary: Synchronize files when the sending side has newer change times while modification times and sizes are identical on both sides Product: rsync Version: 3.1.3 Hardware: All OS: All Status: NEW

On Fri, Feb 19, 2016 at 12:12 PM, Martin Kletzander <mkletzan@redhat.com> wrote: > On Fri, Feb 19, 2016 at 11:12:32AM +0000, Andrei Perietanu wrote: > >> I'm trying to clone a volume in a storage pool and I'm following the steps >> described here: >> >>

Dear Martin Pool. We regularly use rsync for making backups of our file systems but we have noticed that the atimes are not transferred with the files and are also always updated on the sender's side. Therefore, we have created a modified version of rsync based on rsync-2.6.6 protocol version 29 which transfers the access times with the transferred files and also allows to preserve the access

I noticed that rsync is happy to hard-link a device node from a --link-dest dir even if its mtime differs from that of the source device node and --times is given. Is this behavior expected? It seems to break the rule that a difference in preserved attributes disqualifies a hard link. To see the behavior, run the following as root: mkdir src dest basis mknod src/null c 1 3 sleep 1 mknod

Often we need to preserve the information atime conveys, but I have found no way to get rsync to preserve this, nor any hint it is being worked on. It would be great if 'rsync -t' also set atime not just mtime -- or maybe a new option is desired for atime. I don't know if the -X mentioned in "NEWS file from CVS" covers this: > Added the --xattrs (-X) option to preserver

Hello, I just observed something strange: rsync -av --exclude /USER/NoBackup --exclude '*.NTX' --compare-dest=/backup/novell/vollbackup /mnt/novellserver/SYS/ /backup/novell/ziel rsync -av --exclude /USER/NoBackup --exclude '*.NTX' --compare-dest=/backup/novell/vollbackup/PUBLIC /mnt/novellserver/SYS/PUBLIC/ /backup/novell/ziel For debugging purposes (saving time) I used

I posted a patch a few days ago that adds copying of atime. At that time, it was just enabled with -t/--times. After some time, we have figured out that that choice might not have been the best. Here's a new version of the patch (relative to CVS) that adds -A/--copy-atime instead. It also includes a test case. Any feedback on this patch and/or the previous one that I posted?

Is there anyway I can get Dovecot to update mtime on dovecot.index everytime a user successfully checks there email? Or perhaps there is a better way to do what I want here. I am working on a script that I want to check when the last time a user checked there email account. If a user has not checked it in say 6 months I want to automatically suspend the account through the MTA. If they start

Greetings all- I am conducting security testing on a device that uses Linux 2.4 with ext3. I am testing secure overwrite of remnant data in temporary files, but have run into a real good stumpper in the way Ext allocates data blocks. I've got 10 yrs of *NIX behind me, several with Linux, and this has really got me perplexed as I can't find any documentation explaining the subject

Hello, This patch adds client and server support for transmitting the st_nlink field across SSH2_FXP_NAME and SSH2_FXP_ATTRS responses. Please let me know if there anything I can do to improve this patch. I am not subscribed to list so please CC me. Index: sftp-common.c =================================================================== RCS file: /cvs/src/usr.bin/ssh/sftp-common.c,v retrieving

It looks like I need to elaborate further to get a feedback. I checked the rsync source code and it is using utime() to restore atime file attribute. It is fine to change ctime for that transferred file in this case. What we are having problem is that when rsync gets kicked off and transfers one file to the destination, this action changes ctime of "all" files in the same

smbclient (and smbtar) in version 2.2.7a (and prior) has problems with large files (> 4GB). The following patch (against 2.2.7a) fixes all known problems with this. This code has been checked into the CVS tree in all branches as well. -- ====================================================================== Herb Lewis Silicon Graphics Networking Engineer

Hello, since we are using rsync for backing up millions of files in a virtual environment, and most of the virtual machines run on SSD cached storage, i`d be curious how that negatively impacts lifetime of the SSD`s when we do rsync run every night for backup my question: does rsync normal file comparison run to determine if anything has changed change atime of any files ? for me it seems,

Hi list, I have been reading MAN pages and listarchives, but not found the answer to my question though I am sure it must be possible to acheive my wish. I wish to use rsync to create a backup BUT only keep the files for a limited period of time, EG two weeks. I have not yet been able to figure out how to do this inside rsync (while the backup is being performed) and my understanding of the

I find rsync an excellent tool when I need to move multi-gigabyte filesystems, because I can do most of the copying during the week - then a quick cleanup sweep in our 4 hour outage window. I do need to somehow get the atime's to copy over, because as it stands now I loose the age information (which we will soon be using for auto-archiving) on things I copy with rsync. Would it be that hard

What are the filesystem requirements for dovecot - for example I see some people are running with atime updates switched off (as I intend to do so myself), so presumably dovecot has no need of an accurate atime implementation. How about directory atime? ctime/mtime etc? I'm intending to run on a linux box using local disk, so am currently considering using reiserfs (3.6) with noatime,