Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Good day all,
I have a forum running on Slack 14 using apache, PHP, and mysql what I would like to do is have a second server on the network and mirroring the primary Server and allow me 2 options from there.
1: the ability to switch to this secondary server should something happen to the first
2: Share incoming load to both servers,
is there a way to implement either one or both of these features? and can someone help me get on track to doing the same?
I'm assumng you only have one server at the moment and that your forum uses php and MySQL.
The issue will be with the database, you'll have to ensure that you have correct MySQL replication and that your forum supports a master/slave environment. Alternatively you could point both instances of your forum at the one host and then switch to using the replicated database manually if you have a problem.
Also note that if you want to load balance across servers and your forum allows uploads you'll have to take care of them in some way or another, either by storing them in the database or ensuring your forum software can rsync to a remote server as part of the upload.
With more information on your choice of forum software I could give you some more pointers.
Thank You for that great information TenTenths, My Server is Slackware 14 and I am running a phpbb board on it, at the moment it is one server, but as the userbase grows I would like to have a backup system that is a direct mirror of the one online should something happen, and just as a matter of redundancy I would also like to mirror the site, on another machine offsite, should something happen, (Lost connection, Power failure etc..) I was thinking through some sort of cron script, I could make all the servers sync to the master at regular intervals and then probably include in the script a databse backup of the master system and an immediate restore on the slave systems to keep everything up to date? not sure if that could work?
If you're looking for a backup server rather than load balancing then it becomes easier. Your ideas about cron scripting are correct.
For your actual website/attachments/etc.
Use a cron rsync of your website folder, can do this as often as you want, but probably every 15 minutes would be OK. Exclude website log files and anything you don't specifically need.
Database has other options
MySQL replication - Good: Database is up to date. Bad: If a query breaks your database then your backup database will also get broken.
MySQL dump - Good: Can store this on the local and backup server and only read it in to your backup when you need it. Bad: Will be out of date by however long you leave between dumps.
MySQL replication with nightly dump done on backup server. - Best option, that way you have an up to date database and you have older backups to "roll-back" to.