linux - Backing up (and restoring) a Plone instance -
I have a plan installation in my home directory under Linux i ~ / Plone
. It was created from the deputy distribution of the plan from its website. So Plone compiled his dragon and it has been bundled with Zope.
Please tell me which files are required to backup:
- 1) Backup all data
- 2a) Restore back-up data in strong> same version , but is located elsewhere.
- 2b)
I thought that maybe it's a good idea to back up the entire ~ / backup, Plone / The zinstance directory, but I see thousands of files of
/ home / me / Plone /...//>, even the file
zinstance / var / filestorage / Data.fs Given
(!!!) Can this be true?
I have received the resource , but it is not specific enough.
is the only directory that usually contains variables data var / directory (data, logfile). Parts / * will be generated again, for example.
And even simple, usually you only need to back up the var / filestorage / Data.fs
file: your "ZODB" database in one All your data is with data, if you have a new plan, then there may be a var / blobstorage /
directory to store large files (PDF, MP3, etc.): One even back up
Restoring to a new instance only means copying Data.fs (and possibly BloboStorage files). It does not matter if the example is on new or server or such
two big warnings :
-
If I say that I copy my server data to my regular hard disk for a secure test. "Just backup the data .fs file", I'm assuming that you can rebuild your example, in particular you can install any add-on product that is basically: use buildout.cfg ( Recently consider a plan version) and fix a config file back as well.
-
"Copying Data.fs": Better Bin / Reso script to handle your backup, it can handle an augmented backup (you wish) and it will be on your data site Can safely backup The easiest to add to your buildout, which gives you one of the all the necessary options, the
bin / backup
script.
See also
Comments
Post a Comment