Source:Installing VDDK: Difference between revisions
(Marked this version for translation) |
(Fixed links.) |
||
Line 11: | Line 11: | ||
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;" | {|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;" | ||
| rowspan="2" style="padding:0px 10px 0px;" | <translate><!--T:5--> | | rowspan="2" style="padding:0px 10px 0px;" | <translate><!--T:5--> | ||
[[File:SEP_next.png|45px|link=Special:MyLanguage/VMware_Requirements_%26_Restrictions|VMware Requirements & Restrictions]]</translate> | [[File:SEP_next.png|45px|link=Special:MyLanguage/4_4_3:VMware_Requirements_%26_Restrictions|VMware Requirements & Restrictions]]</translate> | ||
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | <translate><!--T:6--> | | style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | <translate><!--T:6--> | ||
See also: [[Special:MyLanguage/VDDK_Compatibility_Matrix|VDDK Compatibility Matrix]] – [[Special:MyLanguage/What_is_a_SEP_sesam_DataMover#SEP_sesam_DataMover_for_VMware_vSphere (SDM-VV)|What is a SEP sesam Data Mover]] – [[Special:MyLanguage/VMware_Requirements_%26_Restrictions|VMware Requirements & Restrictions]] – [[Special:MyLanguage/VMware_Backup|VMware Backup]]</translate> | See also: [[Special:MyLanguage/VDDK_Compatibility_Matrix|VDDK Compatibility Matrix]] – [[Special:MyLanguage/What_is_a_SEP_sesam_DataMover#SEP_sesam_DataMover_for_VMware_vSphere (SDM-VV)|What is a SEP sesam Data Mover]] – [[Special:MyLanguage/4_4_3:VMware_Requirements_%26_Restrictions|VMware Requirements & Restrictions]] – [[Special:MyLanguage/4_4_3_Tigon:VMware_Backup|VMware Backup]]</translate> | ||
|} | |} | ||
Line 91: | Line 91: | ||
<div class="noprint"> | <div class="noprint"> | ||
==See also== <!--T:34--> | ==See also== <!--T:34--> | ||
[[Special:MyLanguage/What_is_a_SEP_sesam_DataMover#SEP_sesam_DataMover_for_VMware_vSphere (SDM-VV)|What is a SEP sesam Data Mover]] – [[Special:MyLanguage/VMware_Requirements_%26_Restrictions|VMware Requirements & Restrictions]] – [[Special:MyLanguage/VDDK_Compatibility_Matrix|VDDK Compatibility Matrix]] – [[Special:MyLanguage/VMware_Backup|VMware Backup]] – [[Special:MyLanguage/VMware_Single_File_Restore|VMware Single File Restore]] – [[Special:MyLanguage/Troubleshooting_Guide#VMware_vStorage_API|VMware troubleshooting]]</div></translate> | [[Special:MyLanguage/What_is_a_SEP_sesam_DataMover#SEP_sesam_DataMover_for_VMware_vSphere (SDM-VV)|What is a SEP sesam Data Mover]] – [[Special:MyLanguage/4_4_3:VMware_Requirements_%26_Restrictions|VMware Requirements & Restrictions]] – [[Special:MyLanguage/VDDK_Compatibility_Matrix|VDDK Compatibility Matrix]] – [[Special:MyLanguage/4_4_3_Tigon:VMware_Backup|VMware Backup]] – [[Special:MyLanguage/4_4_3:VMware_Single_File_Restore|VMware Single File Restore]] – [[Special:MyLanguage/Troubleshooting_Guide#VMware_vStorage_API|VMware troubleshooting]]</div></translate> |
Revision as of 15:21, 13 February 2019
Overview
SEP sesam requires the VMware Virtual Disk Development Kit (VDDK) to be installed on SEP sesam data mover (SDM-VV). A data mover role for VMware vSphere can be combined either with a SEP sesam Server, SEP sesam Remote Device Server or SEP sesam Client.
On Windows, VDDK is installed automatically during the SEP sesam installation. However, if you use a new vSphere version you should check the VDDK Compatibility Matrix to find its corresponding VDDK version and install it manually, if required. On Linux, you have to install the required VDDK version manually. Note that every new release of vSphere has a corresponding VDDK version; typically, the version number of VDDK matches the version number of vSphere. For details on the required version, see VDDK Compatibility Matrix.
Installing VDDK on Linux
For details on the required version, see VDDK Compatibility Matrix. Then download the required VDDK for Linux from the VMware download center. Choose the binary tar.gz for 64-bit Linux, then unpack and install the VDDK as shown in the example.
- If a previous VDDK installation exists, run the following: rm -r /usr/lib/vmware-vix-disklib/
- Unpack the archive with tar to create the vmware-vix-disklib-distrib subdirectory. tar xvzf VMware-vix-disklib-<distrib>.tar.gz cp -r vmware-vix-disklib-distrib/ /usr/lib/vmware-vix-disklib The VMware VDDK will be installed to
- Install components as needed.
- Restart the SEP sesam service for the changes to take effect.
/usr/lib
as default.
Note | |
SEP only supports installation of VDDK into the default path! |
Installing VDDK on Windows
VDDK is installed automatically during the SEP sesam installation, but you may have to install another version (for details, see VMware support matrix). For example, VDDK 6.0.x in combination with vSphere 6.5 does not provide SAN transport support when using datastores formatted with new VMFS 6.0 filesystem. In such case, you have to install the corresponding VDDK version manually.
For details on the required version, see VDDK Compatibility Matrix.
- Download the required .zip file for Windows from the VMware download center and download it to skel directory on the VMware data mover.
- Use the PowerShell script set_vddk.ps1 (as shown below ) to automatically execute the .bat file, update the required libraries and set the registry key correctly.
- Some versions, for example, VDDK 6.5.x on Windows, might require rebooting the host after the update. This is required when attempting to mount a VMDK save set, stored on a data store, to the local system.
- After a reboot, run the following script from the command line:
vstor2install.bat in directory C:\Program Files\VMware\VMware Virtual Disk Development Kit\bin.
Note | |
By default, the Powershell execution policy is set to Restricted. To execute the PowerShell scripts, set the execution policy to RemoteSigned by using the set-executionpolicy remotesigned command. Note that you must be logged in as administrator or start the script with administrative privileges. For more information on PowerShell script execution policy, see Using the Set-ExecutionPolicy Cmdlet. |
Open the <SESAM_ROOT>/bin/sesam/
directory and execute set_vddk.ps1 -e update.