Renaming source causes data vulnerability with mirroring?

[jeff-k]

Hello,

I am evaluating VV Pro 2 and it seems like there is a data vulnerability using the tool as backup. If source file(s) are renamed, then during the mirror operation all the pre-renamed files on the target are deleted, then the renamed files are copied to the target. This leaves a potentially large amount of time when there is no copy of the files on the backup/target drive. Is there some way to change execution order so new/changed files are copied prior to deleting?

Thanks

[TGRMN Software]

Hello

you can use the ViceVersa file archiving feature http://www.tgrmn.com/web/kb/item22.htm to move target files to a special folder instead of deleting them. You can keep these archive files for a specified time you can select.

thanks
_________________
--
TGRMN Software Support
http://www.tgrmn.com
http://www.compareandmerge.com

[jeff-k]

Using the archive feature is not a good solution - would result in massive waste of disk space. I assume since you suggest it that VV doesn't have tha ablilty to do copies prior to deletes?

[TGRMN Software]

No, that is not possible currently, unless you run 2 profiles in sequence using VVEngine http://www.tgrmn.com/web/vvengine/vvengine.htm :
the first profile performs a replication (that does not delete target files), the second a full backup / mirroring (which does delete target files that are no longer in source).
_________________
--
TGRMN Software Support
http://www.tgrmn.com
http://www.compareandmerge.com