What we want for our server

Platinum

Platinum

New Member
We have a server here that we want to setup as a file server. What we really want is two 500gb+ drives which mirror each other in case one fails. 1 problem... the server only supprots SCSI drives which can only support up to 300gb per drive. So... we basically need to get 4. Is there a way to have 2 of these drives setup in a RAID, which will then be mirrored to thse other 2 drives?

Maybe have 2 300gb drives act as 1 drive, and be mirrored to the other 2, which are also acting as 1 drive
 
it's not really my expertise, raid and all.
but if you can make 2 sets of drives in raid in your hardware config
and then mirror the 2 drives you see in windows using disk manager.

or am i talking total crap here? i've never used raid setups before
 
I don't recommend any of that. Set up a RAID 5 array, if you have 4 drives. Set it up as a 3 drive array with a spare. So you will have 300 gig x3 (just under a TB) and with the spare drive if any of the drives fail the spare will rebuild the array, and then all you have to do is swap out the bad drive.

I just did this exact same thing this week. We have some old Compaq dual xeon 2.5 servers w/ raid and 2 gigs of RAM. There was no OS on them, so I slapped Linux on it, set up a samba server and a share. Gave it an IP and tossed it on a managed switch on a VLAN with all the other servers (my cisco guy did the switch config). Now my users have access to RAID 5 file server share. However, I only have three drives so I am not running with a spare.

The tricky part will be setting up permissions for the shares, and if you are making a part of your domain network at work you may need to bind it to your DNS server and your LDAP directory. If its going to be for a limited amount of users, just set up its own local user:group and give that information out to your users who need to map it.
 
tlarkin said:
The tricky part will be setting up permissions for the shares, and if you are making a part of your domain network at work you may need to bind it to your DNS server and your LDAP directory.
Click to expand...

Not necessary. DNS is for resolving domain to IP. On a local domain, all you have to do is use UNC and map the shares to the file server.
 
SirKenin said:
Not necessary. DNS is for resolving domain to IP. On a local domain, all you have to do is use UNC and map the shares to the file server.
Click to expand...

hence the part where I said, "you may":)

If domain users are mapping it, the easiest way is to make it part of the domain, IMO. There are always many ways to accomplish something though.
 
I have the same setup here. All my computers are on a local domain, as well as my file server. I just mapped the shares and it works perfect. :)
 
You must log in or register to reply here.
Back
Top