[GeoNode-users] Resilient hosting of GeoNode
alessio.fabiani at geo-solutions.it
Fri May 25 05:00:30 PDT 2018
I'd suggest the backup and restore procedure of GeoNode, which dumps almost
everything you need and restores it also. (it is worth to do tests first
with a dev version, mostly on the restore procedure)
You can use a bash script like this to perform the backups
And a script like this to perform the restore
The settings must be customized for both prod and dev. On the above example
I put them into a backup folder, and they look more or less like this
Things to notice on the settings are:
1. GeoServer Data Dir must be accessible and writable by the Tomcat user
daemon and the user running the script. Also you need to provide correct
path in both cases, prod and dev
2. apps and dumps must be aligned (dumps are just the names of the dump
files); you can customize the apps modules as you need, accordingly on what
you want to backup/restore
2018-05-25 13:47 GMT+02:00 Carol Kraemer <ckraemer at itos.uga.edu>:
> Nifty idea, Jac. Thank you for sharing here and I’d be interested to hear
> the solution as well.
> *From:* geonode-users [mailto:geonode-users-bounces at lists.osgeo.org] *On
> Behalf Of *Jac Steiner
> *Sent:* Thursday, May 24, 2018 5:54 PM
> *To:* geonode-users <geonode-users at lists.osgeo.org>
> *Subject:* [GeoNode-users] Resilient hosting of GeoNode
> I'm working with a government that presently has a GeoNode instance
> installed locally and accessible publicly from the internet. This is
> fragile due to infrastructure weaknesses on premises (e.g. unreliable
> power). I'm considering recommending they move to an instance of GeoNode
> installed in the cloud (perhaps AWS, but a managed solution would be
> ideal). This instance would be locally mirrored on site using their current
> hardware. The local mirror is essential redundancy to accommodate scenarios
> where the internet may go down (e.g. emergency management). The local
> mirror should remain relatively in-sync with the cloud master, but
> infrequent synching, perhaps once a day, should sufficiently cover the
> anticipated usage patterns.
> I figure the devil is in the details here, as in a genuine emergency, if
> the internet is down and changes are being made locally directly on the
> mirror, once internet is back, the synching strategy with the master
> suddenly gets complicated.
> I'm not able to find examples of this type of setup in the docs or
> otherwise. As I'm not a sys admin, I may be using the wrong search terms.
> Can someone point me toward resources that provide further details on
> implementing this type of strategy and best practices? If anyone has
> additional relevant insights they can share, I'd greatly appreciate it.
> Appreciate your help.
> geonode-users mailing list
> geonode-users at lists.osgeo.org
GeoServer Professional Services from the experts! Visit http://goo.gl/it488V
for more information.
Ing. Alessio Fabiani
Via di Montramito 3/A - 55054 Massarosa (LU) - Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 331 6233686
Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE
2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
precisa che ogni circostanza inerente alla presente email (il suo
contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
operazione è illecita. Le sarei comunque grato se potesse darmene notizia.
This email is intended only for the person or entity to which it is
addressed and may contain information that is privileged, confidential or
otherwise protected from disclosure. We remind that - as provided by
European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
e-mail or the information herein by anyone other than the intended
recipient is prohibited. If you have received this email by mistake, please
notify us immediately by telephone or e-mail.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the geonode-users