• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

emergency preparedness

michaellunsford

Regular Pleskian
We had an issue over the weekend where an ISP's router was down for 32 hours. This made our plesk server unreachable for the duration.

I was curious to hear opinions on creating a remote fail-safe server with duplicate client information. Like a secondary name server that would point folks to the secondary location, should the first be unreachable.

Three obvious problems present themselves.

The first is the plesk license. Since this is a "backup" that should only duplicate existing data, would I be required to purchase a second (duplicate) plesk license to maintain legal status? Is it even necessary to load plesk on the fail-safe server?

Second problem: how to properly transfer the information from one location to the other. Since these two boxes should reside behind two completely different networks, transferring data from one to the other will drink up some bandwidth. Is there an "incremental" backup that would take up less space?

Third: This idea uses the plesk boxes as the actual name servers. This would certainly simplify matters. However, I can't help but think this may cause some other unforeseen consequences.

Are there more complications I may be unaware of? email? ftp? Thanks for any help or insight!
 
Back
Top