Badgeroonie
IS-IT--Management
Hi all,
I'm after some advice. I wish to provide full redundancy to my file servers, so that if say the motherboard goes boom, then our files would remain available on another server.
Some form of clustering seems to be the way to go, but more specifically the NLB (Network Load Balancing) route appears to be more specific to my needs. From what I read 'clustering' (in Win2003) would use a shared external storage which isn't what I have. I need (ideally I currently believe) to have two similar servers, both of which have a local store of all the files shared on the LAN, so if either one goes down, the other is still there to provide service. One question mark I have though is that the literature I've read thus far seems to apply NLB to internet servers, so I therefore question if it'll suffice in my case?
I have two 'test servers' sat here ready to go with Win2003 installed. I'd really appreciate anyones thoughts or advice toward achieving what I am after.
My thanks in advance!
I'm after some advice. I wish to provide full redundancy to my file servers, so that if say the motherboard goes boom, then our files would remain available on another server.
Some form of clustering seems to be the way to go, but more specifically the NLB (Network Load Balancing) route appears to be more specific to my needs. From what I read 'clustering' (in Win2003) would use a shared external storage which isn't what I have. I need (ideally I currently believe) to have two similar servers, both of which have a local store of all the files shared on the LAN, so if either one goes down, the other is still there to provide service. One question mark I have though is that the literature I've read thus far seems to apply NLB to internet servers, so I therefore question if it'll suffice in my case?
I have two 'test servers' sat here ready to go with Win2003 installed. I'd really appreciate anyones thoughts or advice toward achieving what I am after.
My thanks in advance!