Not that sure that this archive attribute of the file system in Linux is that simple, used for backups and cleared or not, it is in windows, since they use an archive bithttp://www.netadmintools.com/art399.html
The ext2 filesystem on GNU/Linux does not have an archive bit, but it does have three different time stamps (creation, modification, and access) that can be used to work around this. The problem, though, is you need an extra process to make decisions on this. Samba works around this by tweaking the owner bits on ext2.http://www.adsm.org/lists/html/Networke ... 00231.html
Linux/Unix does not have an archive bit, so a Linux client cannot reset it. On Unix clients the backups is performed based on comparing the date of the last successful back at the relevant level and the 'last modified date' in the files inode (also see my letter about the Linux bug with the open (O_CREATE) system call which does not modify mtime, just ctime).
Maybe the reason it is there is due to Samba (CIFS) being included in the default installation of Ubuntu, Mint