Skip to content

Commit 22c5a47

Browse files
committed
fix
1 parent 4a75f24 commit 22c5a47

File tree

1 file changed

+12
-9
lines changed

1 file changed

+12
-9
lines changed

use-timescale/backup-restore.md

Lines changed: 12 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -70,8 +70,6 @@ You can have one cross-region backup per $SERVICE_SHORT. To change the region of
7070

7171
## Create a point-in-time recovery fork
7272

73-
<Availability products={['cloud']} />
74-
7573
<PitrIntro />
7674

7775
You initiate a point-in-time recovery from a same-region or cross-region backup in $CONSOLE_LONG:
@@ -123,21 +121,26 @@ You initiate a point-in-time recovery from a same-region or cross-region backup
123121

124122
<Tab title="Tiger Cloud on Azure" label="azure-cloud">
125123

126-
$CLOUD_LONG automatically handles backup for your $SERVICE_LONGs using the `pgBackRest` tool. You don't need to perform backups manually. $CLOUD_LONG creates one full backup every week, and incremental backups every day in the same region as your $SERVICE_SHORT.
124+
$CLOUD_LONG provides comprehensive backup and recovery solutions to protect your data, including automatic daily backups and point-in-time recovery.
127125

128-
On [$SCALE and $PERFORMANCE][pricing-and-account-management] $PRICING_PLANs, you can check the list of backups for the previous 14 days in $CONSOLE_LONG. To do so, select your $SERVICE_SHORT, then click `Operations` > `Backup and restore` > `Backup history`.
126+
## Automatic backups
127+
128+
$CLOUD_LONG automatically handles backup for your $SERVICE_LONGs using the `pgBackRest` tool. You don't need to perform
129+
backups manually.
130+
131+
$CLOUD_LONG automatically creates one full backup every week, and incremental backups every day in the same region as
132+
your $SERVICE_SHORT. Additionally, all [Write-Ahead Log (WAL)][wal] files are retained back to the oldest full backup.
133+
This means that you always have a full backup available for the current and previous week:
129134

130-
Additionally, all [Write-Ahead Log (WAL)][wal] files are retained back to the oldest full backup. This means that you always have a full backup available for the current and previous week:
135+
![Backup in Tiger Cloud](https://assets.timescale.com/docs/images/database-backup-recovery.png)
131136

132-
![Backup in Tiger](https://assets.timescale.com/docs/images/database-backup-recovery.png)
137+
On [$SCALE and $PERFORMANCE][pricing-and-account-management] $PRICING_PLANs, you can check the list of backups for the previous 14 days in $CONSOLE_LONG. To do so, select your $SERVICE_SHORT, then click `Operations` > `Backup and restore` > `Backup history`.
133138

134139
In the event of a storage failure, a $SERVICE_SHORT automatically recovers from a backup
135140
to the point of failure. If the whole availability zone goes down, your $SERVICE_LONGs are recovered in a different zone. In the event of a user error, you can [create a point-in-time recovery fork][create-fork].
136141

137142
## Create a point-in-time recovery fork
138143

139-
<Availability products={['cloud']} />
140-
141144
<PitrIntro />
142145

143146
You initiate a point-in-time recovery in $CONSOLE_LONG:
@@ -150,7 +153,7 @@ You initiate a point-in-time recovery in $CONSOLE_LONG:
150153
1. Select the recovery point, ensuring the correct time zone (UTC offset).
151154
1. Configure the fork.
152155

153-
![Create recovery fork](https://assets.timescale.com/docs/images/tiger-cloud-console/create-recovery-fork-tiger-cloud.png)
156+
![Create recovery fork](https://assets.timescale.com/docs/images/tiger-cloud-console/create-recovery-fork-tiger-console.png)
154157

155158
You can configure the compute resources, add an HA replica, tag your fork, and
156159
add a connection pooler. Best practice is to match

0 commit comments

Comments
 (0)