Search
Close this search box.

Cristie VA 2.7 What’s New

Cristie VA Release

The new VA 2.7 release (2.7-238) os now live.
Existing customers can update via yum or via GUI now.

Headline Enhancements

Our latest release includes volumes of new functionality which brings with it a wealth of benefits. Some of the key highlights include:

  • VA Features can be enabled and disabled. This keeps the protect.ova download smaller, allowing you to only install the features you require
  • Feature bundles. You can download and install features without an internet connection.
  • BMRCFG status reporting. You can now see the date of your machine DR config. This is shown at the point of recovery/simulation and in the estate display (assuming you deploy the BMR product via the VA)
  • Backup storage can now be named so it is easily identifiable.
  • Manual restore of Protect 4 VM backups. This allows you to restore P4VM backups taken on another Cristie Virtual Appliance.
  • You can now add a machine from a CBMR backup job to a recovery simulation. This will enable the simulation to always attempt to recover the latest available backup. Previously this would have required a manual change after every backup.
  • Update from the graphical user interface. From 2.7 onwards customers can upgrade from the appliance interface as well as via the command line.
  • vSphere 6.7 support. vSphere 6.7 is now supported as a target hypervisor.
  • vSphere 6.7 support. Protect for VMs now supports vSphere 6.7.
  • vSphere VM name limit increased from 15 characters to 80 characters.
  • Discovery is quicker throughout all areas of the VA.
  • Sudo support. Deployment/Licensing/Backup operations can now be performed without using root.
  • You can now disable S3 replications (globally and on a per proxy basis).
  • Estate management (deployment and licensing operations) now support Windows Server 2019.
  • Restores/Simulations of Windows Server 2019 backups is now supported (where 2019 is supported by the 3rd party backup vendor).
  • Replications of Windows Server 2019 is now supported.
  • Added new ‘Midnight’ theme.
  • Show password toggle. Every password field now has the ability to show the password in plain text.
  • Email alerts for failed CBMR or P4VM backups/restores. You can now get basic email alerts if a backup fails. Enhanced email notifications will be part of a future release.
  • Replication/Recovery/Simulation screens are now more responsive and status reporting has been improved.
  • Includes the latest 8.5 release of ABMR, CBMR, NBMR & TBMR for Windows and Linux
  • Includes the latest 8.5 release of CBMR for AIX & Solaris
  • Includes the latest 3.6 release of CloneManager for Windows & Linux
  • Replications to AWS are now supported.
  • Simulations/Recoveries to AWS are now supported.
  • Error messages improved when creating a recovery simulation.
  • You can now specify a VM name for Replication & Migration jobs. Previously the existing hostname would be used for the VM name.
  • Linux PPC is now supported for estate management.
  • Linux PPC is now supported for Recovery/Simulation operations.
  • Simulation health reporting is now more reliable.

Bug Fixes

  • Removing a system from a backup job did not clear it’s backup storage. This sometimes meant it was not possible to delete backup storage.
  • CBMR for Linux would sometimes fail to install on non English systems. This has now been fixed.
  • Some customers attempting to replicate to vSphere were unable to specify a datacenter other than the default, this is now fixed.
  • CBMR backups would fail with an unknown error if your machines license was invalid. This is now handled properly.
  • Backing up Linux & Windows machines to the same CIFS share would sometimes cause Windows backups to fail. This is now fixed.
  • It was not possible to discover a Spectrum Protect (TSM) server if none of the nodes contained a disrec.ini. This is fixed.
  • Changing backup storage for Linux backups would not work until the user manually unmounted the backup shares. This is now done automatically.
  • Windows CBMR recoveries would fail if you restored from a backup location with a user account that was not part of a domain.
  • Disk information missing from DRAnswerfile for Linux recoveries to physical systems
  • Error messages improved when creating a recovery simulation.
  • Replication log files would sometimes be downloaded multiple times. This is now fixed.
  • Selecting Run now on a Replication machine would sometimes start everything in the job. This is now fixed.
  • Values not bound to statement error when configuring a physical replication. This is now fixed.

Contact Us

Thank you for contacting us. We have received your request.