Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people, just like you, are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
Solved

Restored Windows 2003 server on VMWare ESX 4.1

Posted on 2010-11-22
5
831 Views
Last Modified: 2012-05-10
We just purchased a Dell Poweredge R415 server with two AMD Opteron 2.6 ghz procs, 16 gb of RAM, four 600 gb SAS 15K drives configured in a Raid 5 array using a Perc H700 controller.

We have Backup Exec System Recovery 2010 installed on eight of our Windows servers. We have SQL server 2008 R2 and GFI Mail Archiver installed on one of these Windows servers that is being backed up by BESR 2010. The server being backed up is running Windows 2003 32 bit standard. I configured a BESR virtual conversion job to restore the Windows 2003 server using the latest recovery point directly to the ESX server. Once this completed, I created a virtual machine using the vmdks that BESR creates on the ESX server.

The problem is that I can't get all of the GFI MailArchiver services to start and/or stay running on this VM. When logging into Windows on the VM I get a number of SVCAttendant errors. All of the SQL Server and GFI MailArchiver services are configured to start automatically but only some of them will actually be started. Starting one or more of the services that didn't start may cause one of the other services which did start automatically to fail. I started off allocating 1 gb of RAM and 1 CPU to the VM. I tried increasing this to 4 gb of RAM and as many as 6 CPUs. Increasing the number of CPUs allocated to the VM seemed to help the most but the services still aren't super stable. I even tried reserving a certain amount of CPU and RAM for the VM. Also I installed VMWare tools on the VM.

Then I tried installing Windows 2003 64 bit standard server and VMWare Server 2.0.2 onto this same Dell PE R415 server and then recovering the Windows 2003 32 bit standard server using vmdks that BESR 2010 creates (with a virtual conversion job). Within VMWare server 2.0 I allocated 2 CPUs but I can't remember how much memory I allocated to it - I'm pretty sure it wasn't more than 4 gb. The restored Windows 2003 standard server running SQL Server 2008 and GFI MailArchiver worked fine on the Dell PE R415 running VMWare server 2.0.2.

I have reinstalled ESX 4.1 onto the Dell PE R415 server and tried recovering the Windows 2003 32 bit standard server (running SQL Server 2008 and GFI MailArchiver) in a VM one more time with the same result.

Does anyone have any ideas or suggestions?

0
Comment
Question by:Cleartrack
5 Comments
 
LVL 8

Expert Comment

by:jimmyray7
ID: 34193278
Initially, set the number of processors and memory to match the physical server.  Changing the number of processors can have a variety of negative side affects.  

Try to match the hardware on the virtual machine as closely as possible to the physical.  

This guide, although a few versions old, might help with configuring hardware after booting the VM - http://download3.vmware.com/vmworld/2006/tac9886.pdf
0
 
LVL 28

Expert Comment

by:bgoering
ID: 34193503
There are a number of things that can cause issues with a P2V of a server. Such as if the original disk drive was mirrored, or used some kind of raid controller. If there are vendor drivers or management agents configured. Take a look at http://www.experts-exchange.com/Software/VMWare/A_3639-VMware-vConverter-P2V-for-Windows-Servers.html. The article focuses on using VMware Converter rather than BESR to do the conversion - but all of the pre and post tasks should be the same.

Good Luck
0
 
LVL 42

Expert Comment

by:paulsolov
ID: 34276365
I would avoid using Symantec to converter to VMDK files.  

1. Use vmware converter and point to the SV2I (BESR index file)..it knows it natively
2. If this is in a test environment ensure that you are on a non routable vswitch to avoid ip/server conflicts
3. Provide a domain controller in the same test environment
4. Try to give similar cpu/memory specs to VMs
0
 

Accepted Solution

by:
Cleartrack earned 0 total points
ID: 34403506
I installed the latest patches (ESX410-201010001 & ESX410-201011001) available for VMWare ESX 4.1 and this virtual server is working fine now.  

Thanks for everyone's suggestions,

Mike
0
 

Author Closing Comment

by:Cleartrack
ID: 34426463
This solved the problem.
0

Featured Post

Netscaler Common Configuration How To guides

If you use NetScaler you will want to see these guides. The NetScaler How To Guides show administrators how to get NetScaler up and configured by providing instructions for common scenarios and some not so common ones.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
Why VM HD shows  2 different Datastore under storage? 3 64
cannot remove vmnic 7 30
Hypervisor 1 U 10 35
HP H221 HBA with P2000 trouble configuring 4 41
When rebooting a vCenters 6.0 and try to connect using vSphere Client we get this issue "Invalid URL: The hostname could not parsed." When we get this error we need to do some changes in the vCenter advanced settings to fix the issue.
This article outlines why you need to choose a backup solution that protects your entire environment – including your VMware ESXi and Microsoft Hyper-V virtualization hosts – not just your virtual machines.
Teach the user how to rename, unmount, delete and upgrade VMFS datastores. Open vSphere Web Client: Rename VMFS and NFS datastores: Upgrade VMFS-3 volume to VMFS-5: Unmount VMFS datastore: Delete a VMFS datastore:
Teach the user how to convert virtaul disk file formats and how to rename virtual machine files on datastores. Open vSphere Web Client: Review VM disk settings: Migrate VM to new datastore with a thick provisioned (lazy zeroed) disk format: Rename a…

840 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question