•Do not replace newer files with older files: If ticked then new files are not overwritten (replaced) by older files. This option is only available under certain conditions.
•Ignore file modification date & time changes (not recommended): You can tell SyncBackPro to ignore changes to the last modification date & time of a file. Note that this option is not available if your profile is an Intelligent Synchronization profile.
•Ignore directory modification date & time changes: You can tell SyncBackPro to ignore changes to the last modification date & time of directories. It is recommended that you leave this at the default setting, i.e. ignore. If changes are not ignored then SyncBackPro will change the opposite directories last modification date & time to match. Which side is changed depends on what is set on the Decisions, Folders settings page. However, keep in mind that Windows will automatically change the last modification date & time of a directory if any of its files or sub-directories are changed, with a change being anything at all, e.g. changing a sub-directories last modification date & time. This means every time you run a profile if anything is changed then the dates & times will be changed by Windows.
•Ignore creation date & time changes: You can tell SyncBackPro to ignore changes to the creation date & time of files and directories. If you change this option so that you are not ignoring creation date & time changes then you should enable the option to copy create date & times for directories and files. For SFTP the creation date & time may be reported as the same as the modification date & time. For FTP the server must support the retrieval (and maybe setting) of creation dates and times. Many do not.
•Ignore file date & time changes that are because of Daylight Savings Time (DST) changes: By default if the last modification or creation date & time is exactly one hour different then it is ignored. This avoids problems with changes in the time due to Daylight Savings Time.
•Ignore last access date & time changes: You can tell SyncBackPro to ignore changes to the last access date & time of files and directories. The default is to ignore changes and it is not recommended you disable it unless you require it. If you change this option so that you are not ignoring last access date & time changes then you should enable the option to copy last access date & times for directories and files. Most file systems do not support last access dates and times. NTFS does, but it may not be implemented, e.g. many NAS devices will not. For SFTP and FTP, it is highly unlikely that the SFTP/FTP server supports the retrieval of the last access date & time.
•Ignore date & time changes of x seconds or less (differences are rounded down to nearest second): In some situations, the file system itself may not accurately record the correct date & time when a file or directory was last modified or created. This can occur when using SAMBA shares (e.g. on NAS devices) and FAT formatted file systems. With this option, you can tell SyncBackPro to ignore small differences in the date & times, e.g. ignore differences of 2 seconds or less. Note that the difference is rounded down to the nearest second, so a difference of 2.99 seconds is treated as 2 seconds. To avoid inaccuracies in file systems, and differences between file systems, SyncBackPro will ignore differences of 2 seconds by default. You can of course change this if you require finer accuracy. Keep in mind that Google Docs files stored on Google Drive do not record milli-seconds, so setting that value to zero may cause issues.
•Ignore files that have/have not been modified…: This setting allows you to ignore files that were modified within a certain date range, e.g. within the last x days, since a date and time or between two dates and times (inclusive). Note that it uses the files last modification date & time and not the file creation date & time. See the section below for more details. If you wanted to ignore all files the have been modified before a certain date you'd set it to Ignore files that have not been modified since [date]. If you wanted to ignore all files that have been modified after a certain date you'd set it to Ignore files that have been modified since [date]. If you wanted to ignore all files that have not been modified in a certain time period you'd set it to Ignore files that have not been modified between date1 and date2.
•Ignore files that have/have not been created…: This setting allows you to ignore files that were created within a certain date range, e.g. within the last x days, since a date and time or between two dates and times (inclusive). Note that it uses the files creation date & time and not the last modification date & time. See the section below for more details. Keep in mind that some locations, e.g. FTP, may not store the creation date & time of a file.
•Ignore files that have/have not been accessed…: This setting allows you to ignore files that were last accessed within a certain date range, e.g. within the last x days, since a date and time or between two dates and times (inclusive). See the section below for more details. Most file systems do not support last access dates and times. NTFS does, but it may not be implemented, e.g. many NAS devices will not. For SFTP and FTP, it is highly unlikely that the SFTP/FTP server supports the retrieval of the last access date & time.
|
The Ignore files that have/have not… settings above may not work as you expect it when using the within the last option. The following explains how the date & time comparison works:
Seconds: Fractional seconds do not count. For example, if a file was modified 30.5 seconds ago, and you want to ignore files that have been modified within the last 30 seconds, then it will ignore the file, i.e. 30.5 seconds is treated as 30 seconds (it is not rounded up).
Minutes: Fractional minutes do not count. For example, if a file was modified 2 minutes and 31 seconds ago, and you want to ignore files that have been modified within the last 2 minutes, then it will ignore the file, i.e. the seconds are not used in the comparison.
Hours: Fractional hours do not count. For example, if a file was modified 2 hours, 31 minutes, and 32 seconds ago, and you want to ignore files that have been modified within the last 2 hours, then it will ignore the file, i.e. the minutes and seconds are not used in the comparison.
Days: Fractional days do not count. For example, if a file was modified 2 days, 13 hours, 31 minutes, and 32 seconds ago, and you want to ignore files that have been modified within the last 2 days, then it will ignore the file, i.e. the hours, minutes, and seconds are not used in the comparison.
Weeks: Fractional weeks do not count. For example, if a file was modified 2 weeks, 4 days, 13 hours, 31 minutes, and 32 seconds ago, and you want to ignore files that have been modified within the last 2 weeks, then it will ignore the file, i.e. the days, hours, minutes, and seconds are not used in the comparison.
Months: Because months are not all the same length, SyncBackPro assumes there are 30.4375 days per month. Also, fractional months do not count. For example, if a file was modified 2 months, 3 weeks, 4 days, 13 hours, 31 minutes, and 32 seconds ago, and you want to ignore files that have been modified within the last 2 months, then it will ignore the file, i.e. the weeks, days, hours, minutes, and seconds are not used in the comparison.
Years: Because years are not all the same length (e.g. leap years), SyncBackPro assumes of 365.25 days per year. Also, fractional years do not count. For example, if a file was modified 2 years, 7 months, 3 weeks, 4 days, 13 hours, 31 minutes, and 32 seconds ago, and you want to ignore files that have been modified within the last 2 years, then it will ignore the file, i.e. the months, weeks, days, hours, minutes, and seconds are not used in the comparison. |
All Content: 2BrightSparks Pte Ltd © 2003-2024