Re: [WebDNA] backup / mirror website & databases
This WebDNA talk-list message is from 2018
It keeps the original formatting.
numero = 114195
interpreted = N
texte = 1798 Hi Ken, Very nice. I am setting up a backup data center at my home about 20 miles from the business that is located in an industrial area where tracker trailers are in and out constantly. Not uncommon for a driver to hit and pull down a power pole. Installed a backup generator years ago but last summer lightning hit a main verizon Fios hub and all internet was down in the area. Thanks! Steve On 04/20/2018 01:15 AM, Kenneth Grome wrote: > I'm currently setting up two servers for one of my clients, a main > server and a clone that I will call the backup server. They will > reside in different data centers, one East Coast, one West. > > I'll run a WebDNA script via trigger on the backup that flushes > dbs on the main, then duplicates the main dbs to a separate folder > every hour. Rsync then pulls the main dbs from this folder. > > If rsync can't connect to the main my script will text me. Then > I'll check to see if the main has gone down. If so I'll point my > DNS to the backup until the main is online again. > > Since the main is not expected to go down very often, an hour > offline for server switching and DNS propagation doesn't bother my > client, especially when I can implement this solution at low cost. > > The benefit are (1) constant backups in native file format, (2) a > backup that's ready to take over for the main 24/7, and (3) a > backup that's immune to physical disaster on the main. > > Regards, > Kenneth Grome > WebDNA Solutions > http://www.webdnasolutions.com > Web Database Systems and Linux Server Administration > > > >> In the past I've had 2 physical servers running. A primary and >> a backup. They were joined by Gluster so that in the event the >> primary went down for some reason the backup took over without >> the need of downtime to restore from the last nightly backup >> that would be missing current days activity. >> >> My 2 most powerful servers (16GB RAM & dual quad core >> processors) are getting old. I've recently upgraded drives to >> SSD's, replaced power supplies and batteries. I want to only >> have 1 powered up and the other to be a cold spare. >> >> I want to run 2 virutal web servers running on one physical >> server. One serving to the public and the other running and be >> an up to date copy and in the event something such as a hack >> occurred on the primary virtual server where I could just >> change the IP address in the router to send all web traffic to >> the backup server's IP. >> >> I would like to have rsync run once every hour so the process >> time will be minimal and the most data that would be lost would >> be the last hour. Then after the 1:00AM rsync have a script >> create a tar backup file of the directories and databases >> located on the backup server to a directory on a NAS as the >> days backup. > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list talk@webdna.us > To unsubscribe, E-mail to: talk-leave@webdna.us > archives: http://www.webdna.us/page.dna?numero=55 > Bug Reporting: support@webdna.us -- Steve Raslevich --------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list talk@webdna.us To unsubscribe, E-mail to: talk-leave@webdna.us archives: http://www.webdna.us/page.dna?numero=55 Bug Reporting: support@webdna.us .
Associated Messages, from the most recent to the oldest:
1798 Hi Ken, Very nice. I am setting up a backup data center at my home about 20 miles from the business that is located in an industrial area where tracker trailers are in and out constantly. Not uncommon for a driver to hit and pull down a power pole. Installed a backup generator years ago but last summer lightning hit a main verizon Fios hub and all internet was down in the area. Thanks! Steve On 04/20/2018 01:15 AM, Kenneth Grome wrote: > I'm currently setting up two servers for one of my clients, a main > server and a clone that I will call the backup server. They will > reside in different data centers, one East Coast, one West. > > I'll run a WebDNA script via trigger on the backup that flushes > dbs on the main, then duplicates the main dbs to a separate folder > every hour. Rsync then pulls the main dbs from this folder. > > If rsync can't connect to the main my script will text me. Then > I'll check to see if the main has gone down. If so I'll point my > DNS to the backup until the main is online again. > > Since the main is not expected to go down very often, an hour > offline for server switching and DNS propagation doesn't bother my > client, especially when I can implement this solution at low cost. > > The benefit are (1) constant backups in native file format, (2) a > backup that's ready to take over for the main 24/7, and (3) a > backup that's immune to physical disaster on the main. > > Regards, > Kenneth Grome > WebDNA Solutions > http://www.webdnasolutions.com > Web Database Systems and Linux Server Administration > > > >> In the past I've had 2 physical servers running. A primary and >> a backup. They were joined by Gluster so that in the event the >> primary went down for some reason the backup took over without >> the need of downtime to restore from the last nightly backup >> that would be missing current days activity. >> >> My 2 most powerful servers (16GB RAM & dual quad core >> processors) are getting old. I've recently upgraded drives to >> SSD's, replaced power supplies and batteries. I want to only >> have 1 powered up and the other to be a cold spare. >> >> I want to run 2 virutal web servers running on one physical >> server. One serving to the public and the other running and be >> an up to date copy and in the event something such as a hack >> occurred on the primary virtual server where I could just >> change the IP address in the router to send all web traffic to >> the backup server's IP. >> >> I would like to have rsync run once every hour so the process >> time will be minimal and the most data that would be lost would >> be the last hour. Then after the 1:00AM rsync have a script >> create a tar backup file of the directories and databases >> located on the backup server to a directory on a NAS as the >> days backup. > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list talk@webdna.us > To unsubscribe, E-mail to: talk-leave@webdna.us > archives: http://www.webdna.us/page.dna?numero=55 > Bug Reporting: support@webdna.us -- Steve Raslevich --------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list talk@webdna.us To unsubscribe, E-mail to: talk-leave@webdna.us archives: http://www.webdna.us/page.dna?numero=55 Bug Reporting: support@webdna.us .
webdna
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
ReturnRaw (1999)
Database Strategy - more... (1998)
WebCat2: Found Items syntax, etc. (1997)
Secure server question (1997)
Redirect and passing more than one variable... (2002)
WebDNA 6 (2004)
WebCat2 - Getting to the browser's username/password data (1997)
[shownext] and sort (1998)
Formulas.db / Quantity Discount problem (1998)
Multiple catalog databases and showcart (1997)
Grouping search fields, etc. (1997)
[SEARCH] Context for SKU prices not working... (1998)
File Uploads... (1997)
popups, netscape vs explorer (1997)
Search Criteria (2000)
Exclamation point (1997)
[LOOKUP] (1997)
Dismissing dialogs (was 2.1b3 --> way slow) (1997)
orders being printed (1998)
replace using &append=T (2007)