Full backup - Klaros Test Management - Forum - Klaros-Testmanagement
Full backup
Nicolas Plessis, geändert vor 13 Jahren.
Full backup
Youngling Beiträge: 10 Beitrittsdatum: 01.03.11 Neueste Beiträge
Hi,
I'm trying to automate a full backup of klaros, the export in xml isn't really an option in my case
For information, i use a ubuntu 10.04 / postgres setup.
Data:
- dump postgres db: pg_dump klaros > /tmp/klaros-backup.sql
- Attachements are in: /opt/klaros-testmanagement/webapps/*
- Properties: /root/.klaros
Optional:
- Conf: /opt/klaros-testmanagement (optional cause it's more easy to reinstall the core from scratch and then import backups)
If you can confirm that my backup logic makes sense
By the way, why attachement are in the webapps folder instead of data in ~/.klaros/ ?
Thank you.
I'm trying to automate a full backup of klaros, the export in xml isn't really an option in my case
For information, i use a ubuntu 10.04 / postgres setup.
Data:
- dump postgres db: pg_dump klaros > /tmp/klaros-backup.sql
- Attachements are in: /opt/klaros-testmanagement/webapps/*
- Properties: /root/.klaros
Optional:
- Conf: /opt/klaros-testmanagement (optional cause it's more easy to reinstall the core from scratch and then import backups)
If you can confirm that my backup logic makes sense
By the way, why attachement are in the webapps folder instead of data in ~/.klaros/ ?
Thank you.
Torsten Stolpmann, geändert vor 13 Jahren.
RE: Full backup
Jedi Council Member Beiträge: 759 Beitrittsdatum: 12.02.09 Neueste Beiträge
Hi Nicolas,
This is almost correct.
For a full backup you would need to dump your database (as shown above) and include the filesystem under /home/<klarosUserAccount>/.klaros which contains your settings *and* the attachment repository. If you use Derby as a database this folder would also include the database.
The attachment files you see in your webapps folder are temporary files which sometimes do not get deleted due to locking issues in the UI framework we are using. This is confusing and we are still investigating the reasons.
From Klaros Version 3.3 upward these temporary upload files will be created in the /tmp folder instead, so leftover files should no longer be an issue there.
There is no reason to backup the /opt/klaros-testmanagement folder as it contains only distribution or temporary files.
Otherwise the backup solution you propose is the correct way to do this and is the recommended preparation in case of an application update.
Hope this helps.
Torsten
Data:
- dump postgres db: pg_dump klaros > /tmp/klaros-backup.sql
- Attachements are in: /opt/klaros-testmanagement/webapps/*
- Properties: /root/.klaros
- dump postgres db: pg_dump klaros > /tmp/klaros-backup.sql
- Attachements are in: /opt/klaros-testmanagement/webapps/*
- Properties: /root/.klaros
This is almost correct.
For a full backup you would need to dump your database (as shown above) and include the filesystem under /home/<klarosUserAccount>/.klaros which contains your settings *and* the attachment repository. If you use Derby as a database this folder would also include the database.
The attachment files you see in your webapps folder are temporary files which sometimes do not get deleted due to locking issues in the UI framework we are using. This is confusing and we are still investigating the reasons.
From Klaros Version 3.3 upward these temporary upload files will be created in the /tmp folder instead, so leftover files should no longer be an issue there.
There is no reason to backup the /opt/klaros-testmanagement folder as it contains only distribution or temporary files.
Otherwise the backup solution you propose is the correct way to do this and is the recommended preparation in case of an application update.
Hope this helps.
Torsten
Nicolas Plessis, geändert vor 13 Jahren.
RE: Full backup
Youngling Beiträge: 10 Beitrittsdatum: 01.03.11 Neueste Beiträge
Perfect, thank you Torsten !