Do I want to choose Discard or Queue Latest? (Queue latest seems to be the default).
Ans: It's purely your call. When any new replication request comes and already one replication going on that time you need to decide what you want to do like you like to discard this new replication request or Queue it for later. Anyway the limit is only 1
Do I want a Secondary Snapshot history? If so do I need a retention snapshot history of greater than 1? Do I want to keep Primary Snapshot history? & what should be retention priority - I am guessing Never Delete would not be good option if I want to preserve disk space!
Ans: Again this is your call. you can set retention count upto 16. You need to decide if you want to keep Snapshot history both primary and seconday or secondary only. retention priority never delete not good in terms of space management.
Second last question - I am guessing that the Enable overcommitment of pool setting should be set as ON, other internal snapshots may grow & we run out of space.
Ans: Yes it's always recommended to set overcommit as enabled that means volumes will be Thin volume otherwise space management will be difficult because if overcommitment is disabled then all will be fully allocated objects
Last question - In testing scheduled replication - continually get these errors.
Scheduler: The scheduler was unable to complete the replication. - Command is taking longer to complete than anticipated. (task: du-msa-01, task type: Replicate)
Ans: It depends upon size of the volume, replication schedule. We need to give enough time between consequitive replications so that data copy should happen properly.
Hope this helps!
Regards
Subhajit
I am an HPE employee
If you feel this was helpful please click the KUDOS! thumb below!
***********************************************************************************