HPE2-K45 Exam Dumps : Using HPE SimpliVity

• A stretched cluster is a configuration that allows two or more HPE SimpliVity clusters to span across different physical locations, while maintaining a single logical cluster and asingle management interface. A stretched cluster provides high availability, disaster recovery, and workload mobility for the virtual machines (VMs) running on the HPE SimpliVity platform12.
• A VDI infrastructure is a virtualization solution that delivers desktops and applications to end users from a centralized data center. VDI infrastructure can use different types of VMs, such as linked clones or full clones, to provide the desktops and applications to the end users. Linked clones are VMs that share a common base image and consume less storage space, while full clones are VMs that have their own independent copies of the base image and consume more storage space34.
• According to the HPE Reference Architecture for VMware Horizon on HPE SimpliVity document, both linked clones and full clones are supported on a stretched cluster. The document states that "HPE SimpliVity supports both linked clones and full clones on a stretched cluster. Linked clones are recommended for better storage efficiency and performance. Full clones can be used for persistent desktops that require more customization and personalization."5 The document also provides the design considerations and best practices for deploying VDI infrastructure on HPE SimpliVity stretched cluster, such as the network requirements, the VM placement, the backup and restore policies, and the failover and failback scenarios.

References:

1: HPE SimpliVity Stretched Cluster Guide 2: HPE SimpliVity Stretched Cluster 3: What is VDI (Virtual Desktop Infrastructure)? - VMware 4: What is a Linked Clone? - Definition from Techopedia 5: HPE Reference Architecture for VMware Horizon on HPE SimpliVity : [HPE SimpliVity Data Virtualization Platform] : [HPE SimpliVity Intelligent Workload Optimizer] : [HPE SimpliVity Federation Design and Scaling Guide]

 The difference between crash consistent and application consistent cloning methods is that the application consistent method ensures that the cloned virtual machine is in a consistent state with respect to the application and database, while the crash consistent method does not guarantee that1. The application consistent method uses the VMware snapshot or the Microsoft Volume Shadow Copy Service (VSS) to quiesce the application and flush the pending I/O operations to the disk before creating the clone, which prevents data corruption or loss2. The crash consistent method does not quiesce the application or flush the pending I/O operations, and creates the clone as if the virtual machine had crashed, which may result in data inconsistency or recovery issues3. The application consistent method is recommended for virtual machines that run database applications, such as SQL Server or Oracle, while the crash consistent method is suitable for virtual machines that run non-database applications, such as web servers or file servers4. The application consistent method is not available only for Linux operating systems (option D), as it also supports Windows Server operating systems that have VMware Tools or VSS installed5. The crash consistent method should not be used only for the virtual machines with Fault Tolerance enabled (option C), as it can be used for any virtual machine that does not require application consistency. Both methods are not the same,and the speed of cloning is not the only difference (option B), as they have different implications for the data integrity and availability of the cloned virtual machine. References:

• 1: Using HPE SimpliVity Official Certification Study Guide (HPE2-K45), HPE Press, 2019, p. 28.
• 2: Clone a virtual machine - techhub.hpe.com, HPE, 2021, 3.
• 3: HPE SimpliVity OmniStack Interoperability Guide 4.2.0, HPE, 2021, p. 8.
• 4: Using HPE SimpliVity Official Certification Study Guide (HPE2-K45), HPE Press, 2019, p. 29.
• 5: HPE SimpliVity OmniStack Interoperability Guide 4.2.0, HPE, 2021, p. 9.
• [6]: Using HPE SimpliVity Official Certification Study Guide (HPE2-K45), HPE Press, 2019, p. 28.
• [7]: Clone a virtual machine - techhub.hpe.com, HPE, 2021, 3.

According to the HPE SimpliVity Administration Guide1, the file level restore option allows you to recover individual files or folders from a backup of a virtual machine. Thisoption is useful when you need to restore a specific file that was accidentally deleted or corrupted, without affecting the rest of the virtual machine. The file level restore option supports both Windows and Linux based virtual machines, and can be performed using the HPE SimpliVity plugin in the vSphere Web Client. The file level restore option creates a temporary virtual machine from the backup, mounts the virtual disks, and copies the selected files or folders to a destination of your choice. The temporary virtual machine is then deleted automatically.

The other options are not suitable for recovering a single file from a Linux based virtual machine. Restoring a virtual machine from the backup would overwrite the entire virtual machine with the backup data, which may not be desirable or necessary. Moving a virtual machine from DR site to the primary site would not help if the file was deleted from both sites. Reverting to the SimpliVity snapshot would also overwrite the entire virtual machine with the snapshot data, which may not be the latest or the most relevant version. References:

• 1: HPE SimpliVity Administration Guide, https://support.hpe.com/hpesc/public/docDisplay?docId=sf000062138en_us&docLocale=en_US, page 76-78