Backup Disaster Recovery Plan

[tarik]

What you suggest and what is best in practice for backup disaster recovery plan solution.

For example Linux Vps or dedicated mail server with DA and all the things..

1. JetBackup or something else...
2. Or some standby server with synced data that can be easily switched to.
3. rd something else...

p.s. and what is the best process for that cases imagine we have vps1 - main server, vps2 - backup server. And vps1 is down. Should we than take new vps like vps3 to be used (for backup restoration) instead of vps1, or will do restoration from backup server to vps1 instead...

What should be done exactly in steps, what are the best practice cases for that scenarios and also mention the post stuffs like handling with IP/DNS stuffs later after recovery etc... to be nice understandable.

Thanks in advance!

 

[Zhenyapan]

All depends on your SLA. sometimes easier to keep config backups on separate DC and reinstall server from scratch with this configs.
Sometimes you must use doubled online config. There is no one solution for everyone.

 

[Richard G]

Linux Vps

Since you say VPS, maybe regular snapshots?

Should we than take new vps like vps3 to be used instead of vps1.

If that is installed 100% exactly the same way and updated, then mit might be one of the options, however, if will take some downtime to change the nameserver ip's or if you're running external nameservers, then changing DNS ip's of the VPS.
However then I didn't even talk about rDNS records, SSL certificates, SPF records and such.

Like @Zhenyapan said, there is not a single solution for everyone, there are multiple options.

 

[jamgames2]

If you want to be easy lifes.

Directadmin admin backup have options to restore with generate new dns records.

example of VPS3
1. launch vps that already prepare directadmin.
2. restore with admin backup without keeping old records.
3. change ns record in your domains provider panel for pointer to new IPs.

Please note, if you restore with keeping dns records. Directadmin don't have tool to change possible records value like SPF, some of custom TXT record thst use to be value server IPs, ..etc..

 

[tarik]

All depends on your SLA. sometimes easier to keep config backups on separate DC and reinstall server from scratch with this configs.
Sometimes you must use doubled online config. There is no one solution for everyone.

Thanks @Zhenyapan , for "Config Backups" what you actually mean, like only server configuration and control panel (DA) with blank data, or full backup of primary server with all data ?

What is "doubled" online config ?

Thanks in advance!

​

 

[tarik]

If you want to be easy lifes.

Directadmin admin backup have options to restore with generate new dns records.

example of VPS3
1. launch vps that already prepare directadmin.
2. restore with admin backup without keeping old records.
3. change ns record in your domains provider panel for pointer to new IPs.

Please note, if you restore with keeping dns records. Directadmin don't have tool to change possible records value like SPF, some of custom TXT record thst use to be value server IPs, ..etc..

@jamgames2

thanks yes i understand, good!

 

[tarik]

Since you say VPS, maybe regular snapshots?


If that is installed 100% exactly the same way and updated, then mit might be one of the options, however, if will take some downtime to change the nameserver ip's or if you're running external nameservers, then changing DNS ip's of the VPS.
However then I didn't even talk about rDNS records, SSL certificates, SPF records and such.

Like @Zhenyapan said, there is not a single solution for everyone, there are multiple options.

thanks dear @Richard G , yes practice and testing is the best to test many solutions and options! thanks all

 

[Zhenyapan]

"Config Backups"

depends on your servers content - you can backup your customized versions and configs only, just to know wnat to install on new server if that will crash.

"doubled" online

when you have two online servers and both working and serving requests, if any crashes - load-balancer moves all requests to alive one.