Ask the Community
Groups
SAN-Direct Backups - Protecting VMs on a SAN (What is required?) - Connect IT Community | Kaseya
<main> <article class="userContent"> <h2 data-id="issue"><strong>ISSUE</strong></h2> <p>If you are using a Recovery-Series appliance, you have the option to protect the VMware Virtual Disks that are on a SAN (UEB/UB uses <a href="/home/leaving?allowTrusted=1&target=https%3A%2F%2Fpubs.vmware.com%2Fvsphere-51%2Findex.jsp%3Ftopic%3D%252Fcom.vmware.vddk.pg.doc%252FvddkDataStruct.5.5.html" rel="noopener nofollow">HotAdd Transport</a>). This can be done over iSCSI or Fibre Chanel. For best performance, you should use a dedicated connection between the SAN and the Unitrends system (or it should be a closed network that is separate from the users).<br> <br>The following requirements must first be met:<br> <br>Your Unitrends Recovery-Series Appliance should be running the latest version of the RecoveryOS (version 8.2 or newer) and the Guest VMs to protect must be running on licensed ESXi hosts running VMware vSphere version 5.1, 5.5, 6.0, or 6.5 with the following storage configurations:</p> <ul><li>a vCenter Server is required to be registered to the unitrends Appliance.</li> <li>Each ESXi host should also be added per best practices. </li> <li>SAN storage mounted on the ESX server as a VMFS data store.<br> or SAN storage mounted directly by the ESX guest as a <a href="/home/leaving?allowTrusted=1&target=https%3A%2F%2Fkb.vmware.com%2Fs%2Farticle%2F2009226" rel="noopener nofollow"><strong>Virtual (not Physical)</strong></a> <a href="/home/leaving?allowTrusted=1&target=https%3A%2F%2Fdocs.vmware.com%2Fen%2FVMware-vSphere%2F6.0%2Fcom.vmware.vsphere.storage.doc%2FGUID-9E206B41-4B2D-48F0-85A3-B8715D78E846.html" rel="noopener nofollow">RDM disk</a>.</li> <li>FC Connections must be single path or Active/Active ALUA. Multi-Path is not supported. </li> <li>For non-VAAI storage arrays, the ESX host may perform certain operations on the datastore<br>while the SAN-direct backup is running, causing a SCSI reservation conflict. In this case, the<br>backup will continue over the network instead of the SAN, which increases both backup time<br>and network traffic on the LAN. To reduce the probability of reservation conflicts, follow<br>VMware’s recommendations in the article <a href="/home/leaving?allowTrusted=1&target=https%3A%2F%2Fkb.vmware.com%2Fs%2Farticle%2F1021976" rel="noopener nofollow">Frequently Asked Questions for vStorage APIs for<br>Array Integration (1021976)</a>.</li> </ul><h2 data-id="resolution"><strong>RESOLUTION</strong></h2> <p> </p> <h3 data-id="to-configure-a-recovery-series-appliance-for-san-direct-backups-for-fiber-channel">To configure a Recovery-Series appliance for SAN-direct backups for Fiber Channel</h3> <p>The only configuration effort required is to ensure the SAN is compatible and ensure the Unitrends WWPN is provided and provisioned on required SAN LUNs that VMWare backups will occur for. With Unitrends use of VDDK 5.5 or higher and since release 9.0, the vprotect engine will determine compatible SAN paths from VMWare's own configuration, and VMWare will permit the use of that path automatically. Other than proper SAN and VMWare provisioning, no Unitrends UI configuration is required. <br><br>To identify the WWPN of your FC adapter in the Unitrends Appliance, see <a href="/home/leaving?allowTrusted=1&target=https%3A%2F%2Fkaseya.vanillacommunities.com%2Fkb%2Farticles%2Faliases%2Funitrends%2Fhc%2Fen-us%2Farticles%2F360013251438" rel="noopener nofollow">this KB</a>. <br> </p> <h3 data-id="to-configure-the-recovery-series-appliance-for-san-direct-backups-using-iscsi">To Configure the Recovery-Series appliance for SAN-direct backups using iSCSI</h3> <ol><li>Verify that the VMware SAN-direct requirements have been met.</li> <li>Physically connect the Unitrends Recovery-Series appliance to the VLAN used for iSCSI using a dedicated network adapter. <ul><li>Typically a 10G connection is used (note, on 1Gbit, SAN Direct and NBDSSL will have no perceivable performance difference unless the reason to use SAN Direct is to avoid network saturation.) </li> <li>iSCSI IPs and other production IPs should not share the same VLAN. </li> <li>Production LANs should not be able to route to iSCSI Networks through gateways. </li> </ul></li> <li>Log in to the backup system and select <span style="font-family: courier new;"><strong>Configure > Appliances > Select the local appliance > edit</strong></span> </li> </ol><div><span style="font-family: courier new;"><strong><img src="https://us.v-cdn.net/6032361/uploads/migrated/8S0CN9LT4CT6/eid-ka81w000000ka6v-feoid-00n40000003czoj-refid-0em1w000000iinp." alt="User-added image" width="500" height="273" class="embedImage-img importedEmbed-img"></img></strong></span></div> <ul><li>Complete the fields for iSCSI initiator and LUN selection for each LUN a VM resides in that requires protection.<br><br><img src="https://us.v-cdn.net/6032361/uploads/migrated/ZWVTDKAD17GF/san-direct-2.png" alt="san-direct-2.png" class="embedImage-img importedEmbed-img"></img></li> </ul><p> <br><strong>IMPORTANT!</strong> If vProtect cannot directly access the SAN, the backup runs using the network connection, moving the guest’s data from the external SAN through the ESX file system to the backup system. If using network bandwidth is a problem during certain hours, schedule your backups accordingly. This decision is macde by VMWare's protocols, not by unitrends. If SAN is configured but backups continue to use NBDSSL protocols, your SAN vendor or VMWare support or both may be asked to be engaged by Unitrends Support for further diagnosis. Unitrends cannot manage or configure your SAN or VMWare host directly, but we will be happy to participate in your vendor support calls to facilitate speed of resolution. <br> <br>To check whether the backup ran using the SAN-direct method, double-click the backup in the Status window or on the Backups report to view associated details. Look for the following in the Raw Output in the vProtect Messages section:</p> <ul><li> <strong>using transport method san</strong>: The SAN-direct connection was used for the backup.</li> <li> <strong>using transport method nbd</strong> (<strong>or</strong> <strong>nbdssl</strong>): The regular network connection was used for the backup.</li> </ul><p> <br>This information is located in the “VMware SAN-direct backups” section of the Unitrends Administrators Guide.:</p> <ul><li> <a href="/home/leaving?allowTrusted=1&target=https%3A%2F%2Fkaseya.vanillacommunities.com%2Fkb%2Farticles%2Faliases%2Funitrends%2Fhc%2Fen-us%2Farticles%2F360013261738" rel="noopener nofollow">Legacy Administrators Guide</a> under the topic (in Document Version 7.05192016, page 650)</li> <li> <a href="/home/leaving?allowTrusted=1&target=https%3A%2F%2Fkaseya.vanillacommunities.com%2Fkb%2Farticles%2Faliases%2Funitrends%2Fhc%2Fen-us%2Farticles%2F360013198957%3Fq%3DSELECT%2BId%252CSummary%252CIssue__c%252CAttachment__Body__s%252CResolution__c%252CAttachment__ContentType__s%252CAttachment__Length__s%252CAttachment__Name__s%252CTitle%252CKnowledgeArticleId%2Bfrom%2BHow_To__kav%2Bwhere%2BPublishStatus%253D%2527Online%2527" rel="noopener nofollow">Administrator Guide for Recovery Series and Unitrends Backup 10.3</a>, Chapter 6: Host-level Backups Overview (in 10.3.3 | Version 1.03042019, page 613.</li> </ul> </article> </main>