Guest Magoo Posted August 31, 2007 Posted August 31, 2007 Looking for a best practice tip here: Need to install Backup Exec on Server 2003 R2. Disk config is as follows: 2 disks mirrored with OS, 4 disks RAID 5 with Data - plenty of space on each volume. When I go to install Backup Exec, it will want to install on the c:\ drive (OS volume). So my question is for a best practice, should i install this application on the data drive (which is a RAID-5 drive) to continue to allow Windows to have sole access to the OS volume? Or, should I allow it to install on the OS drive and share access with Windows? I realize either way would work,, however I'm looking for a best practice. Thanks, Magoo
Guest J Weldin Posted September 1, 2007 Posted September 1, 2007 Re: Installing applications on server - best practice I consider Backup Exec an integral part of the system function (as opposed to a shared application or data), so I would load it on the C drive. You can relocate the log files if you need to at some time to another location (if you start to run out of room). J Weldin "Magoo" <magoo@magoo.bomb> wrote in message news:48058497-FF79-45B2-816C-F4E2C8287478@microsoft.com... > Looking for a best practice tip here: > > Need to install Backup Exec on Server 2003 R2. Disk config is as follows: > 2 > disks mirrored with OS, 4 disks RAID 5 with Data - plenty of space on each > volume. > > When I go to install Backup Exec, it will want to install on the c:\ drive > (OS volume). > > So my question is for a best practice, should i install this application > on > the data drive (which is a RAID-5 drive) to continue to allow Windows to > have > sole access to the OS volume? Or, should I allow it to install on the OS > drive and share access with Windows? I realize either way would work,, > however I'm looking for a best practice. > > Thanks, Magoo
Recommended Posts