Exchange Server 2007 - Unable to connect to MKS error connecting to /bin

[habibalby]

Hi Guys,

I'm having problem in getting this resolved. The issue started by Veeam is not removing the snapshots successfully and freezes the VM for a long time till the snapshot removed. Then I have started having Backup Exec agent to backup the Exchange and that was damn slow from 3000 mb/m dropped to 140 and less MB/m which is ridicules.

Today I'm having a Shutdown window of 2 hours and first started by stopping exchange services and then I have taken manual snapshot of the VM to delete All the old snapshot and this almost 1 hour and 15 minutes and the progress still 36%.

While Snaphsot is going on the entire VM is freeze and ping to the VM is almost Request Timed Out and very high latency.

eply from 192.168.10.91: bytes=32 time=136ms TTL=127

eply from 192.168.10.91 bytes=32 time=2671ms TTL=127

eply from 192.168.10.91: bytes=32 time=8ms TTL=127

eply from 192.168.10.91: bytes=32 time=198ms TTL=127

eply from 192.168.10.91: bytes=32 time=588ms TTL=127

eply from 192.168.10.91: bytes=32 time=274ms TTL=127

eply from 192.168.10.91: bytes=32 time=137ms TTL=127

eply from 192.168.10.91: bytes=32 time=1493ms TTL=127

eply from 192.168.10.91: bytes=32 time=1524ms TTL=127

eply from 192.168.10.91: bytes=32 time=1589ms TTL=127

eply from 192.168.10.91: bytes=32 time<1ms TTL=127

eply from 192.168.10.91: bytes=32 time=388ms TTL=127

eply from 192.168.10.91: bytes=32 time=330ms TTL=127

eply from 192.168.10.91: bytes=32 time=243ms TTL=127

eply from 192.168.10.91: bytes=32 time=1326ms TTL=127

eply from 192.168.10.91: bytes=32 time=720ms TTL=127

equest timed out.

eply from 192.168.10.91: bytes=32 time=272ms TTL=127

eply from 192.168.10.91: bytes=32 time=2992ms TTL=127

eply from 192.168.10.91: bytes=32 time=5ms TTL=127

Based on the error I got in the VM console the solution is to re-create a VM and re-attach the VMDK disks to it, but as you know this is Exchange and doing this work is tedious, i'm thinking of if its possible to V2V the VM using vConverter will it sort the issue?

Thanks,

[habibalby]

Hi All,

I believe the second approach to this issue is to;

1. Build new VM.
2. Install Exchange 2007 Enterprise
3. Assign new Disks and create new DBs.
4. Move mailboxes

[Lenora_BE]

Hi,

Exclude any antivirus scans from the Backup Exec processes on the Media Server and Exchange server. Make sure your Exchange Management tools install on the Media Server is updated to the same version as the install on the Exchange server.

[Anjani_Kumar]

Well i believe you should go for V2V . IT will take less time than the second way you described.. But should make sure the vm is shut down. The ETA will be depend on the speed and the size of your vm.

All the best,

Please consider marking this answer "correct" or "helpful" if you found it useful.

Anjani Kumar

VMware vExpert 2014 .  Infrastructure Specialist.

Email ID : Anjani.kumar@vmwareminds.com

Website :   http://www.Vmwareminds.com

[habibalby]

Hi,

Thanks guys for your reply, actually all the Exchange Directories and the Backup Exec Directory are excluded from AV. Also on the Media server Backup Exec is excluded too.

I made progress last night by;

1. Repair the media agent on the Exchange Server
2. Reboot ESX host
3. Reboot Exchange
4. Migrated exchange to the Rebooted ESX Host
5. Rebooted the Media Server "Backup Exec"
6. Configured new job against exchange to copy single 2 GB file, it was fast.
7. Ran Incremental exchange started at 298MB/M and dropped to 64MB/M
8. Configured new job as full backup to Disk instead of Tape against specific Storage Group, backup ran at around 5,298 MB/m and dropped to 3,670MB/m
9. I will run the job again to Backup to Tape and hope to see good result.

Thanks guys for your contribution.