First, it is not necessary to have both products installed to accomplish this configuration. RepliStor can be used alone, without AutoStart, to 1) replicate data and 2) repicate share informatioin. If you choose to use both for some other reason not mentioned that is also possible.
In either case, the failover of resources can be done either manually via the GUI tools or automatically if the heartbeats are lost between the two machines.
One thing to avoid at all costs is to just disconnect the primary site from the network but leave the machine running. This almost always leads to a split brain conditioin and makes recovery much more likely to lose data. To test if the failover process is working correctly you should just shut down the primary node and then either AutoStart or RepliStor will lose the heartbeat communications. This will prompt a failover of the Alias and any associated processes.
A manual failover is as simple as Relocating the Resource Group in AutoStart, assuming you are using both AutoStart along with RepliStor. This is done from the AutoStart console of can be done via the AutoStart Command Line interface as well. The same is true if you choose to only use RepliStor's Alias functionality without the use of AutoStart.
I recommend you try this concept out in a test/lab environment first to become familier with the process before configuring a production environment. Both AutoStart and RepliStor can be used for 30 days with a built in temporary license.
I agree with jschrade's comments. Based on your description of File Share replication and a virtual hostname, I would recommend using RepliStor without AutoStart.
An additional reason to include AutoStart which was not yet mentioned is if there are more than 2 nodes in the environment. RepliStor is limited to a 2 node failover topology.
The features that jschrade refers to are known as the RepliStor "Alias" functionality. This provides a virtual name and a failover mechanism. These features are well documented in the RepliStor Administrator's guide and if you have any specific questions we'll gladly help out in the forums.
Originally customer are bought EAS/Replistor for Exchange but due some internal security they just don't allow us to continue implement exchange (not allow EA right during install) so they are change to this solution.
Anyway we are plan add protection on some windows services later.
yito1
262 Posts
0
June 12th, 2010 10:00
Hi,
Why do you use AutoStart and RepliStor?
If it is file server, I think it not to have to put it together.
If you want combine make the data source of RepliStor.
You must read Administrator's guide.
jschrade1
106 Posts
1
June 14th, 2010 05:00
First, it is not necessary to have both products installed to accomplish this configuration. RepliStor can be used alone, without AutoStart, to 1) replicate data and 2) repicate share informatioin. If you choose to use both for some other reason not mentioned that is also possible.
In either case, the failover of resources can be done either manually via the GUI tools or automatically if the heartbeats are lost between the two machines.
One thing to avoid at all costs is to just disconnect the primary site from the network but leave the machine running. This almost always leads to a split brain conditioin and makes recovery much more likely to lose data. To test if the failover process is working correctly you should just shut down the primary node and then either AutoStart or RepliStor will lose the heartbeat communications. This will prompt a failover of the Alias and any associated processes.
A manual failover is as simple as Relocating the Resource Group in AutoStart, assuming you are using both AutoStart along with RepliStor. This is done from the AutoStart console of can be done via the AutoStart Command Line interface as well. The same is true if you choose to only use RepliStor's Alias functionality without the use of AutoStart.
I recommend you try this concept out in a test/lab environment first to become familier with the process before configuring a production environment. Both AutoStart and RepliStor can be used for 30 days with a built in temporary license.
JoelStewart
24 Posts
0
June 14th, 2010 08:00
I agree with jschrade's comments. Based on your description of File Share replication and a virtual hostname, I would recommend using RepliStor without AutoStart.
An additional reason to include AutoStart which was not yet mentioned is if there are more than 2 nodes in the environment. RepliStor is limited to a 2 node failover topology.
The features that jschrade refers to are known as the RepliStor "Alias" functionality. This provides a virtual name and a failover mechanism. These features are well documented in the RepliStor Administrator's guide and if you have any specific questions we'll gladly help out in the forums.
treesk
26 Posts
0
June 15th, 2010 02:00
Thank for your response.
Originally customer are bought EAS/Replistor for Exchange but due some internal security they just don't allow us to continue implement exchange (not allow EA right during install) so they are change to this solution.
Anyway we are plan add protection on some windows services later.