VMware vSphere Distributed Switch (VDS) is a key virtual network platform that is scalable and extensible. It also provides advanced networking features and operational simplicity that helps build a flexible network for the cloud. The advanced networking features such as NIOC, LBT, NetFlow, and Port mirror are available on VDS and not on a virtual standard switch (VSS). This paper walks through the design process of incorporating VDS and its advanced features in different customer deployments.

Go here to read more and to download the PDF.

When and Why to use Snapshots.

By no means is a snapshot supposed to be used as a backup. A snapshot is great for mitigating risk before doing an update to a VM (Virtual Machine). A snapshot can cause issues if left unattended. For example, if you allow a snapshot or delta file unattended it can continue to grow, it will do so until there is no space left, what this will do is effectively bring every VM on that datastore to a halt. The only way to recover would be to commit that snapshot, and doing so on a full datastore can be very difficult.

When would you create a Snapshot.

You would create a snapshot in these scenarios.

- Before applying security updates and or patches to an OS
- Before installing a major application
- Before attempting the repair of a VM (OS based troubleshooting)
- Before removal of software, in case corruption occurs and you have to use a different method of removal

Removal of snapshots should be scheduled. For example, you create a snapshot, the description should have a short description and a date of when it was created. Once the snapshot is created, create yourself a calendar appointment to remove it a week later, that is probably the longest time you would want to leave a snapshot, any longer, you create the risk or major work being done to the VM and causing the snapshot/delta file to grow out of control.

You would not create snapshots in these scenarios

- You need a backup of an OS
- You are installing a piece of software that you need for a small project and it is intended you roll back to a pristine OS a couple months after.
- Before large DB work, exchange defrags, maintenance, large file transfers, etc.

When and Why to use Templating

Templates allow you to create a pristine copy of a VM without causing any downtime; this VM can then be restored at a later date if needed also the VM can be thin-provisioned to save on space. Creating a template doesn’t just duplicate the VM’s virtual disks, additionally, the VM’s .vmx configuration file is duplicated and renamed with the .vmtx extension, and this means that all the settings behind your VM are being duplicated as well. This saves time by reducing the number of wizards and dialog boxes you need to complete. Note that if a VM is currently in snapshot mode you will not be able to clone it.

When you would create VMware Templates

- When you need a backup of a VM because you are going to be working on it for a long period of time.
- An in place non-disruptive backup of a critical VM
- If you know that you will need to deploy multiple copies of a VM
- When you need a pristine copy of an environment for development testing, ie Install OS, Install SQL, install software package, template, then clone from template, repeat.

When you would not create VMware Templates

- Before applying security updates and or patches to an OS
- Before installing a major application
- Before attempting the repair of a VM (OS based troubleshooting)
- Before removal of software

For a limited time, buy VMware vSphere Essentials or Essentials Plus and get vSphere Fundamentals for SMBs online training free! If you’re new to virtualization, vSphere Fundamentals is designed to help you learn the vSphere Architecture, guide you through the installation, and understand best practices.

You will have till November 15th to redeems the tokens. I believe its only valid for US customers, which sucks for us up here in Canada. Never the less, its interesting enough for me to blog about.

Full Promo details here.

-NS

In Windows management, best practices are guidelines that are considered the ideal way, under normal circumstances, to configure a server as defined by experts. For example, it is considered a best practice for most server technologies to keep open only those ports required for the technologies to communicate with other networked computers, and block unused ports. While best practice violations, even critical ones, are not necessarily problematic, they indicate server configurations that can result in poor performance, poor reliability, unexpected conflicts, increased security risks, or other potential problems.

Best Practices Analyzer (BPA) is a server management tool that is available in Windows Server® 2008 R2. BPA can help administrators reduce best practice violations by scanning one or more roles that are installed on Windows Server 2008 R2, and reporting best practice violations to the administrator. Administrators can filter or exclude results from BPA reports that they do not have to see. Administrators can also perform BPA tasks by using either the Server Manager GUI, or Windows PowerShell cmdlets.

Check it out here.