vDR Restore Failed
Hi
Restore of my Exchange failed, using VDR.
Restore was of 3 disks - OS, Mailbox, Logs.
I only really needed to do Mailbox and Logs, OS was otherwise OK, but in my haste I ticked the whole lot.
Error log:
5/14/2011 11:34:05 PM: Restore using Saints Exchange
5/14/2011 11:34:05 PM: To volume Saints Exchange...
5/14/2011 11:34:05 PM: Restoring from /SCSI-0:1/, Session (5/14/2011 12:14:11 AM)
5/15/2011 12:56:11 AM: Performing full restore of disk "[Exchange Logs] Saints Exchange/Saints Exchange_1-flat.vmdk" using "Network"
5/15/2011 8:48:02 AM: File "Saints-MGMT.Saints.local/
5/15/2011 2:58:52 PM: Performing full restore of disk "[Exchange MB] Saints Exchange/Saints Exchange_1-flat.vmdk" using "Network"
5/15/2011 2:58:53 PM: 1 task errors
5/15/2011 2:58:53 PM: Completed: 8 files, 422.7 GB
5/15/2011 2:58:53 PM: Performance: 468.0 MB/minute
5/15/2011 2:58:53 PM: Duration: 15:24:39 (00:00:08 idle/loading/preparing)
And
5/15/2011 2:58:54 PM: Restore using Saints Exchange copy
5/15/2011 2:58:54 PM: To volume Saints Exchange...
5/15/2011 2:58:54 PM: Restoring from /SCSI-0:1/, Session (5/14/2011 12:14:11 AM)
5/15/2011 2:59:00 PM: Can't initialize destination, error -3941 ( create snapshot failed)
5/15/2011 2:59:00 PM: Task incomplete
Looking at the logs it seems the Logs disk restored successfully.
Looking at the logs it seems the Mailbox disk restored successfully.
THe OS disk failed due to insufficient space.
The VM wont start due to insufficient space. I have created a new Datastore with a larger allocation of space and I am now transferring the OS disk to the new Datastore.
Mailbox Datastore looks around the right size...Im hoping this works.
in the OS VMX file it says the disk in use is filename.vmdk. In the Datastore there are filename_1.vmdk and filename_2.vmdk also, both not quite as big as the filename.vmdk.
What are these? Why have I run out of space?
Does the restore -add- files to the Datastore as opposed to overwriting that is currently there?
Restore of my Exchange failed, using VDR.
Restore was of 3 disks - OS, Mailbox, Logs.
I only really needed to do Mailbox and Logs, OS was otherwise OK, but in my haste I ticked the whole lot.
Error log:
5/14/2011 11:34:05 PM: Restore using Saints Exchange
5/14/2011 11:34:05 PM: To volume Saints Exchange...
5/14/2011 11:34:05 PM: Restoring from /SCSI-0:1/, Session (5/14/2011 12:14:11 AM)
5/15/2011 12:56:11 AM: Performing full restore of disk "[Exchange Logs] Saints Exchange/Saints Exchange_1-flat.vmdk" using "Network"
5/15/2011 8:48:02 AM: File "Saints-MGMT.Saints.local/
5/15/2011 2:58:52 PM: Performing full restore of disk "[Exchange MB] Saints Exchange/Saints Exchange_1-flat.vmdk" using "Network"
5/15/2011 2:58:53 PM: 1 task errors
5/15/2011 2:58:53 PM: Completed: 8 files, 422.7 GB
5/15/2011 2:58:53 PM: Performance: 468.0 MB/minute
5/15/2011 2:58:53 PM: Duration: 15:24:39 (00:00:08 idle/loading/preparing)
And
5/15/2011 2:58:54 PM: Restore using Saints Exchange copy
5/15/2011 2:58:54 PM: To volume Saints Exchange...
5/15/2011 2:58:54 PM: Restoring from /SCSI-0:1/, Session (5/14/2011 12:14:11 AM)
5/15/2011 2:59:00 PM: Can't initialize destination, error -3941 ( create snapshot failed)
5/15/2011 2:59:00 PM: Task incomplete
Looking at the logs it seems the Logs disk restored successfully.
Looking at the logs it seems the Mailbox disk restored successfully.
THe OS disk failed due to insufficient space.
The VM wont start due to insufficient space. I have created a new Datastore with a larger allocation of space and I am now transferring the OS disk to the new Datastore.
Mailbox Datastore looks around the right size...Im hoping this works.
in the OS VMX file it says the disk in use is filename.vmdk. In the Datastore there are filename_1.vmdk and filename_2.vmdk also, both not quite as big as the filename.vmdk.
What are these? Why have I run out of space?
Does the restore -add- files to the Datastore as opposed to overwriting that is currently there?
change the names in vmx file
ASKER
Ok, that explains why its run out of space.
I have cancelled the migrate and I am now moving the filename_1.vmdk to local host datastore, which will free up about 12GB's.
I can then see if the VM will boot.
Yes?
I have cancelled the migrate and I am now moving the filename_1.vmdk to local host datastore, which will free up about 12GB's.
I can then see if the VM will boot.
Yes?
ASKER
The name is correct I think.
Are the filename_#.vmdk's snapshots?
Are the filename_#.vmdk's snapshots?
they could be separate disks
snapshots usually 000001.vmdk etc
snapshots usually 000001.vmdk etc
ASKER
I dont understand.
I have 3 disks asscoiated with this VM:
OS
Mailbox
Logs
Each disk is a seperate datastore.
In the OS Datatsore I have (amongst other files):
Filename.vmdk (85GB)
Filename_1.vmdk (12GB)
Filename_2.vmdk (53GB)
I am moving off Filename_1.vmdk to ESX local datastore.
Is this ok?
I have 3 disks asscoiated with this VM:
OS
Mailbox
Logs
Each disk is a seperate datastore.
In the OS Datatsore I have (amongst other files):
Filename.vmdk (85GB)
Filename_1.vmdk (12GB)
Filename_2.vmdk (53GB)
I am moving off Filename_1.vmdk to ESX local datastore.
Is this ok?
ASKER
I now have 11GB free on the OS datastore and the VM will still not power on due to insufficient disk space!!
WHat is going on
WHat is going on
okay thats okay then if you have three different virtual disks.
that would be okay.
then just readd the disk to vm settings if your doing this msnually.
that would be okay.
then just readd the disk to vm settings if your doing this msnually.
which disks were restored?
ASKER
I accidentally selected all 3 disks to restore.
Mailbox and Logs seem to be ok, but the OS disk failed due to insufficient space.
I moved off Filename_1.vmdk (freed up 11GB) and it still says insufficient space.
I created a new VM, added those disks, same thing.
I dont get all, all disks have free space!!
Mailbox and Logs seem to be ok, but the OS disk failed due to insufficient space.
I moved off Filename_1.vmdk (freed up 11GB) and it still says insufficient space.
I created a new VM, added those disks, same thing.
I dont get all, all disks have free space!!
you mentioned that the os disk was not restored due to insufficient disk space?
of exchange_1 was restored correctly
but exchange-flat has a write error, so this disk could be damaged?
of exchange_1 was restored correctly
but exchange-flat has a write error, so this disk could be damaged?
ASKER
Yes the disk ran out of space - I thought the restore would overwrite, not append.
Other 2 disks restored ok it seems (need to boot exchange to check!)
I see no exchange-flat.
Would it be best to try restoring the OS again, after making sure there is enough space?
Other 2 disks restored ok it seems (need to boot exchange to check!)
I see no exchange-flat.
Would it be best to try restoring the OS again, after making sure there is enough space?
okay so you deleted os and logs?
can you select the original os disk only in properties and see if u can start machine
sometimes a insufficient disk error could be many things
can you select the original os disk only in properties and see if u can start machine
sometimes a insufficient disk error could be many things
ASKER
No, originally I deleted Mailbox and Logs. OS was fine, but I chose by mistake to restore that too.
If I remove the Mailbox and Logs disk from the VM it still fails to boot.
If I remove the Mailbox and Logs disk from the VM it still fails to boot.
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER
Ok.
If I choose to restore the OS disk to another Datastore, I get the error:
The virtual disk at node "SCSI (0:0) Hard Disk 1" is currently configured to overwrite an exisitjng virtual disk on the destination.
An unused virtual disk node must first be selected before a different datastore can be selected.
If I choose to restore the OS disk to another Datastore, I get the error:
The virtual disk at node "SCSI (0:0) Hard Disk 1" is currently configured to overwrite an exisitjng virtual disk on the destination.
An unused virtual disk node must first be selected before a different datastore can be selected.
have you changed the destination target?
ASKER
That is the error I get when I am trying to select another destination to restore to
ASKER
Ah I wonder if this is becuase I am currently moving a file from the OS disk to another store...
ASKER
That was it,
Rsstoring to a different (new) datatstore now on the 15k sas array, I will then attach this to the VM and hope it boots.
Rsstoring to a different (new) datatstore now on the 15k sas array, I will then attach this to the VM and hope it boots.
Are you using the same Virtual Machine name?
Okay, so just restore the OS disk. Attach to a virtual machine, and see if it quickly starts to boot and then power off.
then add Logs and Mailbox virtual disks.
Power On.
then add Logs and Mailbox virtual disks.
Power On.
ASKER
Back to the old 100Mbps bottleneck now.
The OS disk size is 199GB, but with only about 80GB used - will it restore 199GB or 80GB?
The OS disk size is 199GB, but with only about 80GB used - will it restore 199GB or 80GB?
It will restore the VMDK that was on the original disk.
If that was 199GB, it will restore 199GB.
If that was 199GB, it will restore 199GB.
ASKER
Well I used Thin disks so only 80Gb or so was used, althought 199Gb was provisioned
There was an issue with vDR which on restore converted a thin disk to a thick, filling up the datastores, but I believe this has been now fixed in 1.2 and later.
What version of vDR are you using?
What version of vDR are you using?
ASKER
1.2.1
okay the latest.
ASKER
Well, just have to sit tight now and wait.
ASKER
Restore finsihed, still wouldnt boot.
However, I created another VM, identical hardware config, booted up and all disks are there.
But no network. Device Manager shows ! next to Ethernet Controller.
Just reinstalling VMWare tools..
However, I created another VM, identical hardware config, booted up and all disks are there.
But no network. Device Manager shows ! next to Ethernet Controller.
Just reinstalling VMWare tools..
ASKER
Well the old (original) Exchange VM thinks its still using the corrupted datastore/disk and still will not boot with the same error. Even afetr removing all the disks, in the summary it still says the old Datastore is connected,
If I manually try to remove the Datastore it tells me it cannot becuase the resource is in use.
I manually disconnected the datastore from the SAN end and now the old VM is greyed out as (inaccessible).
THe new VM will not install or uninstall VMWare Tools, the install just hangs.
So close, yet so far!
If I manually try to remove the Datastore it tells me it cannot becuase the resource is in use.
I manually disconnected the datastore from the SAN end and now the old VM is greyed out as (inaccessible).
THe new VM will not install or uninstall VMWare Tools, the install just hangs.
So close, yet so far!
can you start a VM with just the OS disk?
ASKER
The new VM Starts fine now.
Just no NIC and problems installing VMWare Tools.
Just no NIC and problems installing VMWare Tools.
okay, put tools on hold for the moment.
is tools already installed?
and are the disks okay, exchange look okay?
despite nic issue? we can see if we can work on this and get you up and running.
is tools already installed?
and are the disks okay, exchange look okay?
despite nic issue? we can see if we can work on this and get you up and running.
ASKER
Tools were already installed, but when I booted no NIC driver on guest OS.
Exchange files looks ok...but of course I cannot check properly becuase of no network to communicate with AD!
Exchange files looks ok...but of course I cannot check properly becuase of no network to communicate with AD!
okay, if you add a new nic does that work?
you can do this hot plug as well?
you can do this hot plug as well?
what nic type have you been using e1000, vmxnet3
ASKER
Doesnt work - tried online and offline adding NICs, both E1000 and VMXNET3
ASKER
I also did a setup.exe /c which forcefully removed VMWare Tools.
Install still just hangs on "Preparing to install"
Install still just hangs on "Preparing to install"
does plug and play start in the vm?
what is the device error in the device manager and what nic is currently in the vm?
what is the device error in the device manager and what nic is currently in the vm?
so we have no tools in the machine now?
no tools vmxnet3 will not work.
ASKER
When I add a NIC the OS does pick it up, but device manage shows the yellow ! next to Ethernet Controller like there is no driver.
No Tools now
No Tools now
ASKER
Just removed all NICs, rebooted, and try to install tools like this
okay is plug and play services started
ASKER
Can I install drivers manually?
http://downloadcenter.intel.com/detail_desc.aspx?agr=Y&DwnldID=18725
http://downloadcenter.intel.com/detail_desc.aspx?agr=Y&DwnldID=18725
there are drivers already for the e1000 in the os.
have you tried removing the nics from the vm, but leaving thr nic in the vm settings
also check plug and play services?
also check plug and play services?
ASKER
PnP service is started
ASKER
have you tried removing the nics from the vm, but leaving thr nic in the vm settings
Can you clarify please?
Can you clarify please?
in the virtual machine device manager in th os delete
ASKER
Ok I uninstalled the NIC from Device Manager
Now what?
Now what?
if you click refresh at the top of device manager, does it find a nic?
ASKER
Yes
it does find a nic by no drivers?
what is the error in device manager?
what is the error in device manager?
ASKER
Yes, finds nic but no drivers.
Error is the standard "no driver"
Error is the standard "no driver"
is the nic an intel e1000?
what nic is defined in the vm properties?
as we got no tools it must be e1000
what nic is defined in the vm properties?
as we got no tools it must be e1000
ASKER
The NIC in VM Settings is E1000
what is the driver specified in the vm settings?
ASKER
Its all E1000!
ok, you could try installing an intel driver manually, ive never had to, as it should pickup the driver in the machine.
ASKER
the only way I can get the file over is via ISO.
But when I mount the ISO nothing happens in guest OS.
Works fine on other VM's...
But when I mount the ISO nothing happens in guest OS.
Works fine on other VM's...
something is wrong in this vm, with plug and play, its not performing correctly.
you could attach the disk another vm, mount the iso, copy files to, detatch carefully, do not delete, and after bootup try the drivers.
you could attach the disk another vm, mount the iso, copy files to, detatch carefully, do not delete, and after bootup try the drivers.
ASKER
Whilst I was doing all this I just noticed the NIC popped up!
I set the IP and I can ping it.
Just rebooting to see if it sticks.
Hopefully this will be it.
I will be installing another Exchange VM from scratch after this and moving everything over though, as I am not convinced this VM is 100% working properly.
I set the IP and I can ping it.
Just rebooting to see if it sticks.
Hopefully this will be it.
I will be installing another Exchange VM from scratch after this and moving everything over though, as I am not convinced this VM is 100% working properly.
okay, another exchange server, quite straight forward, install in organization, move mailboxes, move publuc folders, let users all users connect and their profile will update to new one with the new server reference, change smtp connevtor, and then decomission as per microsoft docs.
ASKER
BINGO
Mail flow
I love you Hanccocka
Mail flow
I love you Hanccocka
Thanks, i'll expect a card on Valentines Day!
for what its worth get a full backup.
ASKER
Yes!!
it will append.
you can restore to different location or datastore, or use rehersal mode that restores to separate folder called vmname rehersal.