By default, NetVault Backup runs a maximum of 50 concurrent push-installation processes. You can modify the default settings to increase the number of concurrent processes. For more information, see Configuring default settings for Deployment Manager.
Before you start the push installation procedure, verify that the following requirements are met:
• |
Copy the packages to a shared location: Copy the client and plug-in packages to a shared location. Only CIFS shares are currently supported as package stores. The path must be accessible to the NetVault Backup Server and all target machines where you want to install the packages. |
• |
Configure a package store in NetVault Backup: After copying the installation packages, configure the shared location details in NetVault Backup. For more information, see Configuring a package store. |
• |
Configure the preferred network address setting on multihomed NetVault Backup Servers: On multihomed NetVault Backup Servers, configure the Preferred Network Address setting to allow the remote clients to send status messages to the correct address. For more information about this setting, see Configuring network addresses for multihomed machines. |
• |
Verify that the firewall is configured to allow traffic through the ports required for push installation: To push the client and plug-in packages to a remote machine, the NetVault Backup Server establishes the initial WMI session with the remote machine using RPC over port 135. All further WMI traffic uses the dynamic port range of 49152 through 65535. |
This section includes the following topics:
1 |
In the Navigation pane, click Guided Configuration, and then on the NetVault Configuration Wizard page, click Install Software/Add Clients. |
2 |
3 |
Click Manage Stores, and provide the following details. |
Provide the UNC (uniform naming convention) path of the CIFS (Common Internet File System) share. The format for specifying the path is: NOTE: If the server IP address is used to configure a local package store (for example, \\10.11.12.3\PkgStore), the user credentials are not validated when the package store is added or updated. If you specify invalid credentials, no errors are reported. However, the deployment task fails if the authentication fails and the packages cannot be retrieved from the store. Therefore, we recommend that you use the server name when configuring the path to a local store (for example, \\WinServer1\PkgStore). | |
Specify a user account that can be used to access the CIFS share. | |
4 |
© 2021 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy