Close this search box.

Cristie VA 4.8.1 What’s New

Here’s an update on what’s new for the Cristie Virtual Appliance. The 4.8.1 release includes lots of new functionality and bug fixes which bring with it a wealth of benefits.

We are pleased to announce a new update for the Cristie Virtual Appliance. The 4.8.1 release includes lots of new functionality and bug fixes which bring with it a wealth of benefits.

Headline Enhancements

      • Backup server protection – You can now import all clients from a chosen backup server to be added to a Simulation job.
      • You can now perform CloneManager Offline replications to SMB/NFS storage.
      • Rubrik Security Cloud support – You can now enter RSC details into the backup server discovery page to automatically discover all managed CDMs.
      • Active-active clustering – You can now configure active-active clustering up to a maximum of 32 nodes, allowing you to load balance operations across several instances of the VA and providing additional redundancy.
      • Recovery templates – You can now pick (and tweak) pre-defined recovery templates, allowing you to configure jobs en-masse without the need to manually enter all of the details for recovery/simulation/replication.
      • You can now use BIOS UUIDs as a system identifier for iPXE web boot mappings.
      • Context menus – You can now right click on jobs/systems to perform actions without having to use the actions menu.
      • Orchestration display now shows current task and current task status (where applicable).
      • You can now run individual tasks or stages inside an orchestration job.
      • Reusable tasks have been retired in favour of recovery templates.
      • You can now import an Orchestration recovery task into a Simulation job. Allowing you to test your recovery prior to a disaster scenario.
      • You can now specify local boot as part of a boot mapping. Allowing you to reboot systems back to the recovered OS without removing the boot media.
      • You can now bulk import clients from a backup server into a Simulation job.
      • The Recovery wizard will now display contextual help based on your selections.
      • Linux DR ISOs now boot to text based mode by default. Reducing the RAM requirements.
      • You can now create boot mappings as part of the Recovery wizard. 
      • You can now re-run a standalone Recovery operation.
      • You can now edit boot mappings in Boot Management.
      • You can now setup Simulation and Replication jobs as “Run once” schedules.
      • If configured, a Recovery will now trigger on boot of the ISO. (9.5.2 or later is required).
      • You can now import a Simulation job into an Orchestration job.
      • Credentials are now validated before every replication.
      • You can now deploy DR proxies to a HMC environment.
      • User audit logging can now be enabled from the Options page.
      • Replication Sandbox is now available for CloneManager Offline replications to AWS.
      • Export VA configuration has been enhanced to optionally export all recovery media, allowing you to import everything required to a fresh VA following a disaster. 
      • Significant performance enhancements.
      • Various minor GUI fixes & enhancements.

    Bug Fixes

        • Disk selections were not being honoured properly for CloneManager Offline replications.
        • Older appliances would sometimes fail to reboot after an upgrade with “failed to start switch root” errors.
        • Download links under Tools -> Download Software were not always working.
        • Importing AD groups would only import one user.
        • Modifying an Orchestration recovery would break disk mapping for Linux recoveries.
        • Web boot iPXE would not work for RBMR.
        • Editing a physical recovery wouldn’t show the target system properly.
        • Web boot – iPXE environment wouldn’t reboot if a mapping wasn’t available.
        • Windows custom ISO static address could sometimes be assigned to the wrong adapter.
        • Editing an Orchestration stage would sometimes fail.
        • VA would continue to create Hyper-V targets if the system was not discoverable.
        • Fetching multiple RBMR DR configs would cause the proxy to hang.
        • The UpgradeAdministrator account was not always being removed following an automatic upgrade.
        • VA OVA’s was being deployed with a 100GB disk instead of 200GB.
        • Post recovery checks would sometimes fail when comparing Windows DR configs.
        • Show discovered targets display wouldn’t show which system was selected.
        • It was not possible to create a custom log bundle with Orchestration job logs.
        • Import hotfix display would show features not available on the VA.
        • Linux restores to physical systems would show an input for drivers. This has been removed.
        • Windows CBMR recoveries would sometimes fail with exit code 127.
        • Too many network interfaces would break the interface.
        • CBMR backup credentials were not tied to Estate Management.
        • Boot Management page styling was broken.
        • Exporting VA configuration through browser downloads has been retired.
        • Hyper-V recoveries would default to BIOS boot for EFI system recoveries.
        • Reverting to snapshots would not always power off the VM once a snapshot had been reverted.
        • Other minor bug fixes.

      Useful Forum Posts

        Contact Us

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