Skip to content

Commit e7a9e5a

Browse files
authored
Merge branch 'main' into lio/just-simply
2 parents e4bd5d7 + 87b3074 commit e7a9e5a

File tree

2 files changed

+22
-1
lines changed

2 files changed

+22
-1
lines changed

docs/concepts/managed-storage/managed-postgres.md

Lines changed: 11 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -72,7 +72,17 @@ For a smoother experience with Defang, we recommend using Postgres 14 for your c
7272

7373
```
7474

75-
<!--
75+
## Final Snapshots
76+
77+
When a project is deployed to a production environment any managed postgres instances are automatically configured to create a snapshot of the database before deletion. The snapshot will be named with the following format
78+
79+
`
80+
<project-name>-<service>-postgres-<id>-final-snapshot
81+
`
82+
83+
The AWS Console can be used to restore a snapshop into a new instance of postgres.
84+
85+
<!--
7686
### Major Version Updating of Engine
7787
7888
To update the database engine you can update the image to a later version in your compose file and apply it via ```defang compose up --provider=aws```. In the example below, we change from Postgres 15 to 16.

docs/concepts/managed-storage/managed-redis.md

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -29,3 +29,14 @@ cache:
2929
- mode: host
3030
target: 6379
3131
```
32+
33+
## Final Snapshots
34+
35+
When a project is deployed with the `production` [deployment mode](/docs/concepts/deployment-modes) any managed redis instances are automatically
36+
configured to create a snapshot of the datastore before deletion. The snapshot will be named with the following format
37+
38+
`
39+
<project-name>-<service>-redis-<id>-final-snapshot
40+
`
41+
42+
The AWS Console can be used to restore a snapshop into a new instance of redis.

0 commit comments

Comments
 (0)