VMware 101 Series - VM Snapshot

series of VMware 101 my name is the handshake today I'm going to talk about VM snapshot let's get started if you're not subscribed my channel please subscribe my channel it's it's hardly 1 a.m. and I'm creating and recording this video only for you guys thanks so much what is VMs snapshot the snapshot is a technology which can which can help you to take a point-in-time snapshot appointing them backup of the virtual machine and you can keep doing continual work and you can go back to that particular stage where the snapshot was taken ok it was really short but I'll explain you in this session so this is my virtual machine and I use this virtual machine for a daily purpose and let's assume this is our weapon virtual machine and I do these database related work on this virtual machine and I have a requirement that every day I need to start with the fresh database so what I can do I can install the virtual machine installed the database application like Microsoft sequel server application and I can create a snapshot which is snapshot one and what after they staff creation of snapshot I can start working on the virtual machine and this is my state 1 the I create a data is 1 and if my work is done what I can do I can go back to the snap 1 and what it works the task which I had done after the snapshot we get it is automatically and I mean happiness exact same data or I can chain one more snapshot after creating data bus 1 which will be my snap to and after take the snapshot I will be having this third stage where I will be running well we have where I will be current status of this is my status they are currently I can go back to snapshot 1 or I can go to a snapshot first after the snap one off snapshot to when I go back to the snapshot 1 I mean we have in the VM with the sequel server installation no database if I go back to the snapshot - which is here I will be hanging a VM with the sequence of our installation as well as where the database is also created so what is the meaning of going back going back is nothing but after this creation of database 1 whatever changes if I don't database 3 right the Turks - I created a base 2 here and if I go back to snapshot 1 I lose this data ok if I go back to this one so if I whenever I went to the snapshot the status where I was I was running is basically gates gets over it and all its get basically a deleted ok this is called a snapshot revert process there is one more process called the snapshot delete and what happened when you leave the snapshot means if I want to commit this data entry going about your machine or william decayed i think simply create the snapshot and whatever changes was happening after this we get committed to the VMDK ok talking about the snapshot all the vmware never support up to 32 snapshot so one virtual machine you can create up to 32 snapshots and you can revert all go back to the in a snapshot or a mistake let me tell you how this wasn't back in ok when will we create a virtual machine as I told you if you have seen my on your video all the virtual machine components there are some dis some some files called a vm d a vm ax and and some other files as well so whenever i do any writing without any snapshot of the virtual machine my data or whatever whatever great i am writing on the virtual machine will get written directly on VMDK so we have negated my days when I create snapshot basically its create that VM BK as a real and it's clean one more dist it's V MSP virtual machine the VMDK file which is acting as a VM SM file and which is nothing but the snapshot disk and this snapshot disk read and write and whatever changes mean wha other the snapshot will get written here even if we delete anything it will get written here that this data has been deleted whenever you request anything to be to be read from the void or existing which BMD here let's assume there's some files which was originally written on this VM it will be read from this but after whatever right we will do it we will do it here if you delete something from you know this will not get deleted from here it will just get committed here that some file that file has been deleted whenever you add one more snapshot basically it's create upon you make that file and the read-only and then it will create another snapshot file and that will be has a read write mode and you will be pointed to the then your next location will be getting written here so whatever task or whatever changes will do will get written on the snapshot disk when you when you if you went back to the snapshot what happened so let's say you take one more snap shown you you go back to this snapshot so this finally becomes a rewrite and then you will be able to access those things and you can make you will be able you you will make those changes and you can clear one was not get out of that so up to 32 you can go to and you can hear the snapshot there is misconception about the above the deletion and B and they revert to the snapshot and that is the main reason I am creating this video what is the deletion of snapshot if I delete the snapshot that means whatever data I have that means via where I had the at this situation I have this sequel server installation with the database one and Adam is two or database one if I do that actually we are making it when how those committing and my VMDK whatever changes was was half this Munich a million committed on actually on beacon and I will the snapshot we get deleted or there you can go back to the stage there but the data is out there it will get committed into the into the original disk and so this is the this is the basically difference between the shell of the snapshot and the they went back to the snapshot when you referred back to snapshot so let's say I have here and I went back to here so I will be having a snapshot or virtual machine with just a sequel server installation if I rewind back put this snapshot I mean we're having oho machine with the with the one database if I everyone back to this snapshot I will be having a virtual machine with two databases and these are the way I can and if I wanted to finally have those two databases to the VMB gate I can delete all these snapshots and I ever think we'll be getting written into this virtual VM beacon or which is the library Omega so this is how the snapshot things work this important thing is snapshot trying or the snapshot discs are always within this and there is no only a low limit on this so you may say that virtual machine with 40 GB but but the snapshot file may increase up to 400 GB as well because these are this thing basically whatever changes you two will get committed on to the virtual machine so you let's say you need 20 GB data it will get committed to the disk even if you believe that if you actually get committed notice and and whenever you do snapshot snapshot snapshot there might be chances you may crash virtual machine and so there is some limitation that SRM does not support up after some level of snapshots and and we may see a recovery that's completely different story but architects or the vml engineers they they always recommend not to have a snapshot on the virtual machine more than seven days because it making it a problem because snapshot is become cue huge and when you delete those snapshot that commitment or consolidation of the day stick too much time and till that time virtual machine can be responsive and you may see the downtime in your in your server so make sure you use snapshot carefully this is a really good feature you can use it you just make sure you memorize the snapshot was they can and need to be clean up I had an article written in on my blog how you can monitor the snapshot there is a simple command you can run on the center / on your recent ur and it will give you the list of virtual machines which are having the snapshot that will be helping that is from the snapshot site I hope you must have learned something from this video and I hope you would have liked you would have enjoyed this video it's 1:30 a.m. in night I'm recording this video for you guys only I would recommend please like subscribe my channel put that coming comments and the questions in the chat box or another comment box and let me know if you need any help from my site thank you so much for watching see you in another video bye

Channel: Rahim Shaikh

Views: 2,753

Keywords: vmware training, VCP, VCA, Certification, Cloud, AWS, rahimshiakh.com, rahim shaikh, disaster recovery, RTO, RPO, Active Directory, BCP, DR, Production, ATOT, ATOD, SRM, VMware, ESXi, vCenter, Network, Storage, VM, Physical, CPU, RAM, Disk, solution architect, windows, servers, linux, Microsoft, Azure, local, remote, replication, cloud

Id: awvIKLN1bFo

Length: 9min 18sec (558 seconds)

Published: Sat Aug 24 2019