Unsolved
This post is more than 5 years old
1 Message
0
613
May 13th, 2007 07:00
VSS Cannot Allocate Shadow Copy Space
I'm running Replistor 6.2 in a MS Cluster environment connected to an AX100. I'm trying to set up a Shadow Copy from one shared cluster disk (D:) located on the AX100 to a local disk on the server (V:). When I type in the command 'vssadmin add shadowstorage /for=D: /on=V:' I get the Error: Shadow Copying The Specified Volume Is Not Supported.
On further investigation using the Windows GUI to configure Shadow Storage, it appears that I can only set up 'local disks' as source and destination locations for Shadow Copies not the shared AX100 disks.
I'm not sure whether this is a Windows, Replistor or AX100 problem or whether its something simple I've missed in the configuration - any information on this would be great.
On further investigation using the Windows GUI to configure Shadow Storage, it appears that I can only set up 'local disks' as source and destination locations for Shadow Copies not the shared AX100 disks.
I'm not sure whether this is a Windows, Replistor or AX100 problem or whether its something simple I've missed in the configuration - any information on this would be great.
0 events found
No Events found!
MarkNZ1
4 Posts
0
June 27th, 2007 16:00
MS Clusters works in a kind of active-passive arrangement .. where only 1 node of a cluster has full control of a resource at a time .. in this case the resource is the D: drive (that's the AX100 drive yes ?)
And that the V: drive is internal to one of the cluster nodes (guessing it is another partition on the cluster nodes boot drive ?)
If you then tell VSS that it keeps track of changces to the D: drive by making using of space on V: the cluster software will (and should) tell you "No!" .. the reason being is that the V: drive can only ever be seen by the one cluster node .. the other cluster node could very well have a "V: drive" .. but it will be a completely difference V: drive... so in the even of a cluster failover where the second node takes control of D: .. how does it then get at the VSS data held on the V: drive of the other node ?!?!
A method that might work would be to create a new LUN on the AX100, presend it to BOTH cluster nodes as a drive letter (X: for example) and then make it a dependant resource in the MS Cluster .. where if D: is to be failed over, then X: must also fail over.