How to deal with date changing for test purposes
Posted: Wed Dec 16, 2009 11:40 am
One of my computers is used to test a time driven program. To test this, the system date is changed to varying dates in the future (e/g 6, 11 and 18 January 2010). To make it more complicated, the test may be repeated, so the system date may be set to 6,11,18 January again.
Currently the 'Backup files modified within [Number] Days or Since Date' option in the Backup Job Settings is set to 'All'
Questions:
a) Which method is used to determine if a file has been modified? Date/time of last change, or e/g a CRC of the file? If date/time, does a file with an older date of last change on disk (compared to the previous backup) count as modified, or only if it has a newer date/time of last change?
b) when testing is all complete, and the system date has been set to the current date/time again, what is the recommended method to make sure the backup will keep in sync again?
MTIA
Currently the 'Backup files modified within [Number] Days or Since Date' option in the Backup Job Settings is set to 'All'
Questions:
a) Which method is used to determine if a file has been modified? Date/time of last change, or e/g a CRC of the file? If date/time, does a file with an older date of last change on disk (compared to the previous backup) count as modified, or only if it has a newer date/time of last change?
b) when testing is all complete, and the system date has been set to the current date/time again, what is the recommended method to make sure the backup will keep in sync again?
MTIA