Skip to main content

 Deep Drive VMware Clone


1. Full Clone

A full clone is a complete, independent copy of a virtual machine (VM). 

When you create a full clone, VMware creates a new VM with its own virtual hardware, and it copies all the files from the original VM to the new VM.

==============================================

Characteristics of Full Clones:

- Independent copy of the original VM

- Own virtual hardware

- Copies all files from the original VM

- Can be powered on and off independently

- Can be modified independently

=============================================

2. Linked Clone

A linked clone is a copy of a VM that shares the same virtual disk as the original VM.

 When you create a linked clone, VMware creates a new VM with its own virtual hardware, but it uses the same virtual disk as the original VM.

=================================================

Characteristics of Linked Clones:

- Shares the same virtual disk as the original VM

- Own virtual hardware

- Uses a delta disk to store changes

- Can be powered on and off independently

- Can be modified independently, but changes are stored in the delta disk

================================================

Key Differences:

- Disk usage: Full clones require more disk space, as they create a complete copy of the original VM's virtual disk. Linked clones, on the other hand, share the same virtual disk and use a delta disk to store changes.

- Independence: Full clones are completely independent of the original VM, while linked clones are dependent on the original VM's virtual disk.

- Performance: Linked clones can provide better performance, as they don't require the overhead of creating and maintaining a complete copy of the original VM's virtual disk.

Comments

Popular posts from this blog

Top 10 high-level EC2 scenario-based questions to challenge your AWS & DevOps skills

 Here are 10 high-level EC2 scenario-based questions to challenge your AWS & DevOps skills 1. Your EC2 instance is running but you can’t connect via SSH. What troubleshooting steps will you take?  Check Security Group inbound rules (port 22 open to your IP).  Verify Network ACLs (NACLs not blocking inbound/outbound).  Confirm instance’s Public IP / Elastic IP.  Validate Key Pair and correct permissions on .pem.  Ensure SSM Agent is installed (Session Manager can help).  Check system logs on the console for OS-level issues. 2. You terminated an EC2 instance by mistake. How can you prevent this in the future? Enable Termination Protection in EC2 settings. Use IAM permissions to restrict TerminateInstances. Tag critical instances and set resource policies. 3. Your EC2 instance needs to access an S3 bucket securely. What’s the best way to configure this? Best practice: Attach an IAM Role with least privilege policy to the EC2 instance. Avoid hardcoding...

GitOps-Driven Management of VKS Clusters: Enabling GitOps on VCF 9.0 (Part 03)

  GitOps-Driven Management of VKS Clusters: Enabling GitOps on VCF 9.0 (Part 03) In the Part-02 blog, we walked through the process of deploying an Argo CD instance within a vSphere Namespace on  VMware Cloud Foundation (VCF) 9.0 , enabling a GitOps-based approach to manage Kubernetes workloads in a vSphere environment. With Argo CD successfully installed, we now have a powerful toolset to drive declarative infrastructure and application delivery. In this blog post, we’ll take the next step by demonstrating how to  provision and manage VKS clusters  directly through the Argo CD  UI and CLI . This allows us to fully operationalise GitOps within the private cloud, delivering consistency, scalability, and automation across the Kubernetes lifecycle. Importance of Managing the Kubernetes Cluster with a Gitops Approach Adopting a GitOps-based approach for managing Kubernetes clusters enables declarative, version-controlled, and automated operations by leveraging Git a...
 https://knowledge.broadcom.com/external/article?articleNumber=389217 VMware Aria Suite Backup and Restore Documentation Issue/Introduction This article host backup and restore documentation for VMware Aria Suite 2019 product lines. Environment VMware Aria Suite 8.x VMware Aria Automation 8.x VMware Aria Automation Orchestrator 8.x Cause Technical documentation has been migrated from docs dot vmware dot com to  https://techdocs.broadcom.com . During this migration, some content considered End of Life (EOL) or End of General Support (EOGS) was not targeted for migration. Resolution PDF files are provided in this article while these documents are restored to https://techdocs.broadcom.com. Attachments Backup & Restore with EMC Avamar for VMware Aria Suite.pdf get_app Backup & Restore with Netbackup for VMware Aria Suite.pdf get_app VMware Aria Suite Backup and Restore by Using vSphere Data Protection.pdf get_app