anyone know any managed dedicated server provider who we can mail our hard disks to? We have a small pipe to the Internet and this is the only avenue we've thought of.
Or perhaps another solution that we haven't thought of?
I have a server with 2 hard drives, say drive A and drive B. Right now all my files, database and data is on drive A, and drive B is empty. Since I have another drive available, I want to split the load between the two drives. I'm ok with having the web pages and the database on one drive. I mostly want to just have the data (I have about 500GB of data) split between the two drives. Note that I want to avoid duplicating the data. I want to have each file on either drive A XOR drive B.
Should I map a separate subdomain to drive B and then use that subdomain to serve the half of the data thats there? Is there something I can do with hard/soft links on the server so that even though the data is on 2 drives, users still use the same url to access data on either drive? Any other options?
I would like to hear which configuration you think will be better for a hosting server.
I have allready a raid controller in the server.
I am more concerned with security.
Currently we're using HP servers with 4 hot-swap bays that hold 3.5" Seagate Cheetah 15K RPM SAS disks, which we can get in 300, 450, and 600 GB flavors.
I'm looking at the HP DL380/385 models which use 2.5" SAS disks. About the only decent 15K RPM SAS disk I've found in 2.5" form is the Seagate Savvio, but it doesn't come any larger than 146 GB.
Anyone know of another enterprise-class SAS disk that has all of the following attributes: 2.5", 15K RPM, SAS, and at least 300 GB?
(Please, no 10K RPM or SATA recommendations like the WD Velociraptor. I won't consider anything that's not 15K RPM SAS.)
I do not have a restore disk for my Toshiba laptop and there is a virus on it. Can I use my restore disk from my HP computer? Both use windows XP?
View 4 Replies View RelatedHardisk brands all had their ups and downs over time. So almost all brands made sometime bad drive models that failed (yes, even IBM)
I just finished reading an article that currently for servers it seems Seagate is the best (currently).
Some say Western, some say Maxtor, I heard everything. It seems nobody agrees or there isnt one that actually has the lowest failure rates.
It would be nice to hear from real experience on servers scenarios (not office, or desktop). The article also said Hitachi was one of the worst and my eyes just popped out. I found reviews of people here that said Hitachi where the bests. So to conclude it seems everybody has their own preference.
It would be nice to hear some Datacenters or people with tons of servers. I suppose recovery centers and datacenters probably have the best stats on which disks are failing the most.
How do you handle your mega space requirements for your high-use databases? Do any of you work with storage in the terabytes? If so, what kind of hardware and setup do you use?
Do you just have many commodity servers with maybe 100GB or so in each, or do you have some kind of shared RAID array set up? Or some kind of SAN?
Keep in mind I'm not talking about network storage (i.e. slow, personal use, file server) but rather high-speed intensive high-read/high-write database requirements.
What are the options for implementing such a solution?
What types of products fit such requirements? Could you comment on what things to look for when purchasing such a set of products?
I colo a 1U machine with 2-36gig drives. They're not in RAID, and I have it set to rsync backups to a remote machine on a regular schedule. I have another remote machine functioning as a secondary DNS. Neither of these 2 are on a large upstream pipe. I just bought 2-147gig drives that I'd like to replace the 36g's with. How does this sound for a scenario to accomplish this with little downtime (pre-pardon my noob'ish ways):
1. Do a complete rsync of the filesystem to my remote machine as well as sync the mysql db's (to 1 remote drive).
2. Pop that single rsync'd drive into an external enclosure.
3. Travel to datacenter, once there, plug external drive into laptop and start up a VM that boots off of that drive.
4. Sync again so external drive has the most up-to-date data.
5. Change over IP's from colo to VM on laptop.
6. Shutdown and swap out drives in colo'd box with the new ones.
7. Setup new drives as RAID 1, install OS, then rsync filesystem over from laptop to new drives in colo'd box.
8. Change back IP's.
What am I missing, or is there an easier way without a 2nd colo/dedicated server? Currently, the colo'd machine is using about 1.3Mbit/sec outbound and it's running a low load.
I have a server with SATA- Hot Swap disks. I can do this, and swap out a disk, and re-partition
the new one, however the running Linux kernel hangs on to the old partition table in memory.
So even though the disk is not in use, and has been re-partitioned, I still need to reboot to
get the kernel to see the new partitions, and use them. Is there any way around this?
How to force kernel to re-read disk partitions on non-system disks?
Up to now we've been using CentOS with SCSI/SATA disk shich weren't "hot swap", and now we're upgrading to a Dell PowerEdge 1950 revision III with SAS hot swap disks on a PERC RAID 6i (new model of raid controller from Dell).
OF COURSE, Dell ONLY supports Windows (and Red Hat at the very most on the Linux world) so we were told by a Microsoft Tech that to be able to extract a disk and replace with another it had to be done via software. (The software powers the disk down and then you replace it)
Does anyone use CentOS with hot swap SAS disks? Do you use any special software to monitor the disks and/or replace them?
For building a house for, ie, 30 VPS, what kind of disks are you using? normal SATA? Raptor? SCSI?
I am going to use Quad-core CPU with 4-8GB RAM, but still wondering about the disks
We're about to buy a Dell Poweredge 1950 with hot swap disks in a raid 1 configuration (might even think about other raid combinations).
We will be installing Centos 5 (never tried it - normally use Centos 4) + control panel
The question is: what happens when a disk fails? How do we find out?(Apart from looking at the server) Any software notices?
Once noticed, what is the standard procedure to replace the disk? (Remember they are "hot swap") Do you just pull one out and replace it? Surely you have to rebuild the array...
if I order a RAID from a host, can I be confident that they're not going to put two of the same make, model and order in there?
Or at least run one of the disks for a significant time before using inserting into the RAID?
Since purchasing 16-disk arrray NAS server 4-5 months ago, 5 disks have crashed so far. They are all WD4000YS. They're all "Raid Edition" which supposed to last longer than typical drives. It has been puzzling me until now.
It turns out that "Data Lifeguard" feature was confusing the RAID controller to believe that the disk was dead, hence the "failed" disk. AFAIK, Western Digital released firmware update on 01/09/07 that's supposed to fix this.
[url]p_faqid=1493&p_created=1168299631&p_sid=vfEX7qri&p_accessibility=0&p_redirect=&p_lva=&p_sp=cF9zcmNoPTEmcF9zb3J0X2J5PSZwX2dyaWRzb3J0PSZwX3J vd19jbnQ9MiZwX3Byb2RzPTAmcF9jYXRzPTAmcF9wdj0mcF9jdj0mcF9zZWFyY2hfdHlwZT1hbnN3ZXJzLnNlYXJjaF9mbmwmcF9wYWdlPTEmcF9zZWFyY2hfdGV4dD1XRDQwMDBZUw**&p_li=&p_ topview=1
So, if you have WDxxxxYS on your pre-production server, pull them out for a firmware update first!
For me, I can only swap "hot-spare" out for a firmware update. For other disks, I'll just have to wait for them to "drop" out of the array first. I cannot take this server offline at all. Any suggestions?
If you want a quick run down as to WHY I want to do this, read here
Basically, my ISP could not get my server running stable on a simple raid 1 (or raid 5) so what it came down to was having them install my system on a single disk. I don't exactly like this, main reason being, if the system (or HDD) crashes, I'll end up with another several hours of down time... So here is my proposal:
Please Note: This will have to be accomplished on a live System (full backups!) over ssh as I don't trust my ISP to do things right as described in my post above.
Current Setup:
CentOS 5.3 x86_64
Dual Xeon 5410
16GB RAM
4x 750GB HDDs
/boot - /dev/sda1 - 512MB (real 471MB) ext3
/ - /dev/sda2 - 50GB (real 46GB) ext3
/home - /dev/sda3 - remaining space (real 642GB) ext3
swap - /dev/sdb1 - 32GB
/backup - /dev/sdb2 - remaining space (real 659GB) ext3
/dev/md0 - /dev/sdc + /dev/sdd - raid 1 (NOTE: uses entire disk, no partitions!)
Proposed Solution:
Code:
vgcreate -s 64M vg0 /dev/md0
lvcreate -L 512M -n lvboot vg0
lvcreate -L 50G -n lvroot vg0
lvcreate -L 5G -n lvtmp vg0
lvcreate --extent 100%FREE -n lvhome vg0
mkfs -t ext3 -m 1 /dev/vg0/lvboot
mkfs -t ext3 -m 1 /dev/vg0/lvroot
mkfs -t ext3 -m 1 /dev/vg0/lvtmp
mkfs -t ext3 -m 1 /dev/vg0/lvhome
Now, I'd like to 'init 1' at this stage but I can't, so I won't (possible solutions?? Possible to umount the / partition??)
Assuming I'd have to do this on a fully live system, I'd disable all services that I can
Code:
/etc/init.d/sendmail stop
/etc/init.d/postfix stop
/etc/init.d/saslauthd stop
/etc/init.d/httpd stop
/etc/init.d/mysql stop
/etc/init.d/courier-authlib stop
/etc/init.d/courier-imap stop
/etc/init.d/amavisd stop
/etc/init.d/clamd stop
/etc/init.d/pure-ftpd stop
/etc/init.d/fail2ban stop
/etc/init.d/syslogd stop
Then we copy all of our data from the single partitions to the raid disks
Code:
mkdir /mnt/newroot
mkdir /mnt/newroot/boot
mkdir /mnt/newroot/tmp
mkdir /mnt/newroot/home
Code:
mount /dev/vg0/lvboot /mnt/newroot/boot
mount /dev/vg0/lvroot /mnt/newroot/root
mount /dev/vg0/lvtmp /mnt/newroot/tmp
mount /dev/vg0/lvhome /mnt/newroot/home
(I think I covered everything)
Code:
umount -l /dev/sda1 (/boot)
umount -l /dev/sda3 (/home)
cp -dpRx /* /mnt/newroot/
mount /dev/sda1 /boot
cp -dpRx /boot/* /mnt/newroot/boot/
mount /dev/sda3 /home
cp -dpRx /home/* /mnt/newroot/home/
Once we have everything copied, update /etc/fstab and /etc/mtab to reflect the changes we made:
vi /etc/fstab
Code:
LABEL=/home /home ext3 defaults 0 3
LABEL=/ / ext3 defaults,usrquota,grpquota 1 1
LABEL=/boot /boot ext3 defaults 1 2
tmpfs /dev/shm tmpfs defaults 0 0
devpts /dev/pts devpts gid=5,mode=620 0 0
sysfs /sys sysfs defaults 0 0
proc /proc proc defaults 0 0
LABEL=SWAP-sdb1 swap swap defaults 0 0
To
Code:
/dev/vg0/lvhome /home ext3 defaults 0 3
/dev/vg0/lvroot / ext3 defaults,usrquota,grpquota 1 1
/dev/vg0/lvboot /boot ext3 defaults 1 2
tmpfs /dev/shm tmpfs defaults 0 0
devpts /dev/pts devpts gid=5,mode=620 0 0
sysfs /sys sysfs defaults 0 0
proc /proc proc defaults 0 0
LABEL=SWAP-sdb1 swap swap defaults 0 0
Moving on, we make a fail safe in the event this doesn't work out:
vi /boot/grub/menu.lst
find
Code:
default=0
add after
Code:
fallback=1
Then we find (in the same file):
Code:
title CentOS (2.6.18-164.el5)
root (hd1,0)
kernel /vmlinuz-2.6.18-164.el5 ro root=/dev/vg0/vgroot
initrd /initrd-2.6.18-164.el5.img
Add before:
Code:
title CentOS (2.6.18-164.el5)
root (hd3,0)
kernel /vmlinuz-2.6.18-164.el5 ro root=/dev/sda2
initrd /initrd-2.6.18-164.el5.img
Where (hd3,0) is /dev/sdc. If the system fails to boot to the raid then it'll auto boot to the single disk (/dev/sda)
then update my ramdisk:
mv /boot/initrd-`uname -r`.img /boot/initrd-`uname -r`.img_bak
mkinitrd /boot/initrd-`uname -r`.img `uname -r`
And now to set up grub...
Code:
grub
> root (hd0,0)
> setup (hd0)
we should see something like this:
Checking if "/boot/grub/stage1" exists... no
Checking if "/grub/stage1" exists... yes
Checking if "/grub/stage2" exists... yes
Checking if "/grub/e2fs_stage1_5" exists... yes
Running "embed /grub/e2fs_stage1_5 (hd0)"... 15 sectors are embedded.
succeeded
Running "install /grub/stage1 (hd0) (hd0)1+15 p (hd0,0)/grub/stage2 /grub/grub.conf"... succeeded
Done.
Code:
> root (hd3,0)
> setup (hd3)
Again, we should see something like this:
Checking if "/boot/grub/stage1" exists... no
Checking if "/grub/stage1" exists... yes
Checking if "/grub/stage2" exists... yes
Checking if "/grub/e2fs_stage1_5" exists... yes
Running "embed /grub/e2fs_stage1_5 (hd1)"... 15 sectors are embedded.
succeeded
Running "install /grub/stage1 (hd1) (hd1)1+15 p (hd1,0)/grub/stage2 /grub/grub.conf"... succeeded
Done.
Code:
> quit
From here I think we're ready to reboot, can't see where I missed anything. If all goes well then I should see my volume groups listed in 'df- h'
Due to data center limitations, I am restricted to 100GB on my primary disk but can have up to 2TB on a second disk.Is it possible to have the backup node use the second disk instead of the primary disk?Also is it possible to have multiple to have multiple backup nodes?
View 3 Replies View Relatedjust out of interest, does anyone know a ssh command(s) to bring up your servers hardware stats? Cpu type and clock speed, memory, disks etc.
I've looked everywhere for a shell command to show cpu type with no luck.
i find some post say xen need some time to learn, and it will be a learn curve here,
is it really xen hard to learn and use?
I'm building a couple of VPS host servers for a client.
Each server have to host 20 VPS and each server will be 4 cores with 32GB of ram. So CPU and ram should be just fine, my interrogatioon now is hard drives. The company owns the machines, but not the drives yet.
I searched a lot on your forums but found nothing relating on VPS. I'm basicly a DBA IRL, so I have experience in hardrives when it comes to databases, but it's completely different for VPS.
According to my boss, each VPS will run a LAMP solution (having a separeted DB cluster is out of question for some reason).
First, raid1 is indeed a must. There is room for 2x 3.5 drives. I might be able to change the backplane for 4x2.5, but i'm not sure...
I've came to several solutions:
2x SATA 7.2k => comes to about 140$
2x SATA 10k (velociraptor) => comes to about 500$
2x SAS 10k with PCIe controller => comes to about 850$
2x SAS 15k with PCIe controller=> comes to about 1000$
They need at least 300GB storage.
But my problem is that the servers do not have SAS onboard so I need a controller and in my case the cheapest solution is best.
But I'm not sure that SATA 7.2k will hold the charge of 20 complete VPS.
Does it worth it to go with SAS anyway or SATA should be just fine? With SATA better use plain old sata 7.2k or 10k drives?
That's a lot of text for not much: What is best for VPS: SATA 7.2k, SATA 10k or SAS 10k?
how they sell those usb hard drives that connect to the computer that can hold like 100 gb's.....
well if i hook up one of those external hard drives to my server can i use it as webspace for users?
I have read about all of the things you have to do with an unmanaged server, and how beginners shouldn't even try. I am pretty smart though I have a lot of experience with cpanel, and I am not worried about getting my feet wet.
This is the system I want:
Celeron 1.7 GHz
1 GB RAM
80 GB HD
1500 GB Bandwidth
cPanel / WHm
Full root access
How much time would it take to keep the thing running? How do you monitor the server? How do you know when software updates, and patches are available? Can all of the software needed be found for free? What kind of problems would I encounter, and would this be way over my head?
I have a dedicated from ovh.
Heres the specs
Intel Core2Duo E6750
2x 2.66 Ghz
Dual Core
2 GB DDR 2
2x 750 GB
SATA2 RAID HARD 1
Now basicaly i dont want the hard raid i wana see both 750gig drives.
Now ive bin told u can only do this through the raid bios?
So if any1 has a guide or any helpful comments i would be very gratful.
Its running windows web.
I can install any os i want,Im not very friendly with linux but if thats the only option then id give it a shot.
Now iam useing 320Gig SATA harddrive as my primary hard drive,i dont use 2rd harddrive,iam haveing pure download site,in TOP command 4.5%wa is this bit high? or can i add 2rd harddisk and move some data to there to reduce wa,but my load of the server is fine or any way to reduce wa?
View 1 Replies View RelatedI am running a Fedora box with cPanel...
The hard drive has a capacity of 36 gigs and there's currently 18 GIGs of data on it.
When I do "df -h", it indicates that / has 85% of it's capacity in use. When I run "df -hi" it shows that / has 58% of it's inodes in use.
Is there anything I can do to increase /'s capacity? Can I free up some inodes? All that / contains are folders.
I am about to buy a Compaq server with 6 SCSI hard drives. In you opinion, what is the best RAID configuration with 6 HDs?
View 14 Replies View RelatedDo the old RLX Blade servers use 'mini' hard drives? I can't find an answer anywhere. I seem to recall that they use smaller 2.5" drives. Is this the case?
And, if so, do they make "good" drives worthy of being in a server in that size? Are they essentially just a laptop drive?
I just received:
[cPanel smartcheck] Possible Hard Drive Failure Soon
ATA Error Count: 1512 (device log contains only the most recent five errors)
Error 1512 occurred at disk power-on lifetime: 11736 hours (489 days + 0 hours)
Error 1511 occurred at disk power-on lifetime: 11736 hours (489 days + 0 hours)
Error 1510 occurred at disk power-on lifetime: 11736 hours (489 days + 0 hours)
Error 1509 occurred at disk power-on lifetime: 11736 hours (489 days + 0 hours)
Error 1508 occurred at disk power-on lifetime: 11736 hours (489 days + 0 hours)
----END /dev/sda--
What do you advice me to do? ask the DC to change the Hard Drive or wait till damaged?
I already have a weekly external Backup.
Hard drive arrangement
I have a terminal server with a bunch of applications on it, among which is a database driven app. There have been complaints that access to the db is sluggish. right now the server is on just one 7.2k drive.
I am guessing its a hard drive bottleneck because memory and cpu usage seems okay. I have a few ideas. Please tell me which of these you would recommend.
1. Upgrade entire server to raid 10 system.
2. Upgrade the entire server to a 5-disk RAID 5 system.
3. Create two raid 1 setups. One for the OS and regular apps, the second one to host the DB.
4. Create a raid 1 setup for the OS and regular apps, and a RAID 5 setup for the DB.
Ideally I would like to see improved read/write speeds on both regular files/apps and on the database. The RAID 10 system was what I was leaning towards at first because the stripping increases throughput, but then I realized I may see better performance by keeping the regular files and the DB on independent setups so that OS and file read/writes won't affect the DB read/writes.
On my centos webserver I currently am using a 250gb ide drive.
I just bought 2 Western Digital Raptor WD1500ADFD 150GB 10,000 RPM 16MB hard drives.
And now I am wondering what kind of setup I should have?
Should I have the 250gb hd as a backup drive now and have the two raptors in a raid 0 array.
What would be the best configuration?
I have never had a hard drive fail on me, i dont think the I/O on my servers would ever warrant it but im looking to ask people that have had a hard drive die one them the following:
1. Were you ever cautious before your hard drive failure or did you lose data and if you did lose data, did it make you buck up your ideas (i.e do you now have a solid backup plan or do you still play maverick)
2. If you have had a hard drive failure, has it made you, do you think, overly-cautious?
3. Has a hard-drive failure ever swayed you towards the more expensive raptor drives? and if so, why?