-
Bug
-
Resolution: Duplicate
-
Major
-
None
-
2.13.0 GA, 2.14.0 GA
-
3
-
False
-
None
-
False
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
-
-
API CCS Sprint 38 (3Scale), API CCS Sprint 39 (3Scale), API CCS Sprint 40 (3Scale)
The current restoring command for zync-database restores data to a wrong database ( to the default postgres database ). The command must point zync_production database.
Step 4 of 9.5.4.1. Template-based deployments
oc rsh $(oc get pods -l 'deploymentConfig=zync-database' -o json | jq -r '.items[0].metadata.name') bash -c 'psql -f ${HOME}/zync-database-backup'
should be:
oc rsh $(oc get pods -l 'deploymentConfig=zync-database' -o json | jq -r '.items[0].metadata.name') bash -c 'psql zync_production -f ${HOME}/zync-database-backup'
And step 5 of 9.5.4.2. Operator-based deployments
oc rsh $(oc get pods -l 'deploymentConfig=zync-database' -o json | jq -r '.items[0].metadata.name') bash -c 'psql -f ${HOME}/zync-database-backup'
should be:
oc rsh $(oc get pods -l 'deploymentConfig=zync-database' -o json | jq -r '.items[0].metadata.name') bash -c 'psql zync_production -f ${HOME}/zync-database-backup'
- duplicates
-
THREESCALE-7550 Add documentation about how to scale down pods and then how to scale up after system restoration
-
- Closed
-
- is related to
-
THREESCALE-8575 Rename the section for "3scale Backup and Restore using templates"
-
- Documenting
-
