I am in a little bit of trouble I got a couple (5) of 750GB hdds that I need backed up to another couple (5?) of 750GB hdds so I can save the data storage on them. They are in a Linux box with a LVM setup I also have a RAID ware card on it but not using any RAID # on them. I decided after finding out what I could do with it to go to Windows 2003 on the server and installing RAID5/6 on it.
It seems that I will have to give up all my data and have everything wiped off from the hard drives this is very sad for me but I still have a chance to save the data on them. So I am thinking of copying them to another bunch of hard drives and then re-add it once the system is in place.
I was looking at this
[url]
But thats clearly too expensive as I just need to back up 5 hard drives (750GB/each) and just need to do it one time. Anyone have any suggestions to this or how should I go about doing it. It doesnt have to be right away but its good to know my options.
Is there any place where they might to do this kind of stuff they let you rent their machine for a couple of hours for a fee so you can back up your data? The server is a COLO and the hardware is mine so I have every right to take it off and back it up with no problem from the datacenter.
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?
Do 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?
am getting new server with 2 (73GB) hard drives i need to know the following:
1.I need to put /home in one hard drive 73GB and the other partitions like /boot, /tmp,/usr and /var on the other drive
where should i put /home? on the primary or or secondary drive?is there any effect on the speed?
2. Am used to servers with 1 drive. is there any difference when it comes to security aplications such as APF,BFD,mod security and other aplicatuions settings?
3. in general should i take the same actions when handling a server with 1 drive and server with 2 drives?
/dev/md0: ext3 mounted as / for all of the software RAID partitions.
I was left to believe this would create redundancy as long as only one drive is removed from the array. Although when I unplug any of the hard drives (one at a time) I get input/output errors and when I try to reboot I get kernel sync errors.
What exactly am I doing wrong when trying to create redundancy? I know that SDA contains the /boot/ partition so it wouldn't boot without that but even if I unplug B,C, and D it still can't sync.
I want to try something different on our methods of replacing or upgrading hard drives.
I want to be able to do most of it via our KVM/IP instead of babysitting the server(s) for so long in the DC.
My thoughts are, how can I add the new hard drive in the DC, and move the data over via the KVM/IP. Can this be done with just a raw drive added (no new setup) using DD or even rsync, or is it better to setup a new installation of CentOS on the new drive, and use rsync to move the data over. Then how do I get the proper drive to boot until I go back into the DC to remove the bad or old drive? I'd be interested in how some of you folks are doing this, as far as what's easiest and could be done over the KVM/IP once the new drive is connected.
Or on systems that have 2 drives with cPanel/WHM, how can we temporarily on an emergency basis untilize the backup drive to do a new setup, copy the data over from the drive that is failing, then just replace the bad drive as a backup drive next time you go in the DC? We have an external USB CD in place to allow remote installs...just curious if anyone does something like this or has ideas how we could make this work.
We use cloning software now, but can end up babysitting a clone for a long period in the DC like this.
Mountain View (CA) - As a company with one of the world's largest IT infrastructures, Google has an opportunity to do more than just search the Internet. From time to time, the company publishes the results of internal research. The most recent project one is sure to spark interest in exploring how and under what circumstances hard drives work - or not.
There is a rule of thumb for replacing hard drives, which taught customers to move data from one drive to another at least every five years. But especially the mechanical nature of hard drives makes these mass storage devices prone to error and some drives may fail and die long before that five-year-mark is reached. Traditionally, extreme environmental conditions are cited as the main reasons for hard drive failure, extreme temperatures and excessive activity being the most prominent ones.
A Google study presented at the currently held Conference on File and Storage Technologies questions these traditional failure explanations and concludes that there are many more factors impacting the life expectancy of a hard drive and that failure predictions are much more complex than previously thought. What makes this study interesting is the fact that Google's server infrastructure is estimated to exceed a number of 450,000 fairly mainstream systems that, in a large number, use consumer-grade devices with capacities ranging from 80 to 400 GB in capacity. According to the company, the project covered "more than 100,000" drives that were put into production in or after 2001. The drives ran at a platter rotation speed of 5400 and 7200 rpm, came from "many of the largest disk drive manufacturers and from at least nine different models."
Google said that it is collecting "vital information" about all of its systems every few minutes and stores the data for further analysis. For example, this information includes environmental factors (such as temperatures), activity levels and SMART parameters (Self-Monitoring Analysis and Reporting Technology) that are commonly considered to be good indicators to describe the health of disk drives.
In general, Google's hard drive population saw a failure rate that was increasing with the age of the drive. Within the group of hard drives up to one year old, 1.7% of the devices had to be replaced due to failure. The rate jumps to 8% in year 2 and 8.6% in year 3. The failure rate levels out thereafter, but Google believes that the reliability of drives older than 4 years is influenced more by "the particular models in that vintage than by disk drive aging effects."
Breaking out different levels of utilization, the Google study shows an interesting result. Only drives with an age of six months or younger show a decidedly higher probability of failure when put into a high activity environment. Once the drive survives its first months, the probability of failure due to high usage decreases in year 1, 2, 3 and 4 - and increases significantly in year 5. Google's temperature research found an equally surprising result: "Failures do not increase when the average temperature increases. In fact, there is a clear trend showing that lower temperatures are associated with higher failure rates. Only at very high temperatures is there a slight reversal of this trend," the authors of the study found.
In contrast the company discovered that certain SMART parameters apparently do have an effect drive failures. For example, drives typically scan the disk surface in the background and report errors as they discover them. Significant scan errors can hint to surface errors and Google reports that fewer than 2% of its drives show scan errors. However, drives with scan errors turned out to be ten times more likely to fail than drives without scan errors. About 70% of Google's drives with scan errors survived the first eight months after the first scan error was reported.
Similarly, reallocation counts, a number that results from the remapping of faulty sectors to a new physical sector, can have a dramatic impact on a hard drive's life: Google said that drives with one or more reallocations fail more often than those with none. The observed average impact on the average fail rate came in at a factor of 3-6, while about 85% of the drives survive past eight months after the first reallocation.
Google discovered similar effects on hard drives in other SMART categories, but them bottom line revealed that 56% of all failed drives had no count in either one of these categories - which means that more than half of all failed drives were put out of operation by factors other than scan errors, reallocation count, offline reallocation and probational counts.
In the end, Google's research does not solve the problem of predicting when hard drives are likely to fail. However, it shows that temperature and high usage alone are not responsible for failures by default. Also, the researcher pointed towards a trend they call "infant mortality phase" - a time frame early in a hard drive's life that shows increased probabilities of failure under certain circumstances. The report lacks a clear cut conclusion, but the authors indicate that there is no promising approach at this time than can predict failures of hard drives: "Powerful predictive models need to make use of signals beyond those provided by SMART."
I just got an additional 500GB hard drive added and mounted it to /home2
There are files that are in /home1 (orginal HD) that will need to be constantly moved over to /home2 via a ftp
But i keep getting this error
550 Rename/move failure: Invalid cross-device link
Does anyone have any ideas? I tried changing permissions but no luck also tried mounting the 2nd hard drive within a directory in /home1. Still gives the error.
Today we are going to conduct a detailed study of RAIDability of contemporary 400GB hard drives on a new level. We will take two "professional" drives from Seagate and Western Digital and four ordinary "desktop" drives for our investigation. The detailed performance analysis and some useful hints on building RAID arrays are in our new detailed article.
I have a couple of Dell 1950s and in one of them, I have 2x Seagate 15K.5s that I purchased through Dell and I also have a spare sitting in my rack in case one goes bad, also from Dell.
I was going to be repurposing one of my other 1950s and was going to get two more 15K.5s for it, but wasn't planning on getting them through Dell (rip off?). This way, could still keep the same spare drive around in case a drive went bad in that system as well.
When I was talking to my Dell rep recently when purchasing another system, their hardware tech said you can't use non-Dell drives with Dell drives in the same RAID array because of the different firmware between them.
Anyone know if it is true? Anyone have any experience with using drives from Dell in conjunction with the same model drives from a third party retailer?
currently running a SAN which has 1TB... I would like to add another 1TB to the SAN to mirror the first set and use it for a 2nd server. What's the best way I can do this?
Gmail is sending duplicated emails to our server. The time stamps would differ about 10-20 minutes for each same email and usually would duplicate up to 10 copies.
how do I go about creating the same user with the same id on different linux boxes so when i share a mount folder, it has the permission to write and read properly?
I'm tying to assign nameservers to my new server in whm.
I am trying to do ns1.mydomain.com and ns2.mydomain.com. I would like to manually choose which IPs are given to each nameserver, but WHM is doing it automatically and selecting an internal IP for one.
- uploaded on host 1 at dedicated IP 111.111.111.111
- and also uploaded at host 2 (backup host) at dedicated IP 222.222.222.222
The dns A-record constantly points at host 1 (IP 111.111.111.111); in case that host fails, I manually switch the dns A-record to host 2 (IP 222.222.222.222).
Being dedicated IPs, I can simply type them in my browser's address window, and I see the index page of my website.
So, in fact, my site can be accessed via 3 urls: my_site.com, 111.111.111.111 and 222.222.222.222.
The question is: will that get me into trouble with Google and other search engines that may see there a duplicate content at 3 different urls and penalize me for that? If yes, how can I avoid it?
We are having some problems with a Foundry Bigiron 4000.
The hardware config is as following:
- Bigiron 4000 chassis
- 2x B8GMR3-A management (active + standby)
- 2x B24E
Once every couple of days now, we get the following error in syslog:
Code: 2009-10-05 20:40:00User.Warning8x.xx.50.1Oct 5 20:39:59 gateway IP: IP: Duplicate IP address 8x.xx.38.1 detected sent from MAC address 0004.d3ea.e200 interface 3/13, 1 packets, first packet received at time 1 days 20 hours 41 minutes 37 seconds since bootup!............
we have a subdomain blog.ourdomain.com that we installed wordpress on to publish content for our static website. We were short of time so we set up Comment kahuna to publish articles in the spaces between our posts (bad idea we now know).
Our page rank has stayed at PR2 for over 2 years.
Now - We have moved to a cms that has a blog included and wish to start blogging on that platform (fresh new regular content).
We cannot transfer all the posts to the new platform and why would we as it is duplicate content.
Problems if we change the subdomain to the new blog we will generate about 110 pages of 404 errors as all the pages are indexed from the old blog.
if we leave the subdomain as is we can htaccess all the old urls to the front page of the new blog (we do not know the .htaccess syntaxt to do this so any ideas) existing subdomain is apache, new system hosted at different ip on windows server and is SAAS no access to iis.
Issues -What will happen to our PR if we remove duplicate content but create the 404 errors
Should we just redirect the subdomain to the new blog and be patient?
I already have a web account with a shared web host. My site is growing. I want to buy a new account with a different web host but I'm afraid that the servers will be slower (the specs are better, but maybe it has more sites hosted on it or they are dishonest etc.?).
So, when I buy the new hosting account, can I simply copy and paste my site over and see which server serves the page faster? Then I should be able to decide which server to associate the domain name with...
After updating our server from plesk 11.5.30 to 12.0.18, one of our subscribers is receiving duplicate emails, a varying number anywhere between 5-15 of the same message!
Running plesk 12.0.18 on a CentOS 6.4 Cloud Server
This is a clean installation of Plesk, nothing else has been done on the server. After the Plesk 12 Installation I installed the Route53 Extension directly from the Panel.
I authenticated with the Access ID / Secret key, as soon as I start creating Domains I get duplicated zones in Route53. When I delete the Domain from Plesk only one Domain gets deleted, the other one remains.
This is my debug log where I see it executes the script twice:
