This issue focuses on testing the restoration procedures for PostgreSQL, Storage Account, and API Management within the at21 environment to ensure reliability and data integrity. The goal is to validate each restore scenario, document any issues, and confirm that all services are correctly restored.
Components Involved
PostgreSQL Flexible Server
Azure Storage Account
Azure API Management
Test Scenarios
Below are the specific restore scenarios to test for each component:
1. PostgreSQL
Restore from Within PostgreSQL Flexible Server:
[x] Initiate a restore within PostgreSQL Flexible Server, creating a new server with a unique server name.
[x] Verify that the new PostgreSQL Flexible Server instance is created successfully.
[x] Confirm that all data, tables, and configurations are restored accurately in the new server.
[x] Delete the original PostgeSQL server and do an restore back to the original server name.
[ ] Confirm that apps using this PostgreSQL Flexible Server is able to access data.
Restore PostgreSQL Flexible Server using Backup Vault`:
[x] Delete PostgreSQL server and recreate the server with Terraform
[x] Use Backup Vault and pg_restore to restore databases and tables into the target server.
[x] Verify that all tables and indexes are restored accurately.
[x] Verify with Terraform that server have the correct permission/settings after restore.
[x] Test data consistency by running sample queries.
[x] Confirm user roles, permissions, and configurations are intact.
[ ] Confirm that apps using this PostgreSQL Flexible Server is able to access data.
2. Azure Storage Account
Blob Storage:
[ ] Verify the integrity of blob backups in the designated container.
[ ] Delete data
[ ] Restore blobs to the target container within the at21 environment.
[ ] Confirm that restored blobs are accessible and intact.
[ ] Test dependent applications to ensure they function with the restored blob data.
File Share:
[ ] Verify the integrity of file share backups.
[ ] Delete data
[ ] Restore file shares to the designated location within the at21 environment.
[ ] Confirm that restored files and directories are accessible and correctly structured.
[ ] Test dependent applications to ensure they function with the restored file share data.
3. Azure API Management (APIM)
[x] Verify backup file and configuration settings.
[x] Delete the APIM resource and recreate APIM using Terraform
[x] Restore APIM configuration to ensure policies, APIs, and settings are recovered.
[x] Confirm that all APIs are accessible and functioning as expected.
[x] Test dependent applications for uninterrupted service.
Expected Outcome
Each component should be restored successfully without data loss or configuration discrepancies. All tests should pass, confirming that services are fully functional post-restore.
Additional Notes
Ensure logs are reviewed for any restore-related errors or warnings.
Description
This issue focuses on testing the restoration procedures for PostgreSQL, Storage Account, and API Management within the
at21environment to ensure reliability and data integrity. The goal is to validate each restore scenario, document any issues, and confirm that all services are correctly restored.Components Involved
Test Scenarios
Below are the specific restore scenarios to test for each component:
1. PostgreSQL
Restore from Within PostgreSQL Flexible Server:
Restore PostgreSQL Flexible Server using Backup Vault`:
Backup Vaultandpg_restoreto restore databases and tables into the target server.2. Azure Storage Account
Blob Storage:
at21environment.File Share:
at21environment.3. Azure API Management (APIM)
Expected Outcome
Each component should be restored successfully without data loss or configuration discrepancies. All tests should pass, confirming that services are fully functional post-restore.
Additional Notes