Dear all, I'm trying to setup a development server which hosts a number of virtual hosts.and i need your advice with the following: 1. What's the best Filesystem to be used with an apache server?Relevant info: i. Mysql DB size' 1 GBii. Code directory size' 8 GB (Max file size is 5 KB)2. What's the best file structure to maximize seek time from drives?Relevant info:i. 2 X 1 TB SATAII 64MB blk Edition Int HDDii. 1 X 320GB General info: I have an additional directory which hosts all my code under /Development . this directory has a size of almost 300 GB.14 Virtual Hosts would be created on the server under /etc/httpd/VHosts/ I was thinking of the following structure: Drive A (320 GB): OS Drive B (1 TB): Mysql + /homeDrive C (1 TB): /development + /opt Would this work? i followed no guidelines with the above setup, it's just using my own logic. so i'd appreciate an expert advice with this. Thanks, --Roland
From: Roland RoLaNd r_o_l_a_n_d@hotmail.com
- Drive A (320 GB): OS
- Drive B (1 TB): Mysql + /home
- Drive C (1 TB): /development + /opt
Does that mean no RAID and downtime to recover from backups is acceptable...?
JD
I'm using rsync with a cronjob everynight at 11 pm to do the following: sync relevant directories to a running phsycial machine (same specs more or lesS)Sync relevant directories to a running Virtual Machine(vmware) On down time i'll run either one of those machines till problem is fixed. wouldn't that be enough?
Date: Mon, 10 Jan 2011 03:01:56 -0800 From: jdmls@yahoo.com To: centos@centos.org Subject: Re: [CentOS] Centos installation Vs Disk partitioning
From: Roland RoLaNd r_o_l_a_n_d@hotmail.com
- Drive A (320 GB): OS
- Drive B (1 TB): Mysql + /home
- Drive C (1 TB): /development + /opt
Does that mean no RAID and downtime to recover from backups is acceptable...?
JD
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On Mon, Jan 10, 2011 at 7:21 AM, Roland RoLaNd r_o_l_a_n_d@hotmail.com wrote:
I'm using rsync with a cronjob everynight at 11 pm to do the following:
sync relevant directories to a running phsycial machine (same specs more or lesS) Sync relevant directories to a running Virtual Machine(vmware)
On down time i'll run either one of those machines till problem is fixed. wouldn't that be enough?
On my network I am using a combination of rsync and DRBD volumes to make copies of my data. The main large drive is rsynced regularly to another system. The daily changes (mostly documentation) is mirrored on two drives on one server and that volume is DRBD'ed to the other system. Works well and recovery is quick.
On Mon, Jan 10, 2011 at 3:03 AM, Roland RoLaNd r_o_l_a_n_d@hotmail.com wrote:
Dear all, I'm trying to setup a development server which hosts a number of virtual hosts. and i need your advice with the following:
- What's the best Filesystem to be used with an apache server?
Relevant info:
i. Mysql DB size' 1 GB ii. Code directory size' 8 GB (Max file size is 5 KB)
- What's the best file structure to maximize seek time from drives?
Relevant info:
i. 2 X 1 TB SATAII 64MB blk Edition Int HDD
ii. 1 X 320GB
General info:
I have an additional directory which hosts all my code under /Development . this directory has a size of almost 300 GB. 14 Virtual Hosts would be created on the server under /etc/httpd/VHosts/
I was thinking of the following structure:
Drive A (320 GB): OS Drive B (1 TB): Mysql + /home Drive C (1 TB): /development + /opt
Would this work? i followed no guidelines with the above setup, it's just using my own logic. so i'd appreciate an expert advice with this. Thanks, --Roland
Filesystem is almost always irrelevant. If you don't already know that you need something special, use the default. The only potential issue would be if you have a lot of small files in one directory, or an extremely large disk.
A daily rsync is not enough for protection against disk failures, and disks are exceedingly cheap. Your estimated disk usage is 9GB, and you have 2x 1TB drives. There's no excuse for not making that into a RAID. The Linux caching subsystems will handle most of the performance concerns you might have, as it will automatically cache things you use often. Don't think too much about one thing that has little benefit, while neglecting other things that do.