Unsolved
This post is more than 5 years old
3 Posts
0
234
January 29th, 2007 15:00
Specifications Question
Hello,
Is there any performance concerns with having multiple specifications on a single source going to a single target?
For instance, if I have d:\folder1 and d:\folder2 is there any performance considerations if I have them both included in one specification, or if they were each in their own specification?
My real world scenario might be 50 specifications vs 1. I have folders for different customers which will all have the same specifications options, I just am not sure if it makes sense to separate them or not. I currently have them defined in a Group Specification, which allows me to deal with them individually.
Thanks.
Chuck.
Is there any performance concerns with having multiple specifications on a single source going to a single target?
For instance, if I have d:\folder1 and d:\folder2 is there any performance considerations if I have them both included in one specification, or if they were each in their own specification?
My real world scenario might be 50 specifications vs 1. I have folders for different customers which will all have the same specifications options, I just am not sure if it makes sense to separate them or not. I currently have them defined in a Group Specification, which allows me to deal with them individually.
Thanks.
Chuck.
0 events found
No Events found!
tribicic
157 Posts
0
January 31st, 2007 00:00
- in case you need to resynchronize, you won't need to do it with the complete volume, but only with the folder that went out of sync.
- during the sync, you can start syncing several specifications at once in parallel, which cannot be done if you have only one.
It is also more flexible from the management point....