move instance types section up; setting-up-backup-device42-

Author: Nadia-JSch

docs/administration/appliance-manager/setting-up-backup-device42-appliance-manager.mdx

@@ -41,6 +41,16 @@ Configure the backup options for the Main Appliance and Remote Collectors (RCs).
 
 ![Run the backup](/assets/images/setting-up-backup-device42-appliance-manager/backup-now-form.png)
 
+### For Standby Instances
+
+Select the **Backup Meta Data** option when creating a Device42 instance for recovery or failover purposes. Selecting the metadata option copies all system identifiers, passphrases, certificates, and configuration settings – preparing the standby instance to fully replace your production instance when needed.
+
+The standby instance will have the same system identifiers as the production instance, which means it will connect as the primary instance. For this reason, keep one instance with the identifier data active at a time. See the [Warm HA Setup documentation](administration/appliance-manager/warm-ha-setup-failover-and-automated-backups.mdx) for failover procedures.
+
+### For Test Instances
+
+Do not select the **Backup Meta Data** option when creating test or development environments. Backing up and restoring this way is useful when you just want to recover your data, rather than replacing your production instance. The GUIDs will not be copied without the metadata option selected, and without these GUIDs, the machine cannot connect to external services or be used to replace the production instance.
+
 ### Remote Collector Options
 
 The following table summarizes the backup settings for the selected RC(s):
@@ -119,24 +129,6 @@ The **Region Endpoint** field **is not** simply the endpoint name, as each regio
 
 ![Backup using Amazon S3](/assets/images/setting-up-backup-device42-appliance-manager/s3-settings.png)
 
-## Back Up Different Instance Types
-
-Choose the appropriate backup configuration based on your use case for the instance:
-
-### For Standby Instances
-
-Select the **Backup Meta Data** option when creating a Device42 instance for recovery or failover purposes. Selecting the metadata option copies all system identifiers, passphrases, certificates, and configuration settings – preparing the standby instance to fully replace your production instance when needed.
-
-The standby instance will have the same system identifiers as the production instance, which means it will connect as the primary instance. For this reason, keep one instance with the identifier data active at a time. See the [Warm HA Setup documentation](administration/appliance-manager/warm-ha-setup-failover-and-automated-backups.mdx) for failover procedures.
-
-![Backup with meta data](/assets/images/setting-up-backup-device42-appliance-manager/with-meta-data.png)
-
-### For Test Instances
-
-Do not select the **Backup Meta Data** option when creating test or development environments. Backing up and restoring this way is useful when you just want to recover your data, rather than replacing your production instance. The GUIDs will not be copied without the metadata option selected, and without these GUIDs, the machine cannot connect to external services or be used to replace the production instance.
-
-![Backup without meta data](/assets/images/setting-up-backup-device42-appliance-manager/without-meta-data.png)
-
 ## Schedule the Backup
 
 You can create multiple backup schedules to automate the backup process. All fields are required.