Reportportal: In reference to data migration #992

Created on 5 Jun 2020  路  4Comments  路  Source: reportportal/reportportal

@DzmitryHumianiuk , I followed the steps provided in https://github.com/reportportal/reportportal/issues/992

  1. Backed-Up PostgreSQL DB data. -- Using docker exec -t your-db-container pg_dumpall -c -U postgres > dump_date +%d-%m-%Y"_"%H_%M_%S.sql

  2. Restoring db with new instance -- Using cat your_dump.sql | docker exec -i your-db-container psql -U postgres -d your-db-name

But I see multiple error as shared in screenshot below.
picturemessage_krtkdzc4 cqd

What am I missing?

help wanted

Most helpful comment

@priyankachaturvedi30
hosting of a new instance of reportportal on Server B creates database with initial scheme.
You have to deploy only postgres. Restore it, and after that deploy with docker-compose.

All 4 comments

Your database is not clear. You need to restore backup to absolutely clear and fresh db.

@pbortnik : How do I check that the new instance of db is fresh. I just hosted the new instance of reportportal on Server B using : docker-compose -p reportportal up -d --force-recreate. After all the services were up and running I just tried to restore db in the postgres container just created using - cat your_dump.sql | docker exec -i your-db-container psql -U postgres -d your-db-name

@priyankachaturvedi30
hosting of a new instance of reportportal on Server B creates database with initial scheme.
You have to deploy only postgres. Restore it, and after that deploy with docker-compose.

It worked. Thanks @pbortnik

Was this page helpful?
0 / 5 - 0 ratings