= Equipment to use (the Dirvish Server)=
SERVER NAME: GWIBKP
SERVER OS & VERSION: Slackware Linux Version 10.0 Kernel 2.6.14.5
TECHNICAL DESCRIPTION OF THE SERVER
GWIBKP runs an AMD 3000+ with 512 meg of RAM, dual SATA 233Gig system drives connected to the system board and 16 SATA 233 gig drives in two banks of 8 with each bank hooked to its own 3Ware 9xxx series controller.
NOTE: the ASUS Motherboard A7V600 (VIA chipset) in this server had an capacitor issue where the +5 voltage was not properly distributed. This wrecked havoc on the SATA hard drives causing read problems and corruption. The mainboard was changed out with an ABIT (Nvidia chipset) and the voltage issues are gone.
Onboard SATA
| system1 | system2 |
3ware SATA
| 4:4 | 4:5 | 4:6 | 4:7 | | 4:0 | 4:1 | 4:2 | 4:3 | | 2:4 | 2:5 | 2:6 | 2:7 | | 2:0 | 2:1 | 2:2 | 2:3 |
Disks 2:0-2:6 are configured via the 3WARE controller into a single RAID5 volume. This 1.4 Terabyte RAID volume (/dev/sdc1) is overflow storage for a particular department. All other disks are exported as single-disks.
Slot 2:7 is empty
Slot 4:0 and 4:1 will house the onsite backup volume drives
Slot 4:2 and 4:3 will house the offsite backup drives
The remaining slots are available
The 'system' drives also contain various rsyncs and automated backups.
Primary Duties
Duty 1 - Provide 'Near Line Storage' or overflow storage for a certain department.
Duty 2 - (Nightly backups) The critical servers through out the organizatin are backedup to this server via rsync nightly
Duty 3 - (Offsite backups) Hot pull drives are rotated through this system as .tar files are stored on the disks that go 'offsite'.
Duty 4 - (on the shelf backups) Some data and information needs not be archived for later use but only needs to be stored offline for legal reasons. This is data that is completely purged from all other areas. Data is placed on a hard drive and the hard drive is removed from the system. Slot 2:7 can be designated for that.