InfoScale™ 9.0 Installation and Upgrade Guide - Windows
- Preinstallation and planning
- About the Arctera InfoScale product suite
- Supported hardware and software
- Disk space requirements
- Installation requirements
- Requirements for installing InfoScale Storage in a Microsoft Failover Cluster
- Recommendations and best practices
- About InfoScale licenses
- About telemetry data collection in InfoScale
- About InfoScale and UEFI Secure Boot
- Installing the Arctera InfoScale products
- About installing the InfoScale products
- About the co-existence of InfoScale products
- Installing the server components using the installation wizard
- Applying the selected installation and product options to multiple systems
- Installing the server components using the command-line installer
- Parameters for Setup.exe
- Available product options and supported DMP DSMs
- Registering the InfoScale Storage resource DLLs
- Installing the client components
- Configure Key Management Server (KMS) for volume encryption
- Upgrading the InfoScale products
- Performing the post upgrade tasks
- Deployment scenarios and applicable post upgrade tasks
- Re-enabling Volume Replicator in a non-clustered environment
- Re-enabling Volume Replicator in a Microsoft failover cluster environment
- Reconnecting DMP DSM paths after the upgrade
- Reconfiguring the Veritas InfoScale Messaging Service
- Importing the configured rules
- Upgrading clusters for stronger security
- Reinstalling the custom agents
- Including custom resources
- Administering the InfoScale product installation
- Uninstalling the InfoScale products
- Performing application upgrades in an InfoScale environment
- Upgrading Microsoft SQL Server
- Upgrading Oracle
- Upgrading application service packs in an InfoScale environment
- Appendix A. Services and ports
- Appendix B. Migrating from a third-party multi-pathing solution to DMP
About InfoScale and UEFI Secure Boot
Review the following information if you intend to deploy InfoScale on systems where the Secure Boot feature is enabled:
Secure Boot provides a mechanism that allows only digitally signed and authenticated kernel and driver modules to run on the operating system. This approach makes it harder for unintended or tampered software to load during boot time and take control of the operating system. When the system boots, it checks and validates the identity of all the software components and allows only Original Equipment Manufacturer (OEM) trusted software to load at boot time.
InfoScale supports deployment on Unified Extensible Firmware Interface (UEFI) firmware-based systems where the BIOS is configured to run in the UEFI mode and have the Secure Boot feature enabled. InfoScale kernel and driver modules are digitally signed using Microsoft Windows Hardware Quality Labs (WHQL) release signatures. These signatures help ensure the authenticity and integrity of the InfoScale kernel and driver modules. The signatures contain a chain to the Microsoft Root Certificate Authority to ensure that InfoScale software drivers are Secure Boot safe. During the boot sequence, UEFI environment uses the Windows Boot Manager to validate the InfoScale kernel module signatures before booting the operating system.
Note:
Secure Boot support is available for both on-premise and cloud (AWS and Microsoft Azure) deployments.
Enabling Secure Boot is not a prerequisite. You can install InfoScale packages that contain signed kernel and driver modules even if Secure Boot is not enabled on the systems in your environment. Even though InfoScale packages are digitally signed, there is no change in the InfoScale deployment process.