Federated Repository
What Is a Federated Repository?
How Does a Federated Repository Work?
How Many Members Can Be Added to a Federated Repository?
What Is a Federated Repository?
NAKIVO Backup & Replication supports creating a Federated repository to be used as a destination for new and existing backup/backup copy jobs, backup export, or backup migration. Also, the federated repository can be used as a source for recovery or backup copy jobs. With this feature, existing backup repositories with identical values for their data storage type attribute can be combined into a federated repository. These federated repositories are scaled horizontally to consume multiple backup repositories (federated repository members). Thus, backup/backup copy jobs can continue to run even if one of the members is unavailable or has insufficient storage space. You can use a local folder, NFS share, or CIFS share type of backup repository to create a federated repository.
Important
The Federated repository feature supports backing up data to Incremental with full backups repositories only.
How Does a Federated Repository Work?
When you create a federated repository, the Director creates this federated repository consisting of one or more federated repository members. When you assign this federated repository as a target for new or existing backup/backup copy jobs, backup export, or backup migration, during the job run, the Director determines and assigns an available federated repository member with sufficient storage space to store the backup data.
A federated repository can also be used as a source for recovery and/or replication jobs from backup.
The Federated repository feature supports the following backup location policy:
-
Integrity: All dependent recovery points are stored within a single federated repository member.
To use federated repository members (on NFS and CIFS shares or local folders) in your data protection workflows, follow these steps:
-
Create and set up a federated backup repository.
-
Select the federated repository as a destination for new or existing backup/backup copy jobs.
-
Select the federated repository as a source for recovery or backup copy jobs, as a source for replication from backup jobs.
How Many Members Can Be Added to a Federated Repository?
The maximum recommended number of members assigned to one federated repository is 128. Members of the same federated repository can use different Transporters, and they must be of the Incremental with full backups repository type. The maximum total number of members in all federated repositories is 500 (1 member in each federated repository).
If needed, federated repository members can be managed/refreshed individually or added/removed to/from the federated backup repository.
Note
You cannot simultaneously select:
The members that support immutability and contain at least one immutable object or are associated with job(s) configured to create an immutable recovery point(s) and
The members that do not support immutability.
Selecting one type of member disables the member(s) of the other type.