Trending Topics

Implement and configure AWS Backup for VMware Cloud on AWS VM workloads

Image
In our previous post we saw the design of the AWS Backup on VMC. In this post we’re going through the implementation steps As per the design and best practice, we are going to use the ENI for the Backup traffic CREATE A VPC ENDPOINT  TO CREATE AN INTERFACE ENDPOINT FOR AN AWS SERVICE 1. Open the Amazon VPC console at https://console.aws.amazon.com/vpc    2. In the navigation pane, choose Endpoints 3. Choose Create endpoint 4. Name the endpoint   5. For Service category, choose AWS services 6. For Service name, search “ Backup ” and select “ backup-gateway ” service from the dropdown 7. For VPC, select the VPC which we used for SDDC deployment and extension 8. To create an interface endpoint for Amazon S3, you must “uncheck” Additional settings, Enable DNS name. This is because Amazon S3 does not support private DNS for interface VPC endpoints 9. For  Subnets , select one subnet per Availability Zone which we used for SDDC VMC selection  10. For Security group , sel

VMware: Creating iSCSI network in vSphere ESXi 5.0







Storage Adapter:





Nope.. by default it’s not installed, you must manual add the adapter by clicking Configuration > Storage Adapter > Add Storage Adapter





- Select: Add Software iSCSI Adapter





A new software iSCSI adapter will be added to the Storage Adapters list. After it has been added, select the software iSCSI adapter in the list and click on Properties to complete the configuration








Event: Change Software Internet SCSI Status = Completed


Create new vSwitch (in my case two VMkernel ports):





- Network label: iSCSI01





- Configure IP Address and Subnet Mask


..


- Finish the configuration, repeat this step to configure the 2nd iSCSI02 port


vSwitch2 result:





VMkernel – Override switch failover order:


Now we need to change the failover order for each VMkernel:





iSCSI01: Active Adapter VMNIC4 – Unused Adapter: VMNIC5

iSCSI02: Active Adapter VMNIC5 – Unused Adapter: VMNIC4


Configure Software iSCSI Initiator:


Go to the properties of the iSCSI initiator: Configuration > Storage Adapters > iSCSI Storage Adapter: vmhba** > Properties


And setup Dynamic Discovery – Sent Target location (in my case the StarWind VSA)





- Add target: 192.168.70.2:3260


Next we need to bind a pNIC to the iSCSI VMkernel.. looong loooong time ago (vSphere 4) ..we need to configure this by CLI (esxcli swiscsi nic add -n vmk1 -d vmhba33) but now it’s possible to do this via the GUI.


When you go to tab: Network Configuration > Add..





- Click: Add..





- Now you can select a Physical NIC to bind the VMkernel for your iSCSI targets





Overview:




VMkernel Port Bindings

iSCSI01


VMkernel Adapter

vmk1


Port Group Policy

Compliant


Path Status

Not Used


Physical Network Adapter

VMNIC4


Switch

vSwitch2


IP Address

192.168.70.10


Subnet Mask

255.255.255.0


Configured Speed

1000 Mbps (Full Duplex)





VMkernel Port Bindings

iSCSI02


VMkernel Adapter

vmk2


Port Group Policy

Compliant


Path Status

Not Used


Physical Network Adapter

VMNIC5


Switch

vSwitch2


IP Address

192.168.70.11


Subnet Mask

255.255.255.0



Now you can add the storage by clicking the “Add storage wizard”

Popular posts from this blog

HOW TO EDIT THE BCD REGISTRY FILE

AD LDS – Syncronizing AD LDS with Active Directory

DNS Scavenging.