| Author |
Message |
Bart
Joined: 20 Mar 2009
Posts: 4
|
 Posted: Wed Mar 25, 2009 10:44 am Post subject: Data modified is creation time of "target" - Times |
 |
|
The date modified of some target files is the moment of creation,
this causes the following issue when using Backup (Mirror Source to Target):
These files need to be copied each time because they don't match (= newer) than their original counterparts.
This is the case for about 250.000 out of 900.000 files.
The target system (where Viceversa runs) is Windows 2003 SP2
NtfsDisableLastAccessUpdate = 0x00000000 (0)
Settings:
Comparison Type: Size and Timestamp
Method: Backup (Mirror Source to Target)
No overwrite / read-only / error confirmations
No archive for deleted/replaced source files
No archive for deleted/replaced target files
Speed: 100 Buffer Size: 65536
Copy files even if timestamp changes after initial comparison
Copy directly to destination file (do not use a temporary file)
Try to copy files that are in use by other applications
No empty source/target check
Replace newer target files with older source files (backup only) |
|
| Back to top |
|
 |
TGRMN Software
Site Admin
Joined: 10 Jan 2005
Posts: 8759
|
|
| Back to top |
|
|
Bart
Joined: 20 Mar 2009
Posts: 4
|
| Posted: Wed Mar 25, 2009 2:47 pm Post subject: |
|
|
| A profile log was mailed to support@tgrmn.com. |
|
| Back to top |
|
|
Guest
|
| Posted: Wed Mar 25, 2009 10:36 pm Post subject: Re: Data modified is creation time of "target" - T |
|
|
| Bart wrote: | The date modified of some target files is the moment of creation,
this causes the following issue when using Backup (Mirror Source to Target):
These files need to be copied each time because they don't match (= newer) than their original counterparts.
This is the case for about 250.000 out of 900.000 files.
|
I observed the same. this issue comes up, if you have a large amount of
files and there is a long time between scan source and scan target and if you have set in advanced option: Copy files even file stamps ...
If you perform a second replication, this warning is coming up, that target is newer than source.
Fact is, that date/time are different from source to target. Same is with replicated directories. I would it prefere, that files /directories in target become the same date/time from copied source. |
|
| Back to top |
|
|
Bart
Joined: 20 Mar 2009
Posts: 4
|
| Posted: Thu Mar 26, 2009 9:59 am Post subject: |
|
|
After your post I retried it with a smaller selection (27.000 files) which take just 20 minutes to compare and backup completely. Alas, that failed as well,
failure as in that the timestamps of the written files is the current time and date instead of the original file date.
e.g. some of the original files are date 12-03-2006 10:23, but the copied files are dated (current time) 26-03-2009 17:31.
Last edited by Bart on Thu Mar 26, 2009 4:32 pm; edited 1 time in total |
|
| Back to top |
|
|
Bart
Joined: 20 Mar 2009
Posts: 4
|
| Posted: Thu Mar 26, 2009 11:37 am Post subject: File size |
|
|
Also there seems to be a file size limit around 8GB,
just noticed it said [Can not read data. Insufficient system resources exist to complete the requested service.].
This was while copying a 16GB file (VMware disk file), but that issue is less relevant at the moment.
This also happened when using xcopy /z on Windows, I have now increased the swapfile size and moved it to a different disk to help accommodate more temp/swap space. |
|
| Back to top |
|
|
|
ViceVersa HOME 
Forum FAQ
Search Forum
Register
Profile
Log in
