Skip to content

Commit 364e690

Browse files
committed
fix(docs): switch to infrahub-backup
Signed-off-by: Fatih Acar <[email protected]>
1 parent 1e04bcb commit 364e690

File tree

1 file changed

+13
-13
lines changed

1 file changed

+13
-13
lines changed

docs/docs/guides/database-backup.mdx

Lines changed: 13 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -21,13 +21,13 @@ This guide shows you how to create comprehensive backups of your Infrahub deploy
2121
### Step 1: Install the backup tool
2222

2323
<Tabs groupId="backup-method">
24-
<TabItem value="infrahubops" label="infrahubops CLI (Recommended)" default>
24+
<TabItem value="infrahubops" label="infrahub-backup CLI (Recommended)" default>
2525

26-
Install the infrahubops CLI tool:
26+
Install the infrahub-backup CLI tool:
2727

2828
```bash
29-
curl https://infrahub.opsmill.io/ops/$(uname -s)/$(uname -m) -o infrahubops
30-
chmod +x infrahubops
29+
curl https://infrahub.opsmill.io/ops/$(uname -s)/$(uname -m)/infrahub-backup -o infrahub-backup
30+
chmod +x infrahub-backup
3131
```
3232

3333
</TabItem>
@@ -46,12 +46,12 @@ Alternatively, you can use the [legacy tool](#using-the-python-based-backup-util
4646
### Step 2: Backup the databases
4747

4848
<Tabs groupId="backup-method">
49-
<TabItem value="infrahubops" label="infrahubops CLI" default>
49+
<TabItem value="infrahubops" label="infrahub-backup CLI" default>
5050

5151
Create a backup of your running Infrahub instance:
5252

5353
```bash
54-
./infrahubops backup create
54+
./infrahub-backup create
5555
```
5656

5757
The tool automatically:
@@ -145,12 +145,12 @@ docker compose cp -r infrahub-server:/opt/infrahub/storage /backup/artifacts/
145145
Ensure Infrahub services are running before starting the restore process. You can start from a scratch/blank deployment.
146146

147147
<Tabs groupId="restore-method">
148-
<TabItem value="infrahubops" label="infrahubops CLI" default>
148+
<TabItem value="infrahubops" label="infrahub-backup CLI" default>
149149

150150
Restore from a backup archive:
151151

152152
```bash
153-
./infrahubops backup restore infrahub_backup_20250129_153045.tar.gz
153+
./infrahub-backup restore infrahub_backup_20250129_153045.tar.gz
154154
```
155155

156156
The tool automatically:
@@ -173,9 +173,9 @@ If restoring manually, follow the steps below for each component.
173173
### Step 2: Restore the databases
174174

175175
<Tabs groupId="restore-method">
176-
<TabItem value="infrahubops" label="infrahubops CLI" default>
176+
<TabItem value="infrahubops" label="infrahub-backup CLI" default>
177177

178-
This is automatically handled by infrahubops.
178+
This is automatically handled by infrahub-backup.
179179

180180
</TabItem>
181181
<TabItem value="manual" label="Docker Compose">
@@ -258,9 +258,9 @@ cp -r /backup/artifacts/ /path/to/infrahub/artifacts/
258258
### Step 4: Restart Infrahub services
259259

260260
<Tabs groupId="restore-restart-services">
261-
<TabItem value="infrahubops" label="infrahubops CLI" default>
261+
<TabItem value="infrahubops" label="infrahub-backup CLI" default>
262262

263-
This is automatically handled by infrahubops.
263+
This is automatically handled by infrahub-backup.
264264

265265
</TabItem>
266266
<TabItem value="manual" label="Docker Compose">
@@ -570,7 +570,7 @@ This process restores only data, not cluster roles, replication, or configuratio
570570
### Using the Python-based backup utility
571571

572572
:::info Legacy Tool
573-
The Python-based utility (`utilities/db_backup`) is still available in the main Infrahub repository but is being replaced by infrahubops. Use it only if infrahubops doesn't meet your specific requirements.
573+
The Python-based utility (`utilities/db_backup`) is still available in the main Infrahub repository but is being replaced by infrahub-backup. Use it only if infrahub-backup doesn't meet your specific requirements.
574574
:::
575575

576576
### Use non-default ports

0 commit comments

Comments
 (0)