Windows Installation on Non-SharePoint Nodes
Last updated
Last updated
The following describes installation on nodes that are not running SharePoint. For installation on SharePoint nodes, see .
Before installing, close all programs. Windows Installer Service must be active. If the node is a member of a cluster, start Windows Cluster Service and ensure DPX cluster service is made offline.
Installation on many versions of Windows requires Windows Installer 4.5. If necessary, download it from the Microsoft website at .
From the machine you are installing on, navigate to the location where the installers have been made available. See . To start the installation wizard, run the installer that corresponds to your system.
Installer names have the format DPX-<version>-<platform>-{x64/x86}-installer.exe; for example, DPX-4.9.0-win-x64-installer.exe.
Warning. If you run the installer on a machine with Windows 2008 R2 or later, first right- click the installer executable, then select Run as administrator (even if you are logged in as Administrator).
Note. For 64-bit clients that have limited disk space on the system drive, you have the option to run a client-only installer. This installer requires significantly less temporary disk space than the standard installer. For client-only installation, run DPX-4.9.0-win-x64-clientonly-installer.exe. Note the following limitations of the client-only installers:
The client-only installer does not include the option to make the client a virtualization proxy server. Use the standard installer to install virtualization proxy server features. See in the User’s Guide.
The client-only installer does not support remote deployment.
See also. For the latest system compatibility details regarding supported hardware, file systems, applications, operating systems, and service packs, see .
Click Next.
When prompted, select I accept the terms in the license agreement and click Next.
The Setup Type dialog appears.
Select the components to install. For a master server installation, all components are installed. For a client installation, you can optionally select Virtualization Proxy Server. The following are the installation components:
Client. Installs client software, which enables backup of the machine once it is added to the Enterprise. Any supported client can be a device server. Client software automatically installed on the master server enables the master server itself to be backed up.
Master server virtual appliance. The DPX master server appliance is the one machine that holds and manages the Catalog. You perform this deployment once. The DPX master server appliance is deployed as an OVA.
See also. For the latest system compatibility details regarding supported hardware, file systems, applications, operating systems, and service packs, see .
Virtualization Proxy Server. Installs virtualization proxy server software, which coordinates operations for virtualization restores and for agentless backups of virtual machines. The master server is a virtualization proxy server by default. Specify a virtualization proxy server when you define virtualization restore or agentless backup jobs. A 64-bit machine is required. Do not use a vCenter node as an agentless virtualization proxy server.
Related Topics:
in the User’s Guide
in the User’s Guide.
DPX open storage server. Installs DPX open storage server software, which is required for Block backup to open storage operations.
A DPX open storage server can be hosted on a master server appliance, though installation on a separate machine is recommended for best performance.
When you select DPX open storage server, the installer prompts you to perform a prerequisite check. You are notified if the server has insufficient memory or CPU. Additionally, the installer checks whether a tape library or tape drive is attached, though it does not prevent the installation if this check fails.
See .
Note that installation on virtual machines requires VMware Tools on the VM.
After making selections, click Next.
The Additional Options window may appear. The presented options vary, depending on the selections on the previous Setup Type dialog. Select check boxes as appropriate.
Note. If the installer detects that the node is in a cluster, a message indicates that a cluster node is detected. The installer then configures DPX for cluster protection capability on the node. However, note that cluster detection requires that Windows Cluster Service is started.
Click Next.
If you are installing on a client, skip the next step, which applies only to installation on a DPX master server appliance.
The Destinations Folder dialog appears.
Select the Destination Folder where you want to install DPX.
To install DPX in the default location, click Next. To change the location, click Change. Then enter or browse to the complete path and folder in which you want installed. Note that installing the product on the root of a partition is not supported.
Click Next.
The Add Node to Enterprise dialog appears. You can choose to add the node or not to add the node:
To add the node, select Yes, add this node into Enterprise.
To name the logical node something other than the name displayed, enter the new name in the Logical Node Name field.
To add the node to a node group other than the node group displayed in the Node Group Name field, enter a name in the Logical Node Group Name field. If the node group does not exist, DPX creates it.
If you do not want to add the node to the Enterprise, unselect the checked option. You can always add the node later, using the Configure function on the management console.
Click Next.
You might be prompted for a license key, which is contained in an email you receive with a new release or add-on components. You can copy-paste directly from the email. Alternatively, copy-paste from the email to a text file. You can then copy-paste from the text file or browse to it with the Browse button, which opens the text file and automatically copies the first line to the license key field. See in the User’s Guide.
Click Next. The Checksum Verification dialog appears. If the checksum matches the checksum shipped with the license key, click Yes. If the checksum does not match, ensure the license key file is an ASCII character string and does not contain any extra characters or new lines. If checksum still does not match, contact Catalogic Software Data Protection Technical Support..
Enter a password for user ID sysadmin. The second entry confirms the first. The system administrator is a special user with full rights to DPX. Click Next.
If you are installing on a master server appliance, skip the next step, which applies only to installation on clients.
The Destination Folder dialog appears.
Note. If you are installing on a node in a cluster, a check box alerts you that the installation directory must be the same for all nodes in the cluster and the nodes must not be on shared drives. Select the check box.
Select the destination folder where you want to install and click Next.
The Add Node to Enterprise dialog appears. You can choose to add the node or not to add the node:
To add the node, select Yes, add this node into Enterprise.
To name the logical node something other than the name displayed, enter the new name in the Logical Node Name field.
To add the node to a node group other than the node group displayed in the Node Group Name field, enter a name in the Node Group Name field. If the node group does not exist, DPX creates it.
Note. If you are installing on a cluster node, note that each cluster requires a dedicated node group. Add a cluster node to its dedicated node group. Only cluster nodes should be added to a cluster node group.
If you do not want to add the node to the Enterprise, unselect the checked option. You can always add the node later, using the Configure function on the management console.
Click Next.
Enter the master server host name. This is the resolvable name of the master server. Click Next.
If you are installing DPX on a cluster node, the Cluster Dry Run dialog appears. Enter the cluster IP (the DPX virtual IP address) and the submask. DPX checks the integrity of your cluster. If it fails, fix the cluster (see ), then reinstall. If it succeeds, the Cluster Setup dialog appears.
Domain Administrator. This account must be a local administrator on each cluster node, who has permissions to back up and restore cluster resources and applications.
Cluster Name. Enter a unique name, up to 15 characters, for the virtual resource. This is the DNS name of the virtual node. This name must not be the Windows cluster name that appears under the field. Do not use an underscore (_) in the Cluster Name.
Physical Node IP. Select the IP address for the node.
DPX Virtual Node IP. Enter the IP address for the virtual resource. This must be an available public network address different from the cluster IP address. When you install on other nodes in the cluster, supply this same IP for each node. This IP cannot be the Windows cluster IP or IP used by any other cluster service.
Subnet mask. Enter the subnet mask for the virtual resource. This field is enabled only for the final cluster node.
Network. Select the local network name to use.
For further cluster setup considerations, see .
Note. The Cluster Name and Virtual Node IP fields together define the DPX cluster virtual node. To define the required relationship between the cluster virtual node and the computer object in Active Directory, the cluster name account in Active Directory must have appropriate permissions. See .
Click Next.
In the Ready to Install Program dialog, click Install.
Note. During installation, you may be warned that you do not have enough disk space to successfully install the software.
See also. For the latest system compatibility details regarding supported hardware, file systems, applications, operating systems, and service packs, see .
After the installation completes, the Completion dialog appears. Selecting the Read additional requirements and install summary check box instructs InstallShield to display a summary of the file InstNote.txt, which can be found in the logs directory in the directory. This file and the summary contain important information about your installation, including any non-fatal errors during installation. Leave it checked and click Finish.
The file instNote.txt appears, along with a prompt to reboot the machine. Click Yes to reboot your machine now or No to reboot later. Reboot the machine before running a software update or any backups.
Tip. Running a software update is the next step to perform after the installation completes. It is recommended to reboot now to prepare for the software update.
To complete your installation, install the latest software updates. See .