Hello my situation:
2 esx 3.5 nodes with cluster HA enabled on Equallogic p100 volumes
3 vm for cluster node
all vm are win 2003 sp1 or R2 Enterprise editions
2 domain controller with single domain (2003 R2 ent. edit.) that i wanted use as file servers too: AD1 (fsmo),AD2
my files are profiles,documents and common office doc.All users in the same site and domain can access to these two file server- domain controller with
my question is
how can i create reduntants situation with DFS domain namespace in my 2 dc for my clients?
i know that if i mount volume d:\shared1 ,d:\shared2 in my ad1 with microsoft iscsi iniziator in the vm or as a VMDK disk and i use that volume for my dfs data root, if my ad1 go down or is disconnetted, clients can't access dfs root because, yes AD2 is up, but my data are only in AD1.So my clients can't access to
can be a solution mount a SHARED vmdk virtual disk in both AD1 and AD2 and use tha vmdk as dfs root domain namespace and link targets?
i'll have corrupted files in that shared ntfs volume or i have redundancy for my clients because only one of my name space servers at a time, hadles traffic read write from all clients to that ntfs partition (vmdk shared virtual disk)?
a full dfs replication between AD1 and AD2 can be a solution (without shared vmdk) but i'll need double space for the second vmdk mounted drive in my second server, i think.
Thank for suggestions and for other solution.
2 esx 3.5 nodes with cluster HA enabled on Equallogic p100 volumes
3 vm for cluster node
all vm are win 2003 sp1 or R2 Enterprise editions
2 domain controller with single domain (2003 R2 ent. edit.) that i wanted use as file servers too: AD1 (fsmo),AD2
my files are profiles,documents and common office doc.All users in the same site and domain can access to these two file server- domain controller with
my question is
how can i create reduntants situation with DFS domain namespace in my 2 dc for my clients?
i know that if i mount volume d:\shared1 ,d:\shared2 in my ad1 with microsoft iscsi iniziator in the vm or as a VMDK disk and i use that volume for my dfs data root, if my ad1 go down or is disconnetted, clients can't access dfs root because, yes AD2 is up, but my data are only in AD1.So my clients can't access to
can be a solution mount a SHARED vmdk virtual disk in both AD1 and AD2 and use tha vmdk as dfs root domain namespace and link targets?
i'll have corrupted files in that shared ntfs volume or i have redundancy for my clients because only one of my name space servers at a time, hadles traffic read write from all clients to that ntfs partition (vmdk shared virtual disk)?
a full dfs replication between AD1 and AD2 can be a solution (without shared vmdk) but i'll need double space for the second vmdk mounted drive in my second server, i think.
Thank for suggestions and for other solution.
