makeplane
[feature]: Implementing a Comprehensive Data Recovery Mechanism for Plane
Is there an existing issue for this?
- [X] I have searched the existing issues
Summary
Firstly, I would like to express my gratitude for the dedication you've shown in developing Plane, a project management system that boasts a sleek interface and user-centric functionalities. It is evident that a great deal of thought and effort has been invested in crafting a tool that aims to streamline project management processes.
However, during my usage, I've encountered a significant limitation within the system that I believe warrants urgent attention. Currently, Plane offers the functionality to export workspace or project data in various formats such as CSV, Excel, or JSON. While this feature is undeniably useful for data analysis or reporting purposes, I've realized that there lacks a counterpart facility for data importation or restoration.
The ability to export data without a corresponding method for seamless data restoration or importation places the system at a critical disadvantage. In scenarios such as migration, system failures, or accidental data deletion, the absence of a straightforward data recovery mechanism raises concerns regarding data integrity and operational reliability. From a user's perspective, this gap in functionality can render the system less dependable for critical project management needs.
Therefore, I humbly request the consideration of this feature: the implementation of a comprehensive data recovery mechanism. This mechanism should not only allow users to import previously exported data seamlessly but also provide detailed documentation or guidelines on how to effectively utilize this feature.
The introduction of such a feature would drastically enhance the system's reliability, giving users the confidence that their data can be safely backed up and restored. This reassurance is paramount for any software solution handling essential project management tasks, as it directly influences decision-making and the overall trust in using the system for business-critical operations.
Thank you very much for considering my request. I am hopeful that addressing this issue will elevate Plane's standing as a robust and reliable project management tool. I am looking forward to your positive response and am excited to see how Plane will continue to evolve and meet the dynamic needs of its user base.
Why should this be worked on?
If this issue remains unaddressed, lacking a robust data recovery system renders Plane unreliable and unfit for any user reliant on steadfast project management solutions.
I tried to recover project data by restoring the database, but the experience was terrible. It was completely unusable with persistent internal errors.
@RenderCoder I've been facing the same issue here but I am using Plane self-hosted (Docker).
I found out that we can dump PostgreSQL (plane-db) to a .sql file and back up the plane-uploads volume to a .tar file. These two files can restore the whole Plane service.
I have tried backing up and restoring it many times, and it seems to work without any issues.
@RenderCoder I've been facing the same issue here but I am using Plane self-hosted (Docker).
I found out that we can dump PostgreSQL (plane-db) to a .sql file and back up the plane-uploads volume to a .tar file. These two files can restore the whole Plane service.
I have tried backing up and restoring it many times, and it seems to work without any issues.
I also use the Self Host version and have tried the method you mentioned. I found that I couldn't restore it on platforms like Railway.app. How did you operate? Does the newly created Plane service need to go through an initialization process?
@RenderCoder I've been facing the same issue here but I am using Plane self-hosted (Docker). I found out that we can dump PostgreSQL (plane-db) to a .sql file and back up the plane-uploads volume to a .tar file. These two files can restore the whole Plane service. I have tried backing up and restoring it many times, and it seems to work without any issues.
I also use the Self Host version and have tried the method you mentioned. I found that I couldn't restore it on platforms like Railway.app. How did you operate? Does the newly created Plane service need to go through an initialization process?
make sure plane docker is running...
Backup Database .sql:
docker exec -i YOUR_PLANE_DB_COTAINER_NAME pg_dump --dbname=postgresql://plane:plane@plane-db/plane -c > PATH_TO_BACKUP/dump.sql
Bakup uploads files:
docker run --rm -v YOUR_PLANE_UPLOADS_COTAINER_NAME:/volume -v PATH_TO_BACKUP/:/backup ubuntu tar cvf /backup/plane-app_uploads.tar /volume > /dev/null 2>&1
make sure plane docker is running...
Restore database:
docker cp PATH_TO_BACKUP/dump.sql YOUR_PLANE_DB_COTAINER_NAME:/dump.sql && docker exec -i YOUR_PLANE_DB_COTAINER_NAME psql postgresql://plane:plane@plane-db/plane -f /dump.sql
Restore uploads files:
docker run --rm -v YOUR_PLANE_UPLOADS_COTAINER_NAME:/volume -v PATH_TO_BACKUP/:/backup alpine tar xf /backup/plane-app_uploads.tar --strip-component=1 -C /volume
Feel free to check out my solution: https://github.com/zhgchgli0718/plane-docker-example/tree/main/backup
@RenderCoder I've been facing the same issue here but I am using Plane self-hosted (Docker). I found out that we can dump PostgreSQL (plane-db) to a .sql file and back up the plane-uploads volume to a .tar file. These two files can restore the whole Plane service. I have tried backing up and restoring it many times, and it seems to work without any issues.
I also use the Self Host version and have tried the method you mentioned. I found that I couldn't restore it on platforms like Railway.app. How did you operate? Does the newly created Plane service need to go through an initialization process?
make sure plane docker is running...
Backup Database .sql:
docker exec -i YOUR_PLANE_DB_COTAINER_NAME pg_dump --dbname=postgresql://plane:plane@plane-db/plane -c > PATH_TO_BACKUP/dump.sqlBakup uploads files:
docker run --rm -v YOUR_PLANE_UPLOADS_COTAINER_NAME:/volume -v PATH_TO_BACKUP/:/backup ubuntu tar cvf /backup/plane-app_uploads.tar /volume > /dev/null 2>&1make sure plane docker is running...
Restore database:
docker cp PATH_TO_BACKUP/dump.sql YOUR_PLANE_DB_COTAINER_NAME:/dump.sql && docker exec -i YOUR_PLANE_DB_COTAINER_NAME psql postgresql://plane:plane@plane-db/plane -f /dump.sqlRestore uploads files:
docker run --rm -v YOUR_PLANE_UPLOADS_COTAINER_NAME:/volume -v PATH_TO_BACKUP/:/backup alpine tar xf /backup/plane-app_uploads.tar --strip-component=1 -C /volume
This worked for me. You saved me some good time so thank you! 🙏
@RenderCoder I've been facing the same issue here but I am using Plane self-hosted (Docker).
I found out that we can dump PostgreSQL (plane-db) to a .sql file and back up the plane-uploads volume to a .tar file. These two files can restore the whole Plane service.
I have tried backing up and restoring it many times, and it seems to work without any issues.
I also use the Self Host version and have tried the method you mentioned. I found that I couldn't restore it on platforms like Railway.app. How did you operate? Does the newly created Plane service need to go through an initialization process?
make sure plane docker is running...
Backup Database .sql:
docker exec -i YOUR_PLANE_DB_COTAINER_NAME pg_dump --dbname=postgresql://plane:plane@plane-db/plane -c > PATH_TO_BACKUP/dump.sql
Bakup uploads files:
docker run --rm -v YOUR_PLANE_UPLOADS_COTAINER_NAME:/volume -v PATH_TO_BACKUP/:/backup ubuntu tar cvf /backup/plane-app_uploads.tar /volume > /dev/null 2>&1
make sure plane docker is running...
Restore database:
docker cp PATH_TO_BACKUP/dump.sql YOUR_PLANE_DB_COTAINER_NAME:/dump.sql && docker exec -i YOUR_PLANE_DB_COTAINER_NAME psql postgresql://plane:plane@plane-db/plane -f /dump.sql
Restore uploads files:
docker run --rm -v YOUR_PLANE_UPLOADS_COTAINER_NAME:/volume -v PATH_TO_BACKUP/:/backup alpine tar xf /backup/plane-app_uploads.tar --strip-component=1 -C /volume
This worked for me. You saved me some good time so thank you! 🙏
You could actually use the latest version of Plane, which provides new, native backup and restore scripts.