Skip to main content
Druva Documentation

SQL FAQs

 

This topic contains the following sections:

Overview FAQs


► How does the Phoenix deduplication algorithm work?
Phoenix uses a deduplication technique that makes use of a variable block sizing technique based on file type to determine globally duplicated data across all your servers. The Phoenix agent only transfers unique blocks of data to the cloud. This ensures massive bandwidth savings of up to 90% in many cases.

► Where is my data backed up?
Phoenix backs up your data in the cloud hosted by Amazon. Phoenix relies on the robustness and the security standards of Amazon Web Services to ensure that your backup data stays safe and secure. 

► What does Phoenix back up?
Phoenix provides support for backup of MDF, NDF, and LDF files. 

► What happens if my server loses connectivity?
Phoenix is designed to work efficiently even for organizations with intermittent connectivity.  If Phoenix agents cannot reach Phoenix Cloud, backups or restores stop temporarily. When connectivity resumes, backups or restores start again. A single backup can, therefore, span across multiple backup windows. 

► What are snapshots? 
A snapshot is a point-in-time image of your backup data. To know the type of snapshots that Phoenix supports, see Common terms

► My server is not operational. I want to replace it with another one. Can I? 
Phoenix retains the data from your server that is not operational. You can restore the data to another server. 

► I deprecate servers every 3 years. Can I configure new servers in their place?
Yes, you can. Phoenix retains data from the servers that you deprecate. To set up new servers in their place, restore the data from the deprecated servers to the new servers. 

► What are restores of warm and cold snapshots?
The term "warm" and "cold" signify how old your data is. Restores using warm snapshots are performed for data that is no more than 90 days old. The data is stored in the warm storage. At the end of 90 days, the data is transferred to cold storage, where it resides for as long as you define in the retention policies. For such data, you must use cold snapshots to perform a restore. To know more about hot restore and cold restore, see Common terms
Defreeze is the process of preparing cold snapshots for restore. During a defreeze operation, Phoenix retrieves cold snapshots from cold storage and makes the data available for restore. 
Thawed data is a cold snapshot that has undergone a defreeze operation. The thawed data is available for restore for a specific duration.  

► How does Phoenix handle data availability requirements for regulatory or legal purposes? 
Phoenix stores backups for as long as you need. You can choose from multiple data retention options - as short as 90 days and up to the end of time for retaining data. Data older than 90 days is stored in cold storage. You can restore data stored in archival storage at any time by initiating a defreeze operation. For data that is less than 90 days old, you can perform an on-demand restore. 

► I want to back up secondary servers only if the primary server fails. Can I do this? 
No, you cannot. However, you can create backup sets to back up the content from your secondary servers and your tertiary servers. Phoenix will back up data from your primary, secondary, and tertiary servers according to the schedule defined in the backup policy. 

► Can I specify a bandwidth for backup?
Yes, you can specify the bandwidth limitation for backup.

► Can I specify a bandwidth for restore?
No, you cannot specify the bandwidth limitation for restore. 

► What happens to my data after my contract expires?
After the expiration of your contract, Phoenix does not back up your servers. However, your data is retained on the cloud. You can choose to extend your contract, and then perform a restore of the data.

► Can I export Phoenix data?
No, you cannot export Phoenix data. However, you can choose to restore data to the server to which it belongs, or a new server. 

► Can I perform a restore to a server in another organization under Phoenix?
Organizations in Phoenix are independent entities by design. Phoenix does not have a functionality that allows inter-Organizational restore. 

Configuration FAQs


After the Phoenix agent is upgraded from older clients to version 4.7.1 or later, what happens to my existing backup sets?
After you upgrade the client, 
  • The MS-SQL backup sets configured to back up all instances in the content rule are auto-disabled.
  • Phoenix agent discovers the existing instances on the server.
  • Phoenix creates a new backup set for each instance present on the physical server.  All the newly created backup sets have the same policy and same content rule as that of the earlier backup set for the All instances.
  • Phoenix allows you to restore data from the All instances MS-SQL backup sets. If you have backup sets on the older clients, which were created for a particular instance, backups for those backup sets run without any change.
  • If you do not upgrade from the older clients to 4.7.1 or later, backup jobs for the existing MS-SQL backup set will continue to run as configured. However, you will not be able to create new SQL backup set with Phoenix client versions older than 4.7.1. 

► How do I configure my SQL servers for backup?
To know how you can configure SQL servers for backup, see Introduction to Phoenix for SQL servers

► What do I need to know before performing a configuration of my SQL servers?
Before configuring your SQL servers, we recommend that you read SQL server prerequisites and limitations. The checklist should help you perform a configuration that is best-suited for your environment.

► Unable to configure backup set with the following error "Current Backupset won't be configured as some instances are overlapped in another backupset configuration"?
For MS-SQL server, you can create backup set either for "All instances" or "individual instances". If you have created backup set for "All instances", then Phoenix does not allow you to create backup set for individual instances. Similarly, if you have created backup set for individual instances, then Phoenix does not allow you to create backup set for All instances. However, if you have created backup set for All instances and the backup set is disabled, Phoenix allows you to create backup set for individual instances.

► Why can't I see my instances listed under the Protect > MS-SQL Servers > Instances/AGs tab?
The details of the existing MS-SQL backup sets can be found on the Protect > Windows/Linux Servers > All Servers > servers_name page > SQL Backup Sets tab. To view the available instances and AGs along with their configured backup sets, upgrade the Phoenix agent to the version 4.7.1 or later.

► Unable to create MS-SQL backup sets for Phoenix agents older than version 4.7.1.
You cannot create MS-SQL backup sets for Phoenix agents older than version 4.7.1. However, backups for the old backup sets continue to run as configured.

► Can Phoenix discover the running MS-SQL instances and AGs on Phoenix agents older than version 4.7.1?
No. Phoenix cannot discover MS-SQL instances and AGs running on the server installed with an agent older than version 4.7.1.

► Why do I see additional backup sets created post-upgrade of the Phoenix agent to version 4.7.1?
Phoenix creates a new backup set for each instance present on the physical server. All the newly created backup sets have the same backup policy and same content rule as that of the earlier backup sets for All instances.

How many backup sets can I configure on my MS-SQL server?
The maximum number of backup sets that you can configure on the MS-SQL server depends on the number of the instances existing on that server. You can create one backup set per instance.
For MS_SQL server, you can create backup set either for "All instances" or "individual instances". If you have created a backup set for "All instances", then Phoenix does not allow you to create a backup set for individual instances. Similarly, if you have created a backup set for individual instances, then Phoenix does not allow you to create a backup set for All instances. However, if you have created a backup set for All instances and the backup set is disabled, Phoenix allows you to create a backup set for individual instances.

► My database files are stored on a Cluster Shared Volume, so the default Microsoft Shadow Copy Provider cannot take a snapshot of these files. How do I make the Phoenix agent use the Microsoft CSV Shadow Copy Provider?
  1. From the command prompt, run the following command:
    vssadmin list providers

    Running this command displays a list of VSS providers, and the provider IDs. Copy the Microsoft CSV Shadow Copy Provider ID. 

  2. Stop the Phoenix agent service. 
  3. Open the Phoenix.cfg file in a text editor. The Phoenix.cfg file is available at the following location on Windows Server 2012 and 2008: C:\ProgramData\Phoenix
  4. Add the VSS_PROVIDER_ID parameter, and set its value to match the Microsoft CSV Shadow Copy Provider ID you obtained in the first step. 
    Use the following format to add the Microsoft CSV Shadow Copy Provider ID: 
    VSS_PROVIDER_ID = '<Provider ID>'
    For example:
    VSS_PROVIDER_ID = '{b5946137-7b9f-4925-af80-51abd60b20d5}'
    
  5. Save the Phoenix.cfg file.
  6. Start the Phoenix agent service. 

Backup and restore FAQs


► What type of backups does Phoenix perform on SQL servers?
The first backup of your servers is a full backup. Thereafter, Phoenix performs an incremental backup. Additionally, Phoenix also supports differential backups of SQL servers. To know more, see Common terms.

► How do I back up or restore my data?
To know how to back up your SQL servers, see Back up servers . To know how to restore SQL servers, see SQL server restore

► How does Phoenix back up or restore my SQL server data?
To understand the workflow at the time of backup, see full backup, differential backup, and log backup.
To know how Phoenix restores your file server data, see SQL server restore.

► What do I do if the SQL server transaction log backup fails with VSS1 error?
Check whether you have SQL standalone or SQL FCI installation done. In case you have SQL FCI, upgrade to build 4.7.1 or later and follow setup instructions as described in Configure Phoenix for the backup of databases in SQL Failover Cluster Instance (FCI).
  • Was this article helpful?