Search Results

Search found 4 results on 1 pages for 'samselvaprabu'.

Page 1/1 | 1 

• Why are snapshots considered as temporary backups not real backups?

  - by Samselvaprabu

  I am using VMware ESXi. In our team we use to provide snapshots for long term backup. Then we faced issues like memory spillover and the server got hang up. I started reading in VMware knowledgebase articles and everywhere. Everywhere it was recommended not to have snapshots for a long time. Even VMware advised to keep snapshots for maximum of three days. But our team kept asking us to have at least two permanent snapshots (till deleting the VM). Sometimes we may use the VM for a year). one snapshot is for fresh machine state. (So when we complete testing an application, we will revert back to fresh state and install another application) (If I did not allow that, I may often need to host the VM.) Next snapshot for keeping the VM in some state (maybe they would have found an issue and keep that state for some time. Or they may install prerequisites for the application and keep the machine ready for testing.) Logically, their needs seems to be fair. But if I allow that, I am to permit them to hold the snapshots for long time. We are not using our VM as a mail server or database server. Why is keeping snapshots for long time having an adverse effect? Why are snapshots considered as temporary backups, not real backups?

  Read the article

• Why VM snapshots are affecting performance?

  - by Samselvaprabu

  I read in one of the VMware KB article says that snapshots will directly proportional to VM performance. But my team keep asking me how snapshots can affect performance. I would like to give them solid reason behind the statement that snapshots are performance killers. Can any one explain a little bit theory behind why actually snapshots are affecting the performance? Is it just because Disk I/O rate of hard disk would be slow?

  Read the article

• Does shutdown idle VMs improve the performance?

  - by Samselvaprabu

  Often our team members are coming to me with a compliant that their VMs are slow. Our team members suggested to shutdown some of the VMs temporarily and try to access the VM. But most cases that would not help. Assume that i have assigned 4 GB for and 2 CPUs for my VM. So ideally it should not face performance issue. As our ESXi 4.1 server has multiple VM in the same server (we have overcommited memory and CPU). Does shut down other VM really helps to improve performance or not? [Note : We are using ESXi 4.1 and our hardware is R710 server. We have more number of VMs in single server so we have overcommited memory.]

  Read the article

• How is memory allocated in ESXi server?

  - by Samselvaprabu

  We have an ESXi 4.1 server with 48 GB RAM. For each VM, we are allocating 4GB of memory. Since the server will have 13 virtual machines, my manager thinks this is wrong. I am going to explain to them that ESXi will actually manage memory itself, but they asked me how much memory I allocated for the ESXi server itself. I did not allocate any (I have not even heard of an option for allocating memory for the ESXi server itself). How is memory allocated for ESXi server? How does it over-allocate/distribute RAM among virtual machines without issue?

  Read the article

1