Hi List,
I’m curious - what do people do to back up their data directory? Do you back up everything or just a select few files/folders?
Myself I’d like to back up everything except the data itself (that being /coverages, /data and /gwc), but there’s an issue with the /gwc directory. Not only does it include tiles (which I don’t want to backup), it also includes configuration information for GWC (geowebcache.xml and geowebcache-diskquota.xml) which I do want to backup.
For the purposes of ease-of-backup, ideally the data would be in a completely different directory structure from the configuration files. But failing that, I think it’d be very useful to put the GWC config files outside of the /gwc directory so that directory could just be ignored.
Does anyone else have thoughts on this?
Jonathan
This transmission is intended for the named addressee(s) only and may contain sensitive or protectively marked material up to RESTRICTED and should be handled accordingly. Unless you are the named addressee (or authorised to receive it for the addressee) you may not copy or use it, or disclose it to anyone else. If you have received this transmission in error please notify the sender immediately. All email traffic sent to or from us, including without limitation all GCSX traffic, may be subject to recording and/or monitoring in accordance with relevant legislation.
I usually change the default data dir configuration.
For integrated GeoWebCache, as you suggested, a good approach could be
to select an external folder for tiles and configuration. I usually
also try to avoid to store the tiles in the same filesystem where data
are stored.
For raster and shapefiles also it is good avoiding to store them
inside the default path. Sample datasets, shipped with GeoServer, are
there for simplicity but it is not a good idea to use the default
folder to store your actual data.
2013/3/4 Jonathan Moules <jonathanmoules@anonymised.com>:
Hi List,
I'm curious - what do people do to back up their data directory? Do you
back up everything or just a select few files/folders?
Myself I'd like to back up everything except the data itself (that being
/coverages, /data and /gwc), but there's an issue with the /gwc directory.
Not only does it include tiles (which I don't want to backup), it also
includes configuration information for GWC (geowebcache.xml and
geowebcache-diskquota.xml) which I do want to backup.
For the purposes of ease-of-backup, ideally the data would be in a
completely different directory structure from the configuration files. But
failing that, I think it'd be very useful to put the GWC config files
outside of the /gwc directory so that directory could just be ignored.
Does anyone else have thoughts on this?
Jonathan
This transmission is intended for the named addressee(s) only and may
contain sensitive or protectively marked material up to RESTRICTED and
should be handled accordingly. Unless you are the named addressee (or
authorised to receive it for the addressee) you may not copy or use it, or
disclose it to anyone else. If you have received this transmission in error
please notify the sender immediately. All email traffic sent to or from us,
including without limitation all GCSX traffic, may be subject to recording
and/or monitoring in accordance with relevant legislation.
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
helps if you read the entire Email. Me in that case...
This above mentioned data directory has only database connections.
The file-based data are only few and somewhere else because their update
cycle differs to the DB and styles. That is done with a similar script that
runs monthly.
The tiles are also in a different directory again, because there is no
update rhythm. There are mostly imagery tiles and when we have new imagery I
cut new tiles and then I back-up.
I suppose this is how most production installations operate and why I keep
these three store types separate. Depending on the size of your stores you
may decide whether it is a good way to separate or not. Stuffing everything
in one directory back this up and knowing that all is there has its
advantages too.
Cheers
Christian
-----
____________________________
Dr Christian Maul
Project Manager
Information Services Branch
Department of Sustainability and Environment
Level13, Marland House, 570 Bourke Street
Melbourne 3000
Thanks for the replies both.
I wasn’t aware the GWC tiles could be placed elsewhere; I’ll have to investigate that.
We don’t actually have anything in our /data directory and the content of /coverages can be placed anywhere.
I think what I’ll end up doing is segregating the remaining data from the configuration files and then backing up the configs daily using something like Christian’s script.
Cheers,
Jonathan
helps if you read the entire Email. Me in that case…
This above mentioned data directory has only database connections.
The file-based data are only few and somewhere else because their update
cycle differs to the DB and styles. That is done with a similar script that
runs monthly.
The tiles are also in a different directory again, because there is no
update rhythm. There are mostly imagery tiles and when we have new imagery I
cut new tiles and then I back-up.
I suppose this is how most production installations operate and why I keep
these three store types separate. Depending on the size of your stores you
may decide whether it is a good way to separate or not. Stuffing everything
in one directory back this up and knowing that all is there has its
advantages too.
Cheers
Christian
Dr Christian Maul
Project Manager
Information Services Branch
Department of Sustainability and Environment
Level13, Marland House, 570 Bourke Street
Melbourne 3000
Sent from the GeoServer - User mailing list archive at Nabble.com.
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb
This transmission is intended for the named addressee(s) only and may contain sensitive or protectively marked material up to RESTRICTED and should be handled accordingly. Unless you are the named addressee (or authorised to receive it for the addressee) you may not copy or use it, or disclose it to anyone else. If you have received this transmission in error please notify the sender immediately. All email traffic sent to or from us, including without limitation all GCSX traffic, may be subject to recording and/or monitoring in accordance with relevant legislation.