Volume Group in Nutanix and Mount in Client iSCSI Initiator Step by Step

 What is the Volume Group in Nutanix and How to create? And mount in client or Initiator machines

VGs enable you to separate the data vDisks from the VM's boot vDisk. This separation allows you to create a protection domain that consists only of the data vDisks for snapshots and cloning. In addition, VGs let you configure a cluster with shared-disk access across multiple VMs. Supported clustering applications include Oracle Real Application Cluster (RAC), IBM Spectrum Scale (formerly known as GPFS), Veritas InfoScale, and Red Hat Clustering. To attach the VG to multiple VMs when you use the aCLI, create it with a shared=true attribute. If you use Prism, answer yes when you attach the VG to a second VM. There are two ways to use Nutanix VGs: default VG and VGLB.

Note- : In short we are creating iSCSI disk, that we create in Windows server and allow the initiator to connect the disk and use it as a shared disk for MS Cluster.

Login to Prism 


Click Table -> Storage



Click Volume Group


Enter Volume Group Name

Description


Click Add New Disk


Drop down and select the Storage Container.


Give the size and click Add



Click Add New Client to allow access to connect this Volume group

Enter client machine IP or IQN 

Click Add


You may add multiple clients IP or IQN to connect with VG and use disk as cluster disk.



Click Save 

Go to Table -> Storage -> Table and Volume Goup to see newly created Volume Group


Select the Volume to see the summary

I have assigned two initiators



How to Map Volume in client machine


Login to Client Machine


Open iSCSI Initiator



Enter iSCSI provider IP (Nutanix Server Cluster IP)

Click Quick Connect


Refresh the page 


Go to Disk management to see mounted disk


Failed to install roles in Windows Server 2019 with error 0x80073701

 ISSUE:

Failed to install IIS roles on one Windows Server 2019 with error 0x80073701. 

 

TROUBLESHOOTING:

  1. We ran the scripts sfc /scannow and DISM.exe /Online /Cleanup-Image /Restorehealth to check the system file integrity, from the output of which we noticed the corruptions related to patch KB5014669 and KB5014022.




2023-05-09 09:26:34, Info                  CBS    =================================

2023-05-09 09:26:34, Info                  CBS    Checking System Update Readiness.

2023-05-09 09:26:34, Info                  CBS    

2023-05-09 09:26:34, Info                  CBS    (p)               CBS Catalog Missing            (n)                                           Package_5472_for_KB5014669~31bf3856ad364e35~amd64~~10.0.1.10

2023-05-09 09:26:34, Info                  CBS    Repair failed: Missing replacement mum/cat pair.

2023-05-09 09:26:34, Info                  CBS    (p)               CBS Catalog Missing            (n)                                           Package_5477_for_KB5014669~31bf3856ad364e35~amd64~~10.0.1.10

2023-05-09 09:26:34, Info                  CBS    Repair failed: Missing replacement mum/cat pair.

2023-05-09 09:26:34, Info                  CBS    (w)               CBS Package Index Package Missing               0x80070490                Package_2566_for_KB5014022~31bf3856ad364e35~amd64~~0.0.0.0                Package_2566_for_KB5014022~31bf3856ad364e35~amd64~~10.0.1.14              

2023-05-09 09:26:34, Info                  CBS    (w)               CBS Package Index Package Missing                0x80070490                Package_2567_for_KB5014022~31bf3856ad364e35~amd64~~0.0.0.0                Package_2567_for_KB5014022~31bf3856ad364e35~amd64~~10.0.1.14              


2. As I learned that we have deleted the reg keys for KB5014022 before, we suggested you restore the reg keys or reinstall the package to fix it.


  1. From the CBS log, we noticed that the assembly missing issue is caused by package KB5014669, thus we suggested to remove all the related reg key with script remove-Item -path "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\*KB5014669*".



2023-05-09 09:34:05, Error                 CSI    000068ef (F) STATUS_SXS_ASSEMBLY_MISSING #56773556# from CCSDirectTransaction::OperateEnding at index 0 of 1 operations, disposition 2[gle=0xd015000c]

2023-05-09 09:34:05, Error                 CSI    000068f0 (F) HRESULT_FROM_WIN32(ERROR_SXS_ASSEMBLY_MISSING) #56773398# from Windows::ServicingAPI::CCSITransaction::ICSITransaction_PinDeployment(Flags = 0, a = be61d6ca2ab4dcc4eede90c05a096ade, version 10.0.17763.1790, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}, cb = (null), s = (null), rid = 'Package_5931_for_KB5014669~31bf3856ad364e35~amd64~~10.0.1.10.5014669-10806_neutral', rah = (null), manpath = (null), catpath = (null), ed = 0, disp = 0)[gle=0x80073701]

2023-05-09 09:34:05, Info                  CBS    Failed to pin deployment while resolving Update: Package_5931_for_KB5014669~31bf3856ad364e35~amd64~~10.0.1.10.5014669-10806_neutral from file: (null) [HRESULT = 0x80073701 - ERROR_SXS_ASSEMBLY_MISSING]

2023-05-09 09:34:05, Info                  CBS    Failed to bulk stage deployment manifest and pin deployment for package:Package_3995_for_KB5023702~31bf3856ad364e35~amd64~~10.0.1.10 [HRESULT = 0x80073701 - ERROR_SXS_ASSEMBLY_MISSING]


RESOLUTION:

1. Restore the reg key related to KB5014022 or re-install the patch KB5014022 to fix the corruption.

2. Remove the package KB5014669 by running remove-Item -path "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\*KB5014669*" with powershell as admin.

 

RELATED KNOWLEDGE BASE ARTICLES:

Windows Update (microsoft.com)

Windows Update troubleshooting - Windows Deployment | Microsoft Docs 


Steps to upgrade NSX-T from 4.0.0 to 4.1.0

You may refer below link to download the next version that you want to upgrade.

https://www.virten.net/vmware/nsx/vmware-nsx-t-release-build-numbers/

Login to NSX-T console using Admin account

System -> Under Lifecycle Management -> Click Upgrade



Select MUB file path that you have downloaded ->



Download the supported MUB file



Upload the file VMware-NSX-upgrade-bundle-4.1.0.2.0.21761719-le.mub


Click Upload



Now .MUB file is getting upload, wait for to complete upload



After Uploading extracting the bundle and verifying compatibility



Now Extracting Upgrade Bundle



Now checking Compatibility Matrix of the Upgrade Bundle




Post all validation completion 

Click on Prepare for Upgrade



Accept the License Agreement


Preparing for Upgrade


Click Run Pre Checks



Pre-Check is running





Once Pre Check complete


Click Start Upgrade


Now Upgrade has completed



Now wait for complete the Upgrade

Upgrade completed with new version NSX-T 4.1.0.2.0.21761719








Restore Files and folders, NTFS Permission only using Veeam Backup & Replication

 Open Veeam Backup & Replication

Home -> Backup -> Disk


Select File Server Job Name -> Right click on Job Name

Select Restore guest files -> Microsoft Windows



Select the Restore Point



Click Next and follow the instruction -> Browse




Mounting the drives



Select the folder that you want to Restore


Right click on the folder -> Restore (If you want to overwrite the restore files and folders)


Else click on Restore to (If you want to restore files and folder on different location)



Note-: You may also restore Permissions only using the Veeam Backup & Replication.

 





Schedule back with Excluded disk in Veeam Backup and Replication 12


Once you configure a job with an excluded disk, the excluded disk will not participate in backup.

If still, you want to configure the excluded disk in the restore VM then you can attach the disk from vCenter level.

Edit the VM property and add the existing disk, but before doing this you need to capture the existing disk path.

I have already created a backup job, you may refer Create Backup Job in Veeam Backup and Replication 12 to create a backup job.



Now I am going to modify the Backup Job that I have created.

Right Click on the Job -> Click Edit




Go to Virtual Machines -> Select the Virtual Machine


Click Exclusions



Select VM click on Edit


Select the Disk that you want to Exclude


Once done click Finish



Create Backup Job In Veeam Backup & Replication | Backup Job in VBR

 

Create Backup Job in Veeam Backup and Replication 12

 

I am creating a job to schedule backups with default configuration.

In the later document I will schedule backup with excluded Drive and also,

how to take SQL Transaction log backup.


How to create backup Job SQL server of SQL server Using Tlog

Open Veeam Backup and Replication

Click Home -> Job



Right Click on Backup under Job -> Backup -> Select the backup type that you want to configure

like Virtual Machine, Windows Computer or File Share


I am going to configure Virtual Machine -> Give the Backup Name that you want to configure.



Click Add -> Expend the vCenter from the list and Select the VM that you want to take Backup


Or simply Type VM Name and Search, you will see list of the VMs containing the Name



Select the VM from the list and click Add


Click Next

Select the Backup Repository where you want to keep your backup

Also set the Retention policy to keep full backup longer for Archival purpose



You may configure GRF Retention Policy as well to Keep Weekly Full backup for how long time



Then click next


Click next and Configure the Job Schedule



Click Apply


If you want to run backup job on scheduled Date and Time, then click finish without check mark on 

Run the Job when click Finish


Featured Post

HPE MSA 2040 configuration step by step

HPE MSA 2040 configuration Default IP range for HP SAN storage MSA 2040 is 10.0.0.1/2 You need to connect your laptop and storage with...