Skip to content
This repository was archived by the owner on Nov 30, 2017. It is now read-only.
This repository was archived by the owner on Nov 30, 2017. It is now read-only.

sanity-test fail after migrating service instance data from old bucket to new bucket #25

Description

@ishwarps

Hi,
I need to move the some services data from my old bucket to new bucket. So i copy the following files from my old bucket.
1)dingo-postgresql-clusterdata-backup-k59e4ba3-a6db-4104-825d-f725ee6e55cd.json
2)backups/k59e4ba3-a6db-4104-825d-f725ee6e55cd/wal

I copy this above two files into the new s3 bucket and redeploying dingo-postgresql with new bucket. The dingo-postgresql is successfully deploy but sanity test its failing with following error.

test-storage> psql: could not connect to server: Connection refused
test-storage> Is the server running on host "10.0.124.12" and accepting
test-storage> TCP/IP connections on port 30007?
test-storage> Database still recovering
test-storage> Data was still in recovery after 300s
[stderr]

  • exec
    Errand 'sanity-test' completed with error (exit code 1)

Do i need to copy any other stuff?

Thanks in advanced.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions