---
title: "Backing Up the CTERA Portal Servers and Storage"
slug: "backing-up-the-ctera-portal-servers-and-storage-4"
tags: ["Portal", "8.3"]
updated: 2025-06-18T14:00:01Z
published: 2025-06-18T14:00:01Z
canonical: "kb.ctera.com/backing-up-the-ctera-portal-servers-and-storage-4"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://kb.ctera.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Backing Up the CTERA Portal Servers and Storage

To back up the CTERA Portal servers and storage you need to use third-party recovery tools.

          **Note**

          

If the storage fails and you need to use the backup storage, you need to change the definition of the [storage node](/v1/docs/adding-and-editing-storage-nodes-5-1) to point to the backup storage bucket in the CTERA Portal.

For the CTERA Portal database backup, see [Configuring the CTERA Portal Database for Backup](/v1/docs/configuring-ctera-portal-database-for-backup-and-restore-3).

Using third-party tools can result in a recovery of the storage after a disaster not being consistent with the portal database with the storage recovery being either older or newer than the portal database recovery, which is described in [Configuring CTERA Portal Database for Backup and Restore](/v1/docs/configuring-ctera-portal-database-for-backup-and-restore-3).

If the storage recovery is older than the database, it can be missing some recent blocks. In this situation, you should rollback the portal database to an earlier point-in-time that matches the storage recovery.

If the storage recovery is newer than the portal database, since deleted blocks are kept for a minimum of 30 days and these blocks are never modified, as long as the portal database is no more than 30 days older, there will be no data loss.

          **Note**

          

Running CTERA FSCK is usually recommended following a disaster recovery. CTERA FSCK must be run only with approval from CTERA support.