Nokia problem

Recently I bought nokia 3110 classic looking its latest features. Everything was well and good until I found out the 'password' option for 'memory' card.
I thought it'll provide security to my datas and applications but after I fed the password I was amazed to find out that my mobile was unable to detect my 'memory card'. When I checked the memory status, its showed an 'unformat' memory which was not even getting formatted!
Also the PC do not detect the card. In short, the card was corrupted!
So, dear friends I would like to tell you that before you give password to your card, do consider it twice!!!

When to consolidate and when to delete VM snapshots in VMware

'Consolidate' and 'Delete' terms still confuse many of my fellow experienced IT Professionals.

Let me try to explain the difference in simple words:

Consolidate option was made available from VSphere 5.x onwards and prior to which we had only 'Delete' snapshots option.

Consolidation searches for hierarchies or delta disks to combine without violating data dependency i.e deletes all the redundant 'redo' logs which saves space in datastore and increases VM performance. This operation 'does not' delete the snapshots!

Delete / Delete All will actually delete the snapshots and changes present of the delta disks will be written back to the parent disk (flat.vmdk).

Please think twice before deleting the snapshots as it require space to be available in datastore. Make sure you have

 'snapshot size(delta file) + its parent disk size' space free in datastore, atleast.

Snapshot deletion process and space requirement in datastore is explained in my next post.

Snapshot deletion process

Space requirement in datastore to delete snapshot(s)

In this post, I will explain the snapshot deletion process in VMWare 4.0 and VI infrastructure 3.

Suppose we have 3 snapshots of 10, 30 and 20 GB respectively. When you click on delete snapshot, following happens:

-> A snapshot helper is created which holds all the changes.

-> Snapshot 3 will be copied to snapshot 2 and snapshot 2 might grow upto 50 GB

-> Snapshot 2 will be copied to snapshot 1 and will grow till 60 GB

-> Snapshot 1 will be committed to the original VM Disk file (flat.vmdk)

-> Helper snapshot disk will be committed to the original disk.

-> All snapshots will be deleted.

Snapshot deletion procedure:

Please note, when snapshots are created, original vmdk file becomes 'read-only' and all the changes made after are written to separate 'delta' disks.

This process changed in later version on VSphere 4.1 (and above), each snapshot gets merged to parent disk individually i.e. extra free space is not required - except for the helper file.

Also, below are some points to be noted about snapshots:

1. A snapshot file cannot grow larger than its parent disk.

2. Disk files are not deleted until all the snapshots are committed to parent disk.