2 replies
by khan_sarim Accepted solution
by churdoo Accepted solution
Oh I love these questions. This is like emailing my auto mechanic how to install air conditioning in my car. The two are not co-dependent, albeit it is desirable to have air conditioning in the car, yet it's typically easier and more cost effective to order the car with the air conditioning already installed.
RAID = "Redundant Array of Inexpensive Disks" and is a methodology for storing data across multiple standard disk drives, for reasons of fault tolerance (except RAID 0). So in the event that a disk goes bad in a RAID set, your data is fully and automatically intact on the remaining drives, and when you replace the failed drive, you regain redundancy and can afford a drive to go bad again.
I'm not sure what you're asking here dude. Do you have an existing server in production and now you want to add RAID for fault tolerance, or are you deploying a new server? Since RAID is the makeup of the disk subsystem, then RAID is typically designed into a server at the beginning, rather than retro-fitting into an existing non-RAID server.
So in the case of designing into the server at the beginning, you need a RAID controller compatible with W2K3 server with the drivers, disks, and of course cables. If you have a proper RAID system, then you install W2K3 on the RAID, supplying the drivers at the appropriate point of the install.
This may sound simple, but I'm over-simplifying due to the broad question. So do some more research and post back more specific questions so we can help you more.
This discussion is closed to new replies.
Trending Software posts
Sort by Trending