February 05, 2018
The following Phoenix updates are released for the cloud update on February 05, 2018.
Support for AlwaysOn Availability Groups for MS-SQL server
Druva now supports AlwaysOn Availability Groups for MS-SQL server. You can back up databases that are a part of the AlwaysOn Availability Groups for MS-SQL server.
The key features of this update include:
- Seamless auto-discovery of MS-SQL instances and Availability Groups that are available on the MS-SQL server.
- Ability to enable backups from any preferred secondary or primary node in the Availability Groups.
With this update, Phoenix provides a new menu option, Protect menu, and the Servers menu is moved to the Protect menu. To access the MS-SQL server backup and restore configurations, operations, and other listings, click Protect > MS-SQL Server.
Action required: To use all the new capabilities of this feature, upgrade to the Phoenix agent version 4.7.1. To know more about how it impacts the current backup sets, click here.
For more information, see:
- Backup methods available for MS-SQL server databases
- Configure registered server with MS-SQL backup set
- Configure servers to back up data from multiple workloads
- SQL errors
- Prerequisites to backup availability group databases
- Impact of upgrading Phoenix agent from the old clients to version 4.7.1 on the existing backup sets
Support to trigger backup using command-line interface
You can now backup jobs through the command-line interface. The command line utility is supported only for the configured MS-SQL backup sets.
For more information, see Trigger backup using command-line interface.
Action required: To use the new capability of this feature, upgrade to the Phoenix agent version 4.7.1.
AWS account sharing across multiple organizations
With this update, you can start using an AWS account with multiple Phoenix organizations for disaster recovery. Virtual machines from multiple organizations can be replicated to a single AWS virtual private cloud subnet.
For more information, see DRaaS FAQs.
You can select resource pool, folder, and network settings at the time of restoring a virtual machine or disk to an alternate location.
For more information, see:
The following issue is fixed with the Phoenix update released on Feb 05, 2018:
- ROBO-5865: Phoenix differential backup jobs for Filestream databases failed with an internal error. The full backup jobs and log backups completed successfully for these databases.
January 15, 2018
The following Phoenix updates are released for the cloud update on January 15, 2018.
- Phoenix now provides backup and restore for virtual machines created and managed using Hyper-V on Windows Server 2016
- Support for Mumbai and UK regions
December 04, 2017
The following Phoenix updates are released for the cloud update on December 04, 2017.
Druva is excited to announce the following features:
Microsoft Hyper-V protection
Druva extends its virtual machine backup capabilities to Microsoft Hyper-V virtual machines. Phoenix Hyper-V agent resides on the Hyper-V host and performs image-level backups of the virtual machines. This eliminates the need to install the agent software on each virtual machine guest operating system. The key features include:
Forever incremental backups with source-side global deduplication.
Application consistent backups through integration with Microsoft VSS framework.
Support for all Hyper-V storage deployments including the local and cluster-shared volumes and SMB.
Flexible restore options, such as restore of the entire virtual machines or individual disks, and restore data to the original host or to an alternate host.
For more information, see Backup and Restore Hyper-V Virtual Machines.
NAS backup agent
Druva is pleased to announce a new approach for backing up Network Attached Storage (NAS) devices with Phoenix. The key highlights include:
- Scale-out NAS agent that allows parallel and performant backups for large NAS deployments.
Smart scan approach, including machine learning through metadata analysis, that identifies data that has changed for backup versus initiating repeated backups of all data - changed or unchanged. By focusing on backup of only the new or changed data, backup cycles are dramatically shortened.
Native data format and vendor agnostic approach that enables device migration and data intelligence use cases.
For more information, see Back up and restore NAS shares.
Support for Backup sets for physical servers
A backup set is a data set that you can configure for backups by defining the backup content and backup policies for files and databases. A backup set provides configuration options to customize the backup content, backup policy, and retention settings.
You can configure multiple data sets for backup with their own policies and settings, independent of each other. For example, if you want to back up files and MS-SQL server database on the same server, you can create two backup sets; one for files and another for the MS-SQL server database with their respective policies.
For more information, see:
- Configure registered File servers for backup
- Configure registered servers to back up data from multiple workloads
- Configure registered MS-SQL servers for backup
- Key concepts and terms
- What’s changed with Backup sets
Upgrade to Phoenix agent version 4.7 to use all new capabilities of backup sets.
To know more about what's changed with backup sets, check the article here.
For a quick demo of backup sets, check this video.
Support for Canada region
Druva now allows you to back up virtual machines in Canada. However, Druva does not support disaster recovery in this region.
The following issues are fixed with the Phoenix update released on Nov 20, 2017:
|7592||Backup fails with INTERNAL65535 - TypeError: Incorrect padding|
|7507||CloudCache is not flushing data|
|7208||Disaster recovery request marked as failed in case of network retry scenario|
|6916||File Server backup fails with INTERNAL65535 - AttributeError: 'NoneType' object has no attribute 'get'|
|5672||Server status report shows different time zones for virtual machines although they are part of the same proxy pool|
Known issues and workarounds
For more information on known and fixed issues, see Known issues and fixed issues.