Unsolved
This post is more than 5 years old
2 Intern
•
125 Posts
0
500
June 26th, 2009 10:00
can i use the file on target
in admin guide, i find "Never have an application open the replicated files on the target."
two questions:
when i open the file on target for long time, will it prevent the sync operation(maybe the driver can't perform write when file is opened)?
any suggestion if i want to use file on target?
two questions:
when i open the file on target for long time, will it prevent the sync operation(maybe the driver can't perform write when file is opened)?
any suggestion if i want to use file on target?
No Events found!


dramjass
151 Posts
1
June 26th, 2009 10:00
You do have this option that can override this:
Maintenance -> Options -> Advanced -> Set Expiration Time for Open Files on Target
When this is set, it will tell RepliStor to close the target file so it can be updated.
I am not sure the reason you would need to open files ont he Target, unless you are doing testing or something. But to ensure data consistency issue do not arrise, you can always:
- Disable the Spec
- Make files changes on the Target.
- Close the file.
- Enable the Spec
- Sync the Spec
NOTE: Any changes made to the Target file will be lost.
jschrade1
2 Intern
•
106 Posts
0
August 25th, 2009 09:00
If you do not turn on Target File Protection. then RepliStor allows you to write to the files on either the Source or the Target node. However, if you make changes to the file on the Target, these changes are not generally updated on the Source node. Therefore you run the risk of losing these changes. This is a very dangerous choice and that means that you are responsible for making sure that the files are only updated on one machine and RepliStor is not aware of the updates. If you do a sync in this case, the changed files on the Target will be overwritten by the file from the Source nd the changes will be lost.
That is why the default behavior is to protect the Target's files by locking them. Make sure you fully understand the way this works by testing with non-production data before trying it with real data files. Even then, you should have a complete backup before trying any circular replication of unprotected target files.