Guest UselessUser Posted November 14, 2007 Posted November 14, 2007 Hi all, We are looking at implementing a SAN in our network. We currently have several servers each with their own SCSI arrays locally attached... One of the benefits of a SAN appears to be that the disks are easily available to another machine, should the machine hosting the data fail... How exactly does this work in practice? For example, say I have a volume which contains user home directories on the SAN being shared via Server1. Now the volume will be formatted by NTFS which stores all the permissions.. If Server1 were to fail, how would I quickly restore access to the data, say through Server2? Obviously I would have to change the SAN zoning config to allow Server2 access to the volume which it would then detect as a foreign disk (Is that correct), and I would obviously need to change any login scripts etc to reference the new server, (Or change DNS and make the "strict" registry change to allow Server2 to respond to Server1 requests)... but what about all the sharing and permissions etc?? I am little confused how it actually all fits together?
Guest Meinolf Weber Posted November 14, 2007 Posted November 14, 2007 Re: SAN question Hello UselessUser, High availability you can get with clustering. Two servers up to eight will connect to one or more SAN's and take over if a failure occurs on one server, without interfering the users. Thats a very short description, in reality it's more complex. http://www.microsoft.com/windowsserver2003/techinfo/overview/san.mspx Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights. ** Please do NOT email, only reply to Newsgroups ** HELP us help YOU!!! http://www.dts-l.org/goodpost.htm > Hi all, > > We are looking at implementing a SAN in our network. We currently have > several servers each with their own SCSI arrays locally attached... > > One of the benefits of a SAN appears to be that the disks are easily > available to another machine, should the machine hosting the data > fail... > > How exactly does this work in practice? For example, say I have a > volume which contains user home directories on the SAN being shared > via Server1. Now the volume will be formatted by NTFS which stores all > the permissions.. > > If Server1 were to fail, how would I quickly restore access to the > data, say through Server2? Obviously I would have to change the SAN > zoning config to allow Server2 access to the volume which it would > then detect as a foreign disk (Is that correct), and I would obviously > need to change any login scripts etc to reference the new server, (Or > change DNS and make the "strict" registry change to allow Server2 to > respond to Server1 requests)... but what about all the sharing and > permissions etc?? > > I am little confused how it actually all fits together? >
Recommended Posts