Learn And Share: November 2015

Friday, 27 November 2015

To Use Hyper V in Vmware Workstation

hypervisor.cpuid.v0 = “FALSE”

Add the above line in .VMX file for the vm used for Hyper V

Tuesday, 24 November 2015

VM Deployment

VMware vSphere is one of the most stable, reliable platforms available for building virtulize - cloud infrastructures.

Are you ready to get started?

Just take a few minutes first to consider some important deployment factors. First and foremost is hardware. No, really, you have to get the right hardware.

1. Get the Right HardwareDon’t assume that just any server, CPU, or other hardware component is compatible with vSphere, because only a few are. Incompatible hardware means some or all of the features won’t work, such as Fault Tolerance and Direct Path I/O.
Without the right hardware, vSphere just won’t work. At best, there will be a whole lot of really important features that don’t work. There is an extremely narrow set of hardware components that are certified to work with vSphere. You have to be sure you have one of the certified:

Servers
CPU
Storage adapters
Network adapters
Storage

Bear in mind that the latest VMware vSphere versions are only compatible with 64-bit hardware, so customers still using 32-bit hardware are out of luck. Though the approved hardware components are manufactured by popular makers like Intel and AMD, you can’t assume that all Intel and AMD products are certified, because they aren’t.
Check the Compatibility Guide before buying or prepare to get your feelings hurt.

2. Get the Right Software Licenses: Software vendors have started cracking down on software licensing infringements with a vengeance in recent years. Some of the most aggressive are the big guys like Microsoft, Oracle, and SAP. IBM and AutoDesk are also getting a bad rep for knocking on doors and demanding software audits. Don’t let this simple oversight cost you (and it will: potentially tens of thousands of dollars). Get the software licenses you need and set up some kind of SAM to keep yourself out of hot water in the future.

3. Size the Host Correctly: Each host has to be set up for the appropriate size in order to properly mange the apps that are installed and operated in that environment. You don’t have to guess at it, because there are tools to help you determine what size to set up the host in a given scenario for optimal performance (and profits). Use one of the available tools to determine the right host size in your environment.

4. Monitor Your Clients More Than a Few Hours or Days:
You won’t be able to get a good read on each client’s metrics during the first day or first few days. Monitor your customers over the course of a whole month to get a clear picture of the average and peak workloads you’re dealing with.

Another common deployment mistake is to monitor clients for just a day or less to determine their needs. Average and peak usage can’t really be measured unless you monitor the situation for a full month. By then, you should have collected adequate metrics to properly address the average and peak workloads of each customer.
A little planning now can save you a lot of trouble, expense, and frustration in the long run. For a near-time monitoring solution to improve your VMware performance and free up as much as 60% of your time, visit Opvizor today.

Vmware Snapshot Best Practise

What is VMware Virtual machine snapshot and best practice, in below.

Snapshots are not backups. A snapshot file is only a change log of the original virtual disk. Therefore, do not rely on it as a direct backup process. The virtual machine is running on the most current snapshot, not the original vmdk disk files.

Snapshots are not complete copies of the original vmdk disk files. Taking a snapshot does not create a complete copy of the original vmdk disk file, rather it only copies the delta disks. The change log in the snapshot file combines with the original disk files to make up the current state of the virtual machine. If the base disks are deleted, the snapshot files are useless.
Delta files can grow to the same size as the original base disk file, which is why the provisioned storage size of a virtual machine increases by an amount up to the original size of the virtual machine multiplied by the number of snapshots on the virtual machine.

The maximum supported amount of snapshots in a chain is 32. However, VMware recommends that you use only 2-3 snapshots in a chain.
Use no single snapshot for more than 24-72 hours. Snapshots should not be maintained over long periods of time for application or Virtual Machine version control purposes.
This prevents snapshots from growing so large as to cause issues when deleting/committing them to the original virtual machine disks. Take the snapshot, make the changes to the virtual machine, and delete/commit the snapshot as soon as you have verified the proper working state of the virtual machine.
Be especially diligent with snapshot use on high-transaction virtual machines such as email and database servers. These snapshots can very quickly grow in size, filling Datastore space. Commit snapshots on these virtual machines as soon as you have verified the proper working state of the process you are testing.
An excessive number of delta files in a chain (caused by an excessive number of snapshots) or large delta files may cause decreased virtual machine and host performance

If using a third party product that takes advantage of snapshots (such as virtual machine backup software), regularly monitor systems configured for backups to ensure that no snapshots remain active for extensive periods of time.
Snapshots should only be present for the duration of the backup process.
Snapshots taken by third party software (called via API) may not show up in the vCenter Snapshot Manager. Routinely check for snapshots through the command-line.

For more info, kindly refer VMware KB - http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1025279

Microsoft Virtual Tech Labs

Microsoft E-Books Free Download

Please refer below link to download E-Books free

http://blogs.msdn.com/b/mssmallbiz/archive/2015/07/07/i-m-giving-away-millions-of-free-microsoft-ebooks-again-including-windows-10-windows-8-1-windows-8-windows-7-office-2013-office-365-sharepoint-2013-dynamics-crm-powershell-exchange-server-lync-2013-system-center-azure-clo.aspx

Cloud Certifications

Below are some of the Cloud certification offered by popular vendors. This is only for Admin related certification. Please refer respective vendor site for prerequisite and other details
If you know any other Cloud admin certification available in the market, Please feel free to share

VMWare
VMware Certified Associate – Cloud (VCA-Cloud)
VMware Certified Professional – Cloud (VCP-Cloud)
VMware Certified Advanced Professional – Cloud Infrastructure Design (VCAP-CID)
VMware Certified Advanced Professional – Cloud Infrastructure Administration (VCAP-CIA)
VMware Certified Design Expert – Cloud (VCDX-Cloud)

Microsoft
Microsoft Certified Solutions Expert (MCSE) Private Cloud
Microsoft Specialist certification in Office 365
Microsoft Certified Specialist Implementing Microsoft Azure Infrastructure Solutions

Amazon Web Services (AWS)
AWS Certified Solutions Architect - Professional
AWS Certified Solutions Architect - Associate
AWS Certified SysOps Administrator - Associate
AWS Certified DevOps Engineer - Professional

IBM
IBM Certified Solution Advisor - Cloud Computing Architecture V3
IBM Certified Solution Architect

EMC
EMC Cloud Infrastructure and Services (EMCCIS)
EMC Cloud Architect Virtualized Infrastructure
EMC Cloud Architect IT-as-a-Service

Oracle
Oracle Certified Master, Database Cloud Administrator
Oracle Certified Professional, Database Cloud Administrator

Red Hat
Red Hat Certificate of Expertise in Hybrid Cloud Storage
Red Hat Certified System Administrator in Red Hat OpenStack

Pages