|This article does not cite any references or sources. (August 2009)|
On Windows and OS/2, when a file is created or modified, the archive bit is set, and when the file has been backed up, the archive bit is cleared. It is by use of the archive bit that incremental backups are implemented.
Backup software also provides the option to do a full backup while clearing archive bits - that is, to back up all files regardless of their archive bit status, and to clear the archive bit of all files processed by the backup. This allows for the creation of an initial full backup that will be supplemented by incremental backups in the future.
The operating system never clears the archive bit on its own, unless explicitly told to do so by the user. In MS-DOS as well as nearly all versions of Windows, the archive bit can be seen or changed with the attrib command-line utility, or by viewing the properties of a given file with the Windows shell. The archive bit can also be seen or changed with the GetFileAttributes, GetFileAttributesEx and SetFileAttributes Windows APIs.
When a file with a clear archive bit is moved from one place on a file system to another, the archive bit reverts to being set.
Typically, on a computer system that has never been backed up in a manner that clears archive bits, all files on that computer will have their archive bits set, as there are few applications that make use of archive bits without the user's request.
As the archive bit is a file attribute and not part of the file itself, the contents of the file are unrelated to the status of the archive bit and remain unchanged even if the setting of the archive bit is changed.
Relying on the archive bit for backing up files can be unreliable if multiple backup programs are setting and clearing the attribute bit on the same volume. Another possibility is to use the time stamp of the last change to the file or directory.