Phoenix Critical Updates

Please download latest updates from here- http://www.druva.com/download/phoenix/network-backup

Update: Phoenix Client Server 2.2 Build r2440-1018

September 30th 2011

New Features (Windows):

Microsoft Exchange Server Backup Agent : Phoenix 2.2 significantly enhances its backup capability with a new agent for MS Exchange, which supports dynamic backup and restore of Microsoft Exchange Server databases, mailboxes, and mail items. Each backup except the first is incremental. The Phoenix agent for MS Exchange uses MAPI to backup and restore e-mails (and other mail items) to and from an Exchange store for its backup and restore purposes. The Agent allows restore of server, database, mailbox and individual mails and mail items to the original location. It also provides an interface to browse and search for items within a mail folder.
MySQL Backup Agent for Windows: Phoenix 2.2 introduces a MySQL backup agent for the Windows operating systems. This agent creates backups and restores an entire MySQL data repository, which includes all the databases and tables served by a given MySQL server instance. It also has the option to backup binary logs if they are in different directory. Multiple instances of MySQL server are also supported, but through different backup sets.
Restore Point Deletion: Now users are able to delete individual restore points, except the latest restore point.
Performance Optimizations for large file backups
Set Logon Credentials for Client: The administrator can set the account that the Phoenix client service uses (as part of client management) from the Web Console,
using the Set Logon Credentials screen.

Known Issues (Windows):

MS Exchange related

The Phoenix agent cannot create backups if the Microsoft Exchange Server machine does not have Microsoft Outlook (32 bit) version installed.
When a backupset is configured with large number of mailboxes, regular sync/media dump mail fail after a while. Restarting the sync will ultimately complete.
Phoenix backup client should be installed on the machine where Micosoft Exchange Mailbox Server Role is installed.
Sometimes a backup task that shows its status as ‘canceled’ in Active Tasks in the Web Console takes a long time to be actually canceled from the client. You cannot start another sync on the same backup set during this period.
The Exchange agent does not allow simultaneous backup and restore tasks on the same Exchange server.
The Restored Message folders will get excluded every time from a backup, even if it is removed from the Exclude Folders of the backup set.
Backup of the following System Public Folders is not supported: Event Root, OWAScratchPad, Schema-root, and StoreEvents.
If you create a new backup set while another backup set is being synced, Phoenix takes a long time to display Exhange Agent components.
If the archive of a mailbox is present on a different mailbox server than the one where the mailbox is present, Phoenix will not back it up.
If you take a backup of a database in an inactive node which is part of a Data Availibility Group (DAG), then its restoration will fail.
If the network between the Phoenix client and server is frequently disrupted, sometimes the task is seen as Active, but may be stalled.You need to restart the client service.
The Phoenix client service will not run properly if the user account set in the Set Logon Credentials screen does not have Administrator privileges in Active Directory.
The Backup User name entered in the Set Logon Credentials screen should have an associated mailbox with the same name

Other Known Issues

When specifying the user account used to run the Phoenix client service (in the Set Logon Credentials screen), if the user account is a built-in account of Active Directory, like Administrator or Guest, you need to enter the Display name. For any other account you need to enter the User logon name.
Internet Explorer 9 is not supported
Sometimes, after a fresh installation, the user needs to start the Phoenix server service manually

Update: Phoenix Client Server 2.1.1 Build r1978-855

July 4th 2011

New Features (Linux/Windows):

Phoenix web control panel can be configured to use secure connection i.e https.
Users can delete SMTP server configuration from web gui.
Enhanced restore performance for large sized files

Fixed Issue (Linux/Windows):

Repetitive alerts don’t get generated for missed backups once a backup is completed.

Update: Phoenix Client Server 2.1 Build rev1684 (748)

May 11th 2011

Fixed Issue (Windows):

Sometimes, when the server reboots, the storage doesn’t come up. Phoenix Server Service needs to be restarted for that. This has been fixed.

Fixed Issue (Linux):

Sometimes, when the server reboots, the storage doesn’t come up. Phoenix Server Service needs to be restarted for that. This has been fixed.
The issue regarding license has been fixed. When more than one ethernet cards were present on same machine it used to show invalid license status. Now this situation is handled gracefully.

Feature Enhancement

After migration to check data credibility it triggers the restore point verification in the background

Downloading:
Before starting the installation, ensure that you have downloaded the Druva Phoenix installers from the Druva Website – http://www.Druva.com/

Upgrades:

Server and Client upgrades from Phoenix 2.0 to 2.1 are supported.
2.0r1408-585 -> 2.1 r1684(748)
2.0r1425-592 -> 2.1 r1684(748)
2.1r1535-664 -> 2.1 r1684(748)
2.1r1540-668 -> 2.1 r1684(748)

Update: Phoenix 2.1 rev1535 (664)

March 30th 2011

Fixed Issues (Windows)

Sometimes when a sync operation is going on, the sync fails with a deadlock error in server logs. This issue has been fixed.
If compaction is started after deletion of backup set, then compaction gets stuck. This issue has been fixed.

Fixed Issues (Linux)

Backup Request stalls after some time.

Known Issues (Windows)

If size of data file in a database is increased to a large size, then it starts the differential backup.
If MSSQL database name is in Unicode, “Restore to different location” feature doesn’t work.

How to Update

To upgrade from Druva Phoenix v1.x, support assistance is required. Please contact support@druva.com for more information on the upgrade process and the upgrade utility tool.

Update: Phoenix 2.0 rev1425 (585)

March 28th 2011

New Features

Storage scalability: Druva Phoenix 2.0 sports a new storage engine written from scratch. The new architecture gives it better scalability and performance to support concurrent access to a large number of clients. Druva Phoenix server uses an Oracle Berkeley database engine to manage configuration and storage. Successful installation of the server automatically launches a wizard to install and configure the database.
HyperCache support: Phoenix now offers a HyperCache functionality to boost storage performance. Hypercache is an in-memory cache of the dedupe index.
Microsoft SQL Server (Windows platform only): Phoenix introduces support for MSSQL with the addition of the ëMSSQL Backup Agent. A user can configure Backup Set to take backup of the MSSQL database, including log directory and data directory. User can restore the MSSQL database to its original location through a simple restore.
SSD Storage: A solid-state drive (SSD) is a data storage device that uses solid-state memory to store persistent data. Phoenix uses SSD for storing SIS database. If you want to use a Solid State Drive (SSD) for performance acceleration, specify the path to the SSD volume here. This is the path to the SIS database folder where the Oracle Berkeley DB engine stores its Meta data for the encrypted SIS store.
Hierarchical Restore points: While creating a backup set, user can specify for how much time the restore points are to be kept. This is specified in terms of three fields daily, weekly, and monthly. When Compaction is started, all restore points younger than the daily limit are kept. The restore points that are older than the daily limit but younger than the weekly limit and whose adjacent restore point has a time difference of less than seven days are deleted. Restore points that are older than the weekly limit but younger than the monthly limit and whose adjacent restore point has a time difference of less than thirty days are deleted. All restore points whose creation time is older than the monthly limits are deleted.

Known Issues (Windows)

Sometimes when a sync operation is going on, the sync fails with a deadlock error in server logs.
If compaction is started after deletion of backup set, then compaction gets stuck.
If size of data file in a database is increased to a large size, then also it starts the differential backup.
If MSSQL database name is in Unicode, “Restore to different location” feature doesn’t work.

Known Issues (Linux)

Files get missed sometimes and a DB deadlock error occurs while doing backup of 8 backup sets simultaneously.
Sometimes backup does not get resumed after storage recovery.
If compaction is started after deletion of backup set, then compaction gets stuck.
If a backup fails with storage quota exceed message then after increasing quota limit and restarting backup, some files get missed with error.

How to Update

To upgrade from Druva Phoenix v1.x, support assistance is required. Please contact support@druva.com for more information on the upgrade process and the upgrade utility tool.

Update: Phoenix 1.4.0 rev1221

January 21st, 2011

Critical Fixes

Fixed SQL deadlocks, improved inc. backup performance
Fixed bug with hcache checks for linux client

How to Update

To upgrade the server and client simply install the new binaries on top of the existing installation. Please make sure to upgrade the server first.

Update: Phoenix 1.4.0 rev1020

November 1st, 2010

Enhancements

Added support for MySQL agents for Linux
Limited LVM snapshot support for MySQL

Critical Fixes

Phoenix client and server take less time for restoring large files
Errors in client & server for volume snapshot failure are reported in the phoenix server logs
When the key is reset, connected status in WEB GUI is shown on the backup client page
Correct ETA while doing restore is displayed on the WEB GUI on Active Tasks page
Entry for backup schedule deletion is displayed in the Phoenix server log
While creating a backup set, maximum size for “storage quota & number of days” is shown on the backup client page

How to Update

To upgrade the server and client simply install the new binaries on top of the existing installation. Please make sure to upgrade the server first.

Update: Phoenix 1.3.0 rev0899

July 22nd, 2010

Enhancements

Added Linux client support for Debian and Redhat derived distributions
Media dump for linux server

Critical Fixes

Initially not showing correct ETA in active task list has been fixed
During media load user can have psf files in different locations
Better handling of errors during media load
Fixed issue with extra files/folders being restored in some scenarios

How to Update

To upgrade the server and client simply install the new binaries on top of the existing installation. Please make sure to upgrade the server first.

Update: Phoenix 1.2.0 rev0833

Apr 30th, 2010

Enhancements

Media based initial backup
Force compaction for storage
Improved Dashboard, stats and PDF reports
Universal BMR supports hardware diagnosis
User can create BMR with password
ETA field is included in active task list

Critical Fixes

BMR backs up dynamic disks
Enhanced error message in GUI if server service is not working
Enhanced logging
Enhanced hardware handling in BMR

How to Update

To upgrade the server and client simply install the new binaries on top of the existing installation. Please make sure to upgrade the server first.

Update: Phoenix 1.0.2 rev0687

Feb 10th, 2010

Critical Fixes

Support for creating SIS store on NAS shares
Fix for ACL backup and restore
Fix for SQL deadlock, changes to locking
Fix for thread spooling on the server
Minor changes in the GUI
Fix for race conditions in simutaneous multi-client backups
Fix for sub-folder permissions during backup
Fix for active progress bar for active tasks

How to Update

To upgrade the server and client simply install the new binaries on top of the existing installation. Please make sure to upgrade the server first.

Update: Phoenix 1.0.1 rev0624

Dec 14th, 2009

Enhancements

Global Source Based Data Deduplication
Near Continuous Data Protection
WAN Optimization and Bandwidth Scheduling
Generic Windows based agent
Bare Metal Restore
Web UI with basic Dashboard

Critical Fixes

All ports (webGUI, sync) configurable
Failed to backup .bkf files
Exclude specific files from volume backup – sysfile, pagefile, sys-volume-info etc
Creating a new storage with decimal number as size throws error
Log more information on VSS Errors
ACLs not restored properly if file already exists
Backup Set configured with Bare Metal Restore needs at least one folder configured
Client Log is missing or incomplete in failed backups

How to Update

To upgrade the server and client simply install the new binaries on top of the existing installation. Please make sure to upgrade the server first.

Note: Please note that after applying the update, the first incremental backup will be slow, but the following incremental backups will be much faster.