<?xml version="1.0" encoding="iso-8859-1"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0">
<channel>
<atom:link xmlns:atom="http://www.w3.org/2005/Atom" rel="hub" href="https://pubsubhubbub.appspot.com/" />
<atom:link xmlns:atom="http://www.w3.org/2005/Atom" type="application/rss+xml" rel="self" href="http://backupforum.progforums.com/BackupForum/rss.php?tid=181" /> 
<title>Backup forum : IDrive : Common Room : Changes that trigger a backup on a linux host</title>
<link>https://backupforum.progforums.com/BackupForum</link>
<description> Backup forum</description>
<language>en</language>
<docs>http://backend.userland.com/rss</docs>
<item>
<title>Changes that trigger a backup on a linux host in IDrive : Common Room</title>
<link>https://backupforum.progforums.com/BackupForum/viewtopic.php?pid=707#p707</link>
<guid isPermaLink="false">707@https://backupforum.progforums.com/BackupForum</guid>
<description>Topic: Changes that trigger a backup on a linux host

Message: Thanks for posting your findings.
</description>
<pubDate>Wed, 01 Jun 2022 23:48:30 +0100</pubDate>
</item>
<item>
<title>Changes that trigger a backup on a linux host in IDrive : Common Room</title>
<link>https://backupforum.progforums.com/BackupForum/viewtopic.php?pid=706#p706</link>
<guid isPermaLink="false">706@https://backupforum.progforums.com/BackupForum</guid>
<description>Topic: Changes that trigger a backup on a linux host

Message: In my previous post, I was asking about some things that would trigger a backup to occur on a linux host.&#160; So, here's a list of the tests that I ran:Things that did NOT trigger a backup:1) Changing permissions2) Changing ownership3) Changing inode(I'm really happy about #3... that means I can move files to a new disk and, provide all the paths stay the same, they will not get backed up again)Things that DID trigger a backup1) Changing the timestamp (either forwards or backwards)2) Changing the file size (even if you force the timestamp to be unchanged)3) Changing the file in a way that keeps the same sizeI tested moving timestamps backwards to simulate if you placed an older copy of the file in place.&#160; So, ANY timestamp change triggers a backup, even if you do not modify the file.Also, I did want to make sure that the backup wasn't triggered just on the file size, so I did a set of modifications that kept the same file size, and as expected, they triggered a backup.&#160; That was probably just being a bit paranoid, but just wanted to be sure.So, it's a reasonable backup solution for linux provided you're basically a single user.Trying to do system-level backups is probably not great because:o&#160; It doesn't handle permissions and ownerships at all (which renders it virtually useless for a system-level install)o&#160; It doesn't handle symlinks correctly (they should be backed up as a symlink, NOT as a file/directory that the link points ato&#160; I assume that it probably doesn't handle other types of special files (hard links, semaphores, sockets, etc.) though I didn't test them out.All in all, I'm happy to use it as a user-level backup solution.
</description>
<pubDate>Wed, 01 Jun 2022 23:03:51 +0100</pubDate>
</item>
</channel>
</rss>
