J
Jake
Hi,
What do you guys do to get your system up again when your main domain
controller / fileserver goes down? Directory service and dns would be
seamless between domain controllers, but the file share location for
roaming profiles and home folder is 'hardcoded' in each user account to
the server that goes down..
We are in the process of virtualize our domain controllers/file servers.
The have access to a common SAN where profiles and home folders are
stored. We use ESX Server 3.5i if that makes any difference.
What is 'best practice' for failsafe operation in this scenario? I
would rather not use DFS as there are huge amounts of data involved and
I don't want to keep two identical copies (other than backups, which are
stored in another location
Thanks for comments and urls...
jake
What do you guys do to get your system up again when your main domain
controller / fileserver goes down? Directory service and dns would be
seamless between domain controllers, but the file share location for
roaming profiles and home folder is 'hardcoded' in each user account to
the server that goes down..
We are in the process of virtualize our domain controllers/file servers.
The have access to a common SAN where profiles and home folders are
stored. We use ESX Server 3.5i if that makes any difference.
What is 'best practice' for failsafe operation in this scenario? I
would rather not use DFS as there are huge amounts of data involved and
I don't want to keep two identical copies (other than backups, which are
stored in another location
Thanks for comments and urls...
jake