-
Notifications
You must be signed in to change notification settings - Fork 370
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problem with backups #3050
Comments
When restoring ive go a lot of errors, is it normal ? ERROR: relation "index_urls_on_url_token" already exists Now i can find the pushes created on other instances, its good but i have all theses errors because of things already existing on main instance |
I tried with a ph_dump et pg_restore, it works better, i clean database every time I retrieve a backup ! |
Hi @TomHeim29,
Yeah these seem like warnings when you are importing into a DB with pre-existing data. pg_restore should be done into a clean/empty DB. I think if these errors come up, the records aren't imported.
This is likely because of the above but could also be because of expiration... What are you trying to do? Sync multiple instances/databases? |
juste instance a db into another instance, it finaly worked with that : sudo sh -c 'docker exec postgres pg_dump -Fc -U user db > backup.dump' restore backup : sudo cat backup.dump | sudo docker exec -i postgres pg_restore --clean --if-exists -U user -d db |
Checklist
issues
.discussions
.❓ Question
Hi !
I followed https://docs.pwpush.com/docs/database-backup/#automate-the-backup-optional to set up backups. But i can't recover pushes created earlier.
I tried to create a push then export sql database et inject it bacdk into another instance. Can't access to the push created anymore. Do you know if I am following the correct way to backup my pwpush instance ?
The text was updated successfully, but these errors were encountered: