VIOPS: Proven Practices for Deploying and Managing VMware : All Content - All Communities

VSphere on DELL PowerEdge 1850R

fmbraga — Sun, 22 Nov 2009 08:22:13 GMT

Hi Martin,

Have you upgraded your BIOS firmware ? You'll only be able to install 64-bit guests if you enable Virtualization Support in CPU configuration. Some of the latest 1850 do support Intel-VT, some of the oldest don't, unfortunattely.

Good luck,

Importing VMDK file created on ESX2.5 to ESX3i

myemmi — Fri, 20 Nov 2009 14:37:05 GMT

Hi Everyone,

First time in this community. I was just wondering if anyone tried or knows if we can import VMDK files created using ESX2.5 enterprise version into ESX3i (free version)?

Thanks You very much.

Mourad

Converter error

liddig1 — Thu, 12 Nov 2009 08:40:48 GMT

Hi,

I'd also check the status of the vss writers on the server you are tyring to clone. Run 'vssadm list writers' from a command prompt to see if everything is ok..

Regards,
Gary

VSphere on DELL PowerEdge 1850R

BlackMamba — Thu, 12 Nov 2009 02:47:05 GMT

Guys,

I have 2 DELL PowerEdge 1850R that I would like to deploy in production. THE CPU is supportedly a 64 bit CPU and got VSphere running successfully.

However, I am unable to install any 64bit O/S. I am kinda stumped. If VSphere sees the CPU as 64bit, why the heck won't Microsoft O/S see the CPU as 64 bit. Is there a setting I am missing? Please advise.

Cheers

martin

vSRM VLAN configuration?

vikash_roy — Tue, 10 Nov 2009 15:17:30 GMT

Check my earlier email

Mirroring two ESX Servers with direct attached arrays

vikash_roy — Tue, 10 Nov 2009 10:28:09 GMT

For the error :

Install the P2V client tool on Windows 2003 physical server manually and try to follow some best practice for P2V. I have updated few on my blog http://www.google.com/search?q=P2V&sitesearch=vikashkumarroy.blogspot.com

For this kind of scenario you must use stand alone P2V tool.

Coming to what you are looking at

1. Install ESX host on both DL380.
2. I guess when you talks about HA/DRS and fail over then you may have VC license. So add both the ESX host into VC.
3. Create a new VM with windows 2003 or use the one which you are doing P2V.
4. Now create NFS share on win2k3 using blog http://vmetc.com/2008/02/19/create-a-nfs-share-for-vm-iso-files-with-windows-200 3-server-r2/
5. When you are installing NFS service on windows , you have like to install it on both ESX host . The reason when one of the ESX host is down the VM will go down which means your shared storage is down. But if you create VM on both the ESX host then you can provide redundancy for each ESX host.
6. Once you are shared NFS folder on WIN2K3, create VMKernal port on each ESX host and mount NFS store on it . You then create datastore and then put VM inside.
7. These NFS can be shared on both the ESX host so that you can enjoy benefit of vmotion /HA

Let us know how it goes

Vikash

My Blog

Creating a file or fullVM VCB backup on a disk by disk basis

theether — Wed, 19 Aug 2009 03:00:25 GMT

Introduction

This proven practice describes a technique for completing a VCB backup for large disks.

Intended Audience

Storage Team, Operations Team

Outline

Link to process and script

Author

Jamie Morrison

Resources

viops.vmware.com/home/docs/DOC-1587.

Disclaimer

You use this proven practice at your discretion. VMware and the author do not guarantee any results from the use of this proven practice. This proven practice is provided on an as-is basis and is for demonstration purposes only.

Creating a file or fullVM VCB backup on a disk by disk basis

Typically a full VM based backup of C: is required for most virtual machines for bare metal recovery. Large data disks may be backed up using other methods such as specific agents (e.g. Exchange, SQL) and can be marked as independent, so as not to be included in the snapshot for the fullVM based backup.

The issue occurs with file servers that may have data disks of hundreds of gigabytes or terabytes that are ideal candidates for a VCB file based backup, but cannot run a full VM based backup due to the size of the data disk, and due to the data disk not being able to be marked as independent, otherwise the file based backup is not possible.

Creating a file or fullVM VCB backup on a disk by disk basis
http://theether.net/kb/100131

Inspired by:

http://communities.vmware.com/blogs/jturver/2008/01/24/vcb-how-to-backup-a-selec ted-specific-disk-or-disks-using-vcbexport-and-a-useful-script-to-do-it

Proven Practice: Enabling SSL Communication between VMware® vCenter Site Recovery Manager and NetApp® FAS Storage Arrays

chogan — Fri, 23 Oct 2009 10:58:20 GMT

Introduction

The attached document contains the steps involved in setting up SSL communication between NetApp storage arrays & VMware vCenter Site Recovery Manager.

Outline

VMware vCenter Site Recovery Manager 4.0 is a disater recovery product which uses array replication technologies to failover from one site to another.

This document focuses on securing the communication between Site Recovery Manager & NetApp FAS arrays by configuring SSL on both the array and on NetApp's Storage Replication Adapter (SRA).

Author:

Cormac Hogan

Global Support Services (GSS)

VMware

Resources:

Disclaimer:

Steps to setup EMC Clariions for VMware Site Recovery Manager

chogan — Mon, 01 Dec 2008 15:38:51 GMT

Introduction

The attached document contains the steps involved in setting up the EMC Clariion storage arrays for use with VMware Site Recovery Manager.

Outline

Site Recovery Manager is a VMware disater recovery product which uses array replication technologies to failover from one site to another.

This particular document looks at one particular vendor (EMC) and one particular array model (Clariion).

The document will take you through the replication setup steps (Mirrorview) and the snapshot setup steps (Snapview).

Author:

Cormac Hogan

Product Support Engineer

VMware

Resources:

Disclaimer:

How to create a proven practice document

schambers — Sun, 07 Sep 2008 17:19:55 GMT

Here's the lightweight process

1. Find the community that fits your practice (don't worry if you get it wrong, the community folks will help find the right home)

2. Create a document

3. Then select "Write a new document"

4. Put your content in, make it look like the template below (click on example to enlarge). There is a template at the bottom of this doc that you can copy & paste with to save you writing this out

5. After you've written the document, you can do a number of things:

Attach a document - this can be instead of writing out content in the main doc (but always add the headers above).
ALWAYS add Tags. The minimum is "proven_practice", but check out some of the others to get an idea. Product names, job roles, company names, busines verticals - these are all good tags.
If you are going to Submit for Approval straight away, then leave "Users who may edit:" set as "Anyone" - this is a collaboration site - and click "Submit for Approval"
If you want to keep this as a draft and work with someone on this prior to publishing, then in "Users who may edit" select the other VIOPS user(s) - and click "Save as Draft"
Always leave Comments open.

6. Wait for the approver to get in touch about adding more content

The template for copying & pasting

Paste the following into your document.

Introduction

explain why this proven practice came about, what problem does it solve?

Intended Audience

what kind of organization would this suit? - company size, business vertical, size of virtual infrastructure- which job roles will be interested in this - a VCP? A CCNA? An IT Manager? A Change Manager? Head of Operations?

Outline

briefly list the steps in the practice, in number order

Author

company logo + bio- author(s) name, email, bio

Resources

link to this document as a minimum- other links to white papers, KB articles, case studies, VMTN etc.

Disclaimer

Title of proven practice goes here

...and the unambiguous, prescriptive and actionable text goes here