fix(docs): few fixes after Pete's rewrite

Signed-off-by: Fatih Acar <[email protected]>

Author: fatih-acar

docs/docs/guides/database-backup.mdx

@@ -26,19 +26,24 @@ This guide shows you how to create comprehensive backups of your Infrahub deploy
 Install the infrahubops CLI tool:
 
 ```bash
-curl -L https://github.com/opsmill/infrahub-ops-cli/releases/latest/download/infrahubops-$(uname -s)-$(uname -m) -o infrahubops
+curl https://infrahub.opsmill.io/ops/$(uname -s)/$(uname -m) -o infrahubops
 chmod +x infrahubops
 ```
 
 </TabItem>
-<TabItem value="manual" label="Manual Process">
+<TabItem value="manual" label="Docker Compose">
 
 If you prefer manual control, proceed to backup each component individually as described in the following steps.
 
+</TabItem>
+<TabItem value="remote" label="Remote Database">
+
+Alternatively, you can use the [legacy tool](#using-the-python-based-backup-utility) to backup a remote Neo4j database.
+
 </TabItem>
 </Tabs>
 
-### Step 2: Backup the Neo4j database
+### Step 2: Backup the databases
 
 <Tabs groupId="backup-method">
 <TabItem value="infrahubops" label="infrahubops CLI" default>
@@ -62,7 +67,7 @@ Artifact storage backup is planned for future versions and must currently be han
 :::
 
 </TabItem>
-<TabItem value="docker" label="Docker Compose">
+<TabItem value="manual" label="Docker Compose">
 
 Connect to your Neo4j container and create a backup:
 
@@ -79,6 +84,14 @@ ls backups/
 # Output: neo4j-2025-03-24T19-57-18.backup
 ```
 
+Backup the Prefect PostgreSQL database containing task logs and execution history:
+
+```bash
+# Export Prefect database (using default credentials)
+docker compose exec -T task-manager-db \
+  pg_dump -Fc -U postgres -d prefect > prefect.dump
+```
+
 </TabItem>
 <TabItem value="remote" label="Remote Database">
 
@@ -119,27 +132,17 @@ For local filesystem storage, copy the artifact directory:
 
 ```bash
 # Copy artifacts directory to backup location
-cp -r /path/to/infrahub/artifacts /backup/artifacts/
+docker compose cp -r infrahub-server:/opt/infrahub/storage /backup/artifacts/
 ```
 
 </TabItem>
 </Tabs>
 
-### Step 4: Backup the task management database
-
-Backup the Prefect PostgreSQL database containing task logs and execution history:
-
-```bash
-# Export Prefect database (using default credentials)
-docker compose exec -T task-manager-db \
-  pg_dump -Fc -U postgres -d prefect > prefect.dump
-```
-
 ## Restore from backup
 
 ### Step 1: Prepare the environment
 
-Ensure Infrahub services are running before starting the restore process.
+Ensure Infrahub services are running before starting the restore process. You can start from a scratch/blank deployment.
 
 <Tabs groupId="restore-method">
 <TabItem value="infrahubops" label="infrahubops CLI" default>
@@ -167,12 +170,20 @@ If restoring manually, follow the steps below for each component.
 </TabItem>
 </Tabs>
 
-### Step 2: Restore the Neo4j database
+### Step 2: Restore the databases
 
 <Tabs groupId="restore-method">
-<TabItem value="docker" label="Docker Compose" default>
+<TabItem value="infrahubops" label="infrahubops CLI" default>
+
+This is automatically handled by infrahubops.
+
+</TabItem>
+<TabItem value="manual" label="Docker Compose">
 
 ```bash
+# Stop app services
+docker compose stop task-worker infrahub-server task-manager
+
 # Copy backup directory to container
 docker cp database-backup infrahub-database-1:/tmp/backup
 
@@ -199,6 +210,17 @@ CREATE DATABASE neo4j;
 SHOW DATABASES;
 ```
 
+Restore the task manager PostgreSQL database
+
+```bash
+# Restore Prefect database
+docker compose exec -T task-manager-db \
+  pg_restore -d postgres -U postgres --clean --create prefect.dump
+
+# Restart task manager to apply changes
+docker compose restart task-manager
+```
+
 </TabItem>
 <TabItem value="remote" label="Remote Database">
 
@@ -233,29 +255,28 @@ cp -r /backup/artifacts/ /path/to/infrahub/artifacts/
 </TabItem>
 </Tabs>
 
-### Step 4: Restore the task management database
-
-```bash
-# Restore Prefect database
-docker compose exec -T task-manager-db \
-  pg_restore -d postgres -U postgres --clean --create prefect.dump
+### Step 4: Restart Infrahub services
 
-# Restart task manager to apply changes
-docker compose restart task-manager
-```
+<Tabs groupId="restore-restart-services">
+<TabItem value="infrahubops" label="infrahubops CLI" default>
 
-### Step 5: Restart Infrahub services
+This is automatically handled by infrahubops.
 
+</TabItem>
+<TabItem value="manual" label="Docker Compose">
 Restart services in the correct order to ensure proper initialization:
 
 ```bash
 # Restart API servers first
-docker compose start infrahub-server
+docker compose restart infrahub-server
 
 # Then restart task workers
-docker compose start task-worker
+docker compose restart task-worker
 ```
 
+</TabItem>
+</Tabs>
+
 ## Validation
 
 Verify your restoration was successful:
@@ -302,6 +323,14 @@ If you're running Infrahub with a Neo4j cluster, follow these steps to backup fr
 Always run backup and restore commands as the `neo4j` user inside containers to avoid permission issues with data files.
 :::
 
+Example cluster topology
+
+| Node             | Role     |
+|------------------|----------|
+| `database`       | Leader   |
+| `database-core2` | Follower |
+| `database-core3` | Follower |
+
 ### Step 1: Create backup from a follower node
 
 ```bash

docs/docs/release-notes/infrahub/release-1_2_0.mdx

@@ -171,7 +171,7 @@ The top menu has also been made more compact, to provide a cleaner look.
 
 Users of Neo4j-enterprise and infrahub-enterprise already had the capability to backup the Neo4j database following the process in our [documentation](../../guides/database-backup.mdx).
 
-With Infrahub 1.2.0 there's a new requirement to also backup the PostgreSQL database that is used for Infrahub's internal task and event system. More information can be found in the [Database backup and restore guide](../../guides/database-backup.mdx#full-backup-and-restore-procedure).
+With Infrahub 1.2.0 there's a new requirement to also backup the PostgreSQL database that is used for Infrahub's internal task and event system. More information can be found in the [Database backup and restore guide](../../guides/database-backup.mdx#create-a-full-backup).
 
 ## Changelog