In this topic:
Installation of VASA Provider with Smart Deployment Wizard
Installation of VASA Provider with Smart Deployment Wizard in unattended mode
The VASA installation scenarios in Smart Deployment Wizard allow installing a first VASA node, or add a node to a highly available VASA configuration. The wizard installs the VASA provider on a specified local or remote machine, registers SANsymphony with the provider, and registers the provider with the vCenter. The wizard can only install VASA on a machine where SANsymphony is installed.
o The wizard creates the user dcsvasa with the local administrator privileges on all machines in the server group, and registers this user in SANsymphony with the roles Full Privileges and Vvol Managers. If the user already exists, the wizard will change its password to the one specified in the wizard.
o The VASA installer creates the service dcsvasa, and runs the service under the user dcsvasa.
o The VASA installer creates a firewall exception rule for TCP port 8443 for all profiles. This port is used for synchronization between VASA nodes, and communication between vCenter/ESX and VASA.
The following pre-requisites should be met on the machine where VASA is installed:
1 Windows version 2012 R2 or higher
2 SANsymphony PSP9 or higher
3 200 MB of free space on the system drive
4 For remote installation, remote WMI should be allowed
5 .Net 4.6.1 should be installed
6 Port 8443 should be free
1 Launch the wizard, select “Application and Server Tools -> VASA Storage Provider for VMware vSphere -> Install VASA Storage Provider”. Accept the license agreement.
2
Enter the name or IP address of the server where the VASA will be installed, and the user name and password to be used for the installation.
The user should exist and have the local administrator privileges on all machines in the server group, and should be registered in SANsymphony with the role Full Privileges.
3 Provide the path to the VASA installation package, and the password for the user dcsvasa that the wizard will create on all machines in the server group.
4
Provide the name or IP address and the credentials of the vCenter to register the VASA provider with.
5 Review the settings and run the installation.
1 Launch the wizard, select “Application and Server Tools -> VASA Storage Provider for VMware vSphere -> Install an additional VASA Storage Provider”. Accept the license agreement.
2
Enter the name or IP address of the server where the additional VASA provider will be installed, and the user name and password to be used for the installation.
The user should exist and have the local administrator privileges on all machines in the server group, and should be registered in SANsymphony with the role Full Privileges.
The user should be different from dcsvasa.
The wizard will validate that another instance of VASA provider is already installed on any server in the server group. This server is named partner server below.
3
Provide the path to the VASA installation package, and the password for the user dcsvasa.
The wizard will validate that the password matches the password of the dcsvasa user on the partner server, the dcsvasa service is running on it, and that the provider synchronization endpoint on port 8443 is replying.
4 Provide the name or IP address and the credentials of the vCenter to register the VASA provider with.
5 Review the settings and run the installation.
| -s, --server | : Required. VASA installation server host name or IP address. |
| -c, --credential | : VASA installation server credential. |
| -p, --password | : Required. DcsVasa password. |
| -i, --installer | : DataCore VASA Storage Provider installer package path. |
| -v, --vcenter | : Required. VMware vCenter server host name or IP address. |
| -l, --vccredential | : Required. VMware vCenter server credential. |
An example where only the required parameters are specified:
If the unattended installation fails, it can resumed from the failed step by running this command:
| -s, --server | : Required. VASA installation server host name or IP address. |
| -c, --credential | : VASA installation server credential. |
| -p, --password | : Required. DcsVasa password. |
| -i, --installer | : DataCore VASA Storage Provider installer package path. |
| -v, --vcenter | : Required. VMware vCenter server host name or IP address. |
| -l, --vccredential | : Required. VMware vCenter server credential. |
An example where only the required parameters are specified:
If the unattended installation fails, it can resumed from the failed step by running this command:
Smart Deployment Wizard version 10.0 PSP 10 does not have a scenario for upgrading the VASA provider. The upgrade should be run from the command line using the VASA installer file, DataCore.Vasa.Provider.PackageInstaller.exe.
1 Place the latest version of the VASA installer on your VASA provider node. Open the folder with the installer and run this command:
DataCore.Vasa.Provider.PackageInstaller.exe PASSWORD="Secret"
PASSWORD should match the password of the dcsvasa user that was specified during the installation of the provider.
Important Note:-
The installer does not validate that the new password matches the previous password. You should check the password of the dcsvasa user before the upgrade.
If you specify a different password, the upgrade will still work, but the provider may become unfunctional. If you forgot the password, see section Changing the password of the dcsvasa user .
2 Check that the provider status in vCenter is “online”, and that the provider datastores are healthy. If there are more nodes in this VASA group, repeat step #1 for the next node.
Follow this procedure if you need to change the password of the dcsavasa user:
1 On the machine where the VASA provider is installed, change the password of local user dcsvasa as usual. Then open the service dcsvasa, go to “Properties -> Log On”, and change the password there. Restart the service.
2 Check that the provider status in vCenter is “online”, and that the provider datastores are healthy. If there are more nodes in this VASA group, repeat step #1 for the next node.
If the upgrade from 2.0 to 2.0.1 fails (for example, if the specified password does not meet the Windows complexity requirements), the provider cannot fully roll back to its previous state and becomes unfunctional. Follow this procedure to recover the provider:
1 From the command line, run the command
do netsh http show sslcert
and save Certificate Hash and Application ID for the entry 0.0.0.0:8443, for example
Certificate Hash : 5627ff5c3adec0be79c8e202cbb7df8e8967f6c1
Application ID : {42fbbaa9-0fc3-4606-9136-415e21ec20de}
2 Delete the certificate binding by running this command
netsh http delete sslcert ipport=0.0.0.0:8443
3 Install VASA provider 2.0.1
DataCore.Vasa.Provider.PackageInstaller.exe PASSWORD="$Password"
4 Stop service dcsvasa
5
Copy database backup files from 'C:\ProgramData\DataCore\VASA Storage Provider\Backup' to 'C:\ProgramData\DataCore\VASA Storage Provider\'.
Rename them to DcsVasa.mdf and DcsVasa_log.ldf.
6 Assign ‘Full control’ permissions for user dcsvasa to files
DcsVasa.mdf and DcsVasa_log.ldf
7 Delete the certificate binding by running this command
netsh http delete sslcert ipport=0.0.0.0:8443
8 Add the binding for the certificate that you saved in step #2
netsh http add sslcert ipport=0.0.0.0:8443 certhash=5627ff5c3adec0be79c8e202cbb7df8e8967f6c1 appid={42fbbaa9-0fc3-4606-9136-415e21ec20de
9 Start service dcsvasa