Managing Server From A Distance
![](https://seccdn.libravatar.org/avatar/d8293474d284267a56f1d5510d82b219.jpg?s=120&d=mm&r=g)
Hi, everyone, We're working on a project where we would be placing a machine loaded with Suse 8.0 to act as a web server within a server farm at our contractor's location. The contractor has several Sun Solaris machines, and we're touting our idea as a way in which they can experiment with Open Source without changing their current setup until they see how ours works. They will provide connectivity to the internet and physical security as well as their firewall. We would maintain the machine remotely. The website it would be running is an ecommerce site running on Apache/PHP/MySql. We expect that traffic will be in the neighborhood of 10,000 users per day. We feel that once we have the machine up and running, sysadmin tasks could be run remotely. But we know that to do this right, we need to think very hard about the best ways to configure everything to minimize problems in the future. We expect that the machine will be a 1.something GHz Pentium processor with a gig of ram and two (or three) 40GB hard drives. The unique data on the primary hard drive would be backed up periodically (probably on an hourly basis) to the secondary drive(s). What are some of the issues we need to consider here? The most immediate concerns we can think of are of a calamitous nature: what happens when the machine has an unforeseen restart and files on the primary drive are corrupted? Can we remotely instruct the machine to boot from the secondary drive? Does anyone else have any (probably hard-won) wisdom on this and other issues we need to be thinking about? With many thanks in advance, Nick
participants (1)
-
Nick Selby