- #BVCKUP COPYING FILES TO SOURCE FOLER UPDATE#
- #BVCKUP COPYING FILES TO SOURCE FOLER MANUAL#
- #BVCKUP COPYING FILES TO SOURCE FOLER ARCHIVE#
On a 1st attempt I changed the destination dir and set to rescan destination in order to have a "clean, initial run". That is, if need use them, use with due care.
#BVCKUP COPYING FILES TO SOURCE FOLER MANUAL#
This is where manual Ctrl-Go starts become of relevance - these will force file system re-test and will discard the override until the next program restart. This is done by adding the following override to the job's config file -įinally, keep in mind that any override is used only when the job is loaded at program's start. Now, you CAN work around this and force the copying of created timestamps. Make note of this, because it's important for the later. It is however re-tested every time the job is started manually with Go ** and the CTRL is held down **. The failure will be recorded between these two lines:įile system is tested once and the results are cached. You can get details from the file system testing log. In your case an attempt to set created time on that test file failed one way or another. The way it understands if these timestamps are supported is by creating a temporary file at each location and then running some tests with it. If the program thinks that either side doesn't support created timestamps, it doesn't clone them from source to the backup. I also found the topic about similar problem with the destination,īut in that topic I haven't found a solution about my problem. Move detection: folders, files (by name/size/times, by file ID, by fuzzy matching)
#BVCKUP COPYING FILES TO SOURCE FOLER UPDATE#
Security info: don't compare, don't update
#BVCKUP COPYING FILES TO SOURCE FOLER ARCHIVE#
> Source does not support "created" file timestampsĪttributes: read-only hidden system archive
Supported attributes : read-only, hidden, system, archive Modified granularity : 100 ns ( 100 ns probed, 100 ns deduced ) Supported attributes : hidden, system, archiveĬreated granularity : 100 ns ( 100 ns probed, 100 ns deduced ) Modified granularity : 1 sec ( 1 sec probed, 100 ns deduced ) Investigating the problem I found in the log following entries: The same scenario ran with alternative software runs OK, but the alternative has some other issues, so that Bvckup is my favorite tool by now. I tried to play arond with the recommendation from here The current result is, that c-dates are not set to their original dates but to now(). I have a test folder Source_fldr, that I want to copy to Target_fldr with preserving both c-dates and m-dates (created/modified). Both USB drive and NAS are mapped as network storage in Windows 7. USB drive is NTFS, NAS is accessed via SMB. I have a PC running Bvckup2, a Synology NAS with DSM 6.x and an USB drive attached to the NAS and exposed as a shared folder by the NAS. I am new to the forum and I am currently evaluating Bvckup2 for my new backup strategy.
0 kommentar(er)
