Skip to main content

 

Druva Documentation

Configuration FAQs

General configuration FAQs

► How do I get started with using Phoenix?
Phoenix is easy to set up. You only need to perform a few, quick steps to get your setup ready. To see the chronology that you must follow, see Phoenix setup process. For a full set of instructions for setting up Phoenix for your file servers, see Initial configuration of file servers. To know how you can set up Phoenix for your SQL servers, see Introduction to Phoenix for SQL servers.
► What is a Phoenix agent?
Phoenix agent is a component of the Phoenix solution that you can deploy locally. It communicates with Phoenix Master for backing up and restoring data. To enable backup and restore of server data, you must install and activate Phoenix agents on the servers that you want to back up. You do not require separate agent installers for file servers and SQL servers. The Phoenix agent installers are designed to identify the type of server. That is why you can use the same installer for installations across file servers as well as SQL servers.  
► Do I require separate agent installers for file servers and SQL servers?
No, you do not. Phoenix agents can identify the type of a server at the time of an installation. That is why you do not require separate installers for file servers and SQL servers.
► What is Phoenix Cloud? 
Phoenix Cloud comprises cloud storage to which your server data is saved.
► Can I install Phoenix agents first, and then register servers?
At the time of registering servers, Phoenix generates an activation token. You must use this activation token to activate Phoenix agents on your servers. You can also use third-party tools such as Microsoft SCCM for mass installation and activation. However, you must have the activation token for activating Phoenix agents. The order does not matter; you can choose to register servers first and then install Phoenix agents. Alternatively, you can install Phoenix agents first, and then register servers. However, to obtain the activation token for activating Phoenix agents, you must register your File servers or SQL servers. 
► Where can I find the Phoenix agent installer?
The Phoenix agent installer is available at http://downloads.druva.com/phoenix/.
Because the Phoenix agent installer is server-aware, it identifies the type of a server at the time of installation. That is why you need not maintain separate installers for file servers and SQL servers.
You can also download the installer from the Phoenix Management Console at the time of registering servers.
► How do I activate Phoenix agents? 
To enable backup and restore of server data, you must install and activate Phoenix agents on the servers that you want to back up.
► Can I mass deploy Phoenix agents?
You can use a third-party script such as Microsoft System Center Configuration Manager for installing and activating Phoenix agents. However, we do not provide scripts for configuring the file servers or SQL servers on which Phoenix agents reside. You must configure each server from the Phoenix Master Management Console.
► How much free space do I need on my servers?
You must ensure that the free space at locations where Phoenix agent configuration details, logs, and metadata reside is at least 1% of the size of the data that you want to back up. To know where Phoenix agent logs and configuration details are available, see Phoenix agent configuration and log files
► What files can I see on the primary partition where I installed Phoenix agent?
You can expect to see the application data (the configuration file and the logs) under your primary partition. If you choose to install Phoenix agent on your primary partition, both the installation directory and the application data will reside on the primary partition.
► What is an activation token? How many do I need?
An activation token is generated at the time of registering servers. It performs a one-time authentication for validating Phoenix agent connections to Phoenix Master. You can use an activation token to activate as many Phoenix agents as you want. We recommend that you generate only those many tokens that you plan to use. We also recommend that you use a single token to activate servers that share something in common. For example, you might want to use a token to activate all servers that are geographically co-located. To better manage activation tokens, delete the tokens that you have not used for activating Phoenix agents. 
To know more, see Manage activation tokens
► Does Phoenix store my activation tokens?
No, Phoenix has no access to your activation tokens. However, Phoenix uses a string of digits to identify your token. Your token appears as a string of multiple instances of asterisk (*) on the Phoenix Management Console. 
► I deleted some activation tokens. What happens to backups from my servers?
An activation token only performs a one-time authentication of Phoenix agents. It does not interfere with backups. If you deleted some tokens, backups from your servers will continue as usual. 

File server configuration FAQs

► Why do I need a backup policy for my file servers? 
Backup policies are rules that define the type of data for backup, and the schedule for data backup. You should create backup policies, and attach them to server groups. This ensures that backups from servers belonging to the server group starts according to the backup policies. To know more about backup policies, see About File server backup policies
► Do you have best practices for creating backup policies?
Yes, we do. For more information, see About File server backup policies. However, for an exact configuration of backup policies that is suitable for your servers, contact the Druva Support team (support@druva.com).
​​​​​​​​​​​​​​► Can I set bandwidth as a percentage value?
No, you cannot specify bandwidth as a percentage value. You can only specify bandwidth in Mbps at the time of creating a backup policy.
​​​​​​​​​​​​​​► What default files does a backup policy exclude from backup?
By default, Phoenix excludes some system files and folders from backups, for example, the Recycle Bin. This ensures a faster backup experience. To see the list the files that Phoenix excludes, see Default folder exclusions.
​​​​​​​​​​​​​​► Can I browse through my folder list while selecting folders for backup?
No, you cannot browse through the folder library. Instead, you must manually type the path to the folders that you want to back up. To include or exclude files, you must select the default file types, and if required, type the extensions of the files that you want to include or exclude. 
​​​​​​​​​​​​​​► What time zone does the backup schedule follow?
The backup schedule follows the time zone of the Phoenix agent. For example, if you set the schedule such that backups start at 8 AM, Phoenix agents located in New York will start backup at 8 AM EDT and Phoenix agents located in California will start backups at 8 AM PST, respectively.
​​​​​​​​​​​​​​► What is a server group? How does it help me?
A server group is a logical categorization of servers that share something in common. For example, servers located in one region can belong to a server group. Similarly, servers having the same operating system can belong to one server group. After you create a server group, you must attach a backup policy to the server group. This ensures that backups from servers belonging to this server group starts according to the backup policy. To know more about server groups, see About server groups
​​​​​​​​​​​​​​► Do you have best practices for creating server groups?
Yes, we do. To know more, see About server groups.  However, for an exact configuration of server groups best-suited for your environment, contact the Druva Support team (support@druva.com).
​​​​​​​​​​​​​​► Can I create separate schedules for each server in a server group?
No, you cannot. You can attach only one backup policy to a server group. Backups from all servers belonging to this server group follow the rules defined by this backup policy. If you want to assign different rules to different servers, consider creating a separate server group for each set of servers that share a set of rules. 
​​​​​​​​​​​​​​► Can I adjust bandwidth on a server-level?
No, you cannot adjust bandwidth at a server-level. However, you can adjust the bandwidth that you assign to a server group by configuring the backup policy attached to this server group. Servers inherit the bandwidth settings from the server groups to which they belong. If you want to assign a different bandwidth value for a single server, create a server group, and assign this server to the server group. You can then attach a backup policy with the required bandwidth value to this server group.
​​​​​​​​​​​​​​► Can I assign more than one backup policy to a server group?
No, you cannot. However, you can detach a backup policy from a server group, and attach a new backup policy to the group. 
​​​​​​​​​​​​​​► Can I use the same token to activate a Windows server and a Linux server?
Yes, you can. However, we recommend that you use a single token to activate servers that share something in common. For example, you might want to use a token to activate all servers that are geographically co-located.
​​​​​​​​​​​​​​► When do I need to consider a reconfiguration of my file servers?
If you want to change the server group to which servers are assigned, you can consider a reconfiguration. You might also consider reconfiguring a server if you want to assign a different backup policy to the server. 

​​​​​​​SQL server configuration FAQs

​​​​​​​► Why do I need a backup policy for my SQL servers? 
Backup policies are rules that define the type of data for backup, the type of backup, and the schedule for data backup. You should create backup policies, and attach them to server groups. This ensures that backups from servers belonging to the server group starts according to the backup policies. To know more about backup policies, see About SQL server backup policies
​​​​​​​​​​​​​​► Do you have best practices for creating backup policies for SQL servers?
Yes, we do. For more information, see About SQL server backup policies. However, for an exact configuration of backup policies that is suitable for your servers, contact the Druva Support team.
​​​​​​​​​​​​​​► Can I set bandwidth as a percentage value?
No, you cannot specify bandwidth as a percentage value. You can only specify bandwidth in Mbps at the time of creating a backup policy.
​​​​​​​​​​​​​​► How do I know what databases and instances are backed up?
By default, Phoenix backs up all instances and the databases within these instances except for tempDB. However, you can exclude the databases that you do not want to back up at the time of creating a backup policy.
​​​​​​​​​​​​​​► Which time zone does the backup schedule follow?
The backup schedule follows the time zone of the Phoenix agent. For example, if you set the schedule such that backups start at 8 AM, Phoenix agents located in New York will start backup at 8 AM EDT and Phoenix agents located in California will start backups at 8 AM PST, respectively.
​​​​​​​​​​​​​​► Why do I need a server group?
A server group is a logical categorization of servers that share something in common. For example, servers located in one region can belong to a server group. Similarly, servers having the same operating system can belong to one server group. After you create a server group, you must attach a backup policy to the server group. This ensures that backups from servers belonging to this server group starts according to the backup policy. To know more about server groups, see About server groups
​​​​​​​​​​​​​​► Do you have best practices for creating server groups for SQL servers?
Yes, we do. To know more, see About server groups. However, for an exact configuration of server groups best-suited for your environment, contact the Druva Support team.
​​​​​​​​​​​​​​► Can I create different schedules for SQL servers in a server group?
No, you cannot. You can attach only one backup policy to a server group. Backups from all servers belonging to this server group follow the rules defined by this backup policy. If you want to assign different rules to different servers, consider creating a separate server group for each set of servers that share a set of rules. 
​​​​​​​​​​​​​​► Can I create different schedules for different databases?
No, you cannot. You can attach only one backup policy to a server group. Backups of all the databases on the SQL servers that belong to this server group follow the rules defined by this backup policy. However, you can modify the backup policy as often as you want to include or exclude databases from backup. 
​​​​​​​​​​​​​​► Can I adjust bandwidth on a server-level?
No, you cannot adjust bandwidth at a server-level. However, you can adjust the bandwidth that you assign to a server group by configuring the backup policy attached to this server group. Servers inherit the bandwidth settings from the server groups to which they belong. If you want to assign a different bandwidth value for a single server, create a server group, and assign this server to the server group. You can then attach a backup policy with the required bandwidth value to this server group.
​​​​​​​​​​​​​​► Can I assign more than one backup policy to databases in a server group?
No, you cannot. However, you can detach a backup policy from a server group, and attach a new backup policy to the group. You can also consider modifying the existing policy to include or exclude databases from backup. 
​​​​​​​​​​​​​​► Can I use the same token to activate all my SQL servers?
Yes, you can. However, we recommend that you use a single token to activate servers that share something in common. For example, you might want to use a token to activate all SQL servers that are geographically co-located.
​​​​​​​​​​​​​​► When do I need to consider a reconfiguration of my SQL servers?
If you want to change the server group to which servers are assigned, you can consider a reconfiguration. You might also consider reconfiguring a server if you want to assign a different backup policy to the server. 

V​​​​​​​Mware configuration FAQs

​​​​​​​► What is backup proxy? 
Backup proxy is a virtual machine that you must deploy and register for backing up and restoring virtual machines in your VMware setup. Backup proxy contains Phoenix agent, the component that performs backup and restore of virtual machines. To know more, see Deploy Phoenix backup proxy.
​​​​​​​​​​​​​​► Why do I need a backup policy for my virtual machines? 
Backup policies are rules that define the schedule for data backup. You should create backup policies, and attach them to server groups. This ensures that backups from servers belonging to the server group starts according to the backup policies. To know more about backup policies, see About VMware backup policies
​​​​​​​​​​​​​​► Do you have best practices for creating backup policies?
Yes, we do. For more information, see Best Practices to create a Backup Policy. However, for an exact configuration of backup policies that is suitable for your virtual machines, contact the Druva Support team.
​​​​​​​​​​​​​​► Can I set bandwidth as a percentage value?
No, you cannot specify bandwidth as a percentage value. You can only specify the bandwidth in Mbps at the time of creating a backup policy. 
​​​​​​​​​​​​​​► What does Phoenix backup?
By default, Phoenix backs up VMDK files and VMX files. However, only VMDK files are available for restore. 
​​​​​​​​​​​​​​► What time zone does the backup schedule follow?
The backup schedule follows the time zone of backup proxy. For example, if you set the schedule such that backups start at 8 AM, backup proxy deployed in New York will start backup at 8 AM EDT and backup proxy deployed in California will start backups at 8 AM PST, respectively.
​​​​​​​​​​​​​​► What is a server group? How does it help me?
A server group is a logical categorization of virtual machines that share something in common. For example, virtual machines located in one region can belong to a server group. Similarly, virtual machines having the same guest operating system can belong to one server group. After you create a server group, you must attach a backup policy to the server group. To know more about server groups, see About server groups
​​​​​​​​​​​​​​► Do you have best practices for creating server groups for virtual machines?
Yes, we do. To know more, see Best Practices to create a server group.  However, for an exact configuration of server groups best-suited for your environment, contact the Druva Support team.
​​​​​​​​​​​​​​► Can I create different schedules for virtual machines in a server group?
Yes, you can. You can attach a backup policy that defines one or multiple schedules to a server group containing virtual machines. Backups from all virtual machines belonging to this server group follow the rules defined by this backup policy. 
​​​​​​​​​​​​​​► Can I adjust bandwidth on a virtual machine level?
No, you cannot adjust bandwidth at a virtual machine level. However, you can adjust the bandwidth that you assign to a server group by configuring the backup policy attached to this server group. Virtual machines inherit the bandwidth settings from the server groups to which they belong. 
​​​​​​​​​​​​​​► Can I assign more than one backup policy to a server group?
No, you cannot. However, you can detach a backup policy from a server group, and attach a new backup policy to the group. 
​​​​​​​​​​​​​​► Can I use the same token to activate a Windows server and a Linux server?
Yes, you can. However, we recommend that you use a single token to activate servers that share something in common. For example, you might want to use a token to activate all virtual machines that are geographically co-located.
​​​​​​​​​​​​​​► When do I need to consider a reconfiguration?
If you want to change the server group to which virtual machines are assigned, you can consider a reconfiguration. You might also consider reconfiguring a server if you want to assign a different backup policy to the virtual machines. 
 
  • Was this article helpful?