I'm not sure I understand what you are using RepliStor (RS) for. First, did you install RS after configuring MSCS. During the install did you check the box to enable the MSCS portion of RS?
Normally you would use RS to replicate data from the shared disk of the MSCS Resource Group to a third server, possibly accross a WAN. It sounds like you are using RS to replicate some data from one MSCS cluster node to the other. Did you add a specification into the MSCS Resource Group? Are the two drives you mentioned shared disks also in the MSCS Resource Group?
If these two disks are really not Shared between the two nodes then you can use RS to replicate the data between the two MSCS nodes but in that case RS would not be used in the Resource Group. If that is correct then all you would need to do is add an extent to the existing disks. Or, if you are not comfortable doing that then just replace the disk on the Target node with the larger disk. You should disable the RS specification going to that disk first and make sure you replace the one on the non-production node first. Then enable the specification and re-sync the data to the new disk. Then you would start using the node that has the new disk as the production node and then replace the disk of the first machine. Then sync back to that node from the second node.
Or, if you can take an outage, just back up the data to tape and replace the two disks and then restore the data to the production node and RS will mirror the data to the other node.
If I am not understanding you requirements please respond with a little more detail.
No, this is not a temporary thing. As the space is running low, I am increasing the space by mapping a new drive of bigger size to ther server which is 750 GB.
So if i change the drive, will I need to do some configuration change on RepliStore to, and like wise on it clustered server.
Since RepliStor will have a specification that points to the original drive letter, you will need to change the drive letter of the new drive to be the same as the drive letter of the drive that is being replaced. That assumes that the specification is replicating the entire drive now.
Your best alternative is to open a Support Case for RepliStor after you have mounted the new drives and then a support person can help you with making any changes to RepliStor.
yito1
262 Posts
0
September 14th, 2010 08:00
Hi,
Is this temporary processing?
Please do the following procedure if it is temporary processing.
Make Specification to synchronize to 500GB ---> 750GB.
Delete the Specification if the synchronization of data finished.
jschrade1
106 Posts
1
September 14th, 2010 09:00
I'm not sure I understand what you are using RepliStor (RS) for. First, did you install RS after configuring MSCS. During the install did you check the box to enable the MSCS portion of RS?
Normally you would use RS to replicate data from the shared disk of the MSCS Resource Group to a third server, possibly accross a WAN. It sounds like you are using RS to replicate some data from one MSCS cluster node to the other. Did you add a specification into the MSCS Resource Group? Are the two drives you mentioned shared disks also in the MSCS Resource Group?
If these two disks are really not Shared between the two nodes then you can use RS to replicate the data between the two MSCS nodes but in that case RS would not be used in the Resource Group. If that is correct then all you would need to do is add an extent to the existing disks. Or, if you are not comfortable doing that then just replace the disk on the Target node with the larger disk. You should disable the RS specification going to that disk first and make sure you replace the one on the non-production node first. Then enable the specification and re-sync the data to the new disk. Then you would start using the node that has the new disk as the production node and then replace the disk of the first machine. Then sync back to that node from the second node.
Or, if you can take an outage, just back up the data to tape and replace the two disks and then restore the data to the production node and RS will mirror the data to the other node.
If I am not understanding you requirements please respond with a little more detail.
Thanks...JS
rama_maddodi
1 Rookie
•
66 Posts
0
September 14th, 2010 09:00
No, this is not a temporary thing. As the space is running low, I am increasing the space by mapping a new drive of bigger size to ther server which is 750 GB.
So if i change the drive, will I need to do some configuration change on RepliStore to, and like wise on it clustered server.
jschrade1
106 Posts
0
September 14th, 2010 12:00
Since RepliStor will have a specification that points to the original drive letter, you will need to change the drive letter of the new drive to be the same as the drive letter of the drive that is being replaced. That assumes that the specification is replicating the entire drive now.
Your best alternative is to open a Support Case for RepliStor after you have mounted the new drives and then a support person can help you with making any changes to RepliStor.
JS
1 Attachment
image002.jpg