c2c-oerpscenario team mailing list archive

[xrg <xrg@xxxxxxxxx>]

On Wednesday 24 November 2010, you wrote:
> that's why
> https://blueprints.launchpad.net/openobject-server/+spec/database-handling-
> serverside exists.

Yes, I agree with the blueprint.

The idea of passing the whole database chunk through a RPC chunk has been 
flawed by design. It is bound to fail one day, and a bad administrator (by 
Murphy's law) will not notice that until he really tries to restore the db. 

That's why I advise to avoid that method.

> why let/ask all the admins to reinvent the wheel.

Exactly. Postgres itself and the filesystem of the server provide so many nice 
tools to backup a server. Why replicate them inside OpenERP?

-- 
If an external filestore is used for document management, database backup does not include the backup of the attachments
https://bugs.launchpad.net/bugs/478186
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.

Status in OpenObject Server: Opinion

Bug description:
attachments are stored in
openobject-server/bin/filestore/<dbname>
a backup just takes a copy of the database content , not of the attachments

so the cylce backup/restore looses data.
especially tricky if postgres-db and openerp-server run on different computers.

absolute minimum requirement is to add this information to the backup menu
* Backup Database (without attachments)
* Restore Database (without attachments)
help="Attachments are stored in openobject-server/bin/filestore/<dbname> and must be backuped separately"

a better solution would be of course to include the attachments in the backup/restore process (which IMHO has to be redesigned to use a storage location on the server and avoid transfer of mass data to and from the client.)