Skip to main content
Druva Documentation

About servers, administrative group, and backup sets

Phoenix Editions: File:/tick.png Business File:/cross.png Enterprise File:/tick.png Elite

Before you configure registered servers for backup, it is important to understand steps of configuration. When you configure a File server, you:

  • Attach the server to an administrator group.
  • Create a backup set and attach it to the server.

Server

The server (or the registered server), is the system that hosts your files and folders with Phoenix agent installed. The server is registered with the organization that you select.

Administrative group

An administrative group is a logical categorization of servers that share something in common. For example, servers located in one region can belong to one group. Similarly, servers having the same operating system can belong to a different group.

An administrative group allows you to organize your servers for better management. To manage the servers under a group, you assign a group administrator. It is mandatory that you create an administrative group and attach servers to it.

Backup set

A backup set defines the following:

  • Backup content: What data to back up?
  • Backup policy: When to back up the data and for how long to retain the backed up data?

When you configure a server for backup, you create a backup set and attach it to the server. For files and folders as a workload, at the time of creating the backup set you:

  • Select the backup set type.
    Here, you select Files.
  • Select the storage location.
  • Create a content rule, which specifies the file and folders on a server you want to back up.
  • Specify the backup schedule in the backup policy.
  • Define the retention period in the backup policy.

After you add a backup set to the server, the server is configured for backup and the agent automatically backs up files and folders based on the content rule and backup policy. You can create multiple backup sets for a server.

Backup content

The backup content in the backup set specifies what should be backed up. You can define the data to back up as the content rule or custom content. When you create a content rule, you choose file types and folders. By default, Phoenix provides a content rule that already includes certain file types and folders that you can use. The following screenshot depicts a sample content rule created to backup all folders on the server.

Content_Rule_All.PNG

In addition, you can create a custom content, and save it with a name so that you can use it later in other backup sets that you create. Once a custom content is defined for a server, you cannot reuse it for another server until you save it. The following screenshot depicts a sample content rule created to backup all folders on the server.

Custom_Content_All.PNG

Backup policy

A backup policy specifies when a backup job is executed for a server, bandwidth available to the agent, and for how long a snapshot or log backup is retained. For File servers, backup policies define:

  • When a backup job is triggered.
  • The bandwidth available for the agent to execute a backup job.
  • The period for which a snapshot is retained. 
  • Pre and post custom script settings.

Configure a server

If you are configuring your first server, you have to attach the following entities to the registered server:

  1. Administrative group
  2. Backup set
    1. Storage
    2. Content rule
    3. Backup policy

The administrative groups, backup sets, and backup policies that you create are specific to the organization under which you register your server. When you configure a server, Phoenix lets you create a new administrative group and backup policy. You can also create administrative groups, content rules, and backup policies in advance and use them when you configure servers for backup.