• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Veeam

S

Sturm

n00b
Joined
Jul 23, 2013
Messages
29
Hello

I'm just starting to trial Veeam Backup & Replication.
On friday, I created my first backup of a testserver. (running in a VMware ESXi environment), now the following error occurred: veeam starts, read tries to start, the backup but then unfortunately crashes my whole ESXi server.
All servers on ESXi are Windows Server 2012 R2, I already patched Veeam to the latest version which supports Windows Server 2012
Anyways, if Veeam is able to crash your whole server (in production), it really is a disaster.

Reading all the good comments about Veeam it really confuses me that it keeps crashing my server, so I hope that one of you can help me out.

If you want some additional information, you can just leave a reply asking for it.
Also guys, towards the ones withe experience with Veeam, what are the limitations of this product? I've done some research but I want to have some advice from practical side.

PS: I'm beginning to develop an aversion towards Veeam.

thanks in advance!
Sturm
 
Last edited:
What is your current setup layout like? (VM count, using hardware pass through, etc.)
Where/What is the source and destination of the backup?
What does the Windows Event Viewer say?
What do your ESXi logs say?
Does the same issue occur in Server 2008/2008 R2?
 
I'd just put in a ticket and see what comes of it, you can put in tickets even as trial user. Make sure that you are running ESXi on supported hardware though otherwise don't put in the ticket.
 
@peanuthead

My current setup is like:
6VM's
1 - Domain controller
1 - Fileserver
1 - ExchangeServer
1 - TerminalServer
1 - VCenter Server
1 - "Backup"server, from which I start the backups, and run Veeam

The destination of the Back ups are at this point, just some storage on the "Backup server". So NO SAN's or such...
About the ESXi, I get a purple debugging screen with some errors: MAIN error: "exception 14 in world"

Unfortunately, I didn't test it on windows Server 2008 because I want to make sure that Veeam can back up Windows Server 2012 R2, but I'll try it tomorrow, to backup a 2008.
 
I'm not sure if R2 is supported just yet (haven't looked either). What is you try '12 R1?
 
Where is Veeam installed, is it on a physical machine or a VM? What version of Veeam do you have installed? Is your repository ok, you do know you have to create one? I have Veeam deployed at many clients and have never heard of it crashing an Exsi host, but theres always a first time I guess. What version of Exsi are you running?
 
Post copies of the following from the esxi host.
hostd.log
vmkernel.log
vmkwarning.log
vobd.log
And the vpxa.log from vcenter all from just after a crash please.
We'll find an answer If you can snag them.

Follow this link for instructions on grabbing them
http://kb.vmware.com/kb/2032076
 
peanuthead said:
I'm not sure if R2 is supported just yet (haven't looked either). What is you try '12 R1?
Click to expand...


I do think that R2 is supported in the latest patch. I even managed to make a back up on friday of a server 2012 R2 so...
 
Veeam is also installed on a VM, and I do have created a backup repo. It's just a drive on the same server where Veeam is installed, but another partition. veeam is installed on the C drive, and I create backups on the F drive.
 
Hello guys, I'm here with a last update. I managed to find the problem, but no solutions yet.
When I created a backup of a server who wasn't turned on, it worked like a charm, but when I tried to backup that same server (who was turned on now), Veeam again crashed my whole ESXi server. So it seems that Veeam has troubles when backing up a server which is turned on.
 
Veeam does not have troubles backing up a server that is powered on. If it did, they'd be out of business - the link to the PSOD image doesn't work, do you have another place to host it? It's giving a 403 unauthorized for the image itself.
 
I also need a full vm-support from the host. Sadly, the vmkernel file doesn't tell me enough (other than the fact you're doing some weird stuff).
 
lopoetve said:
I also need a full vm-support from the host. Sadly, the vmkernel file doesn't tell me enough (other than the fact you're doing some weird stuff).
Click to expand...

How do you mean I do weird stuff?
Today I had a remote session with a sysengineer from Veeam, but unfortunately she also didn't had a clue about the problem. The problem is now being processed by the Veeam support but I do keep a close eye on this forum.
 
Sturm said:
How do you mean I do weird stuff?
Today I had a remote session with a sysengineer from Veeam, but unfortunately she also didn't had a clue about the problem. The problem is now being processed by the Veeam support but I do keep a close eye on this forum.
Click to expand...

You have a huge pile of devices reporting IO beyond end of device, and unusual I/O errors, plus other invalid IOCTL calls. This tells me you're probably doing something unusual with storage and possibly interrupts in some form, even though I can't tell for certain as the logs don't contain the device discovery or information.

The PSOD looks like a TLB issue - what's your processor? Snag the latest bios for your board as well (what motherboard is it)?

run a vm-support from the command line, and upload the resulting tarball :)
 
Per the screenshot it looks like you're running 5.5, 5.5 U1 is out, if all else fails you can try the update, they fixed quite a bit of bugs with the new release.
 
My lab has two 5.1 (U1?) hosts. Do you think it's worth upgrading to 5.1 U1?
 
Last edited:
Sigh. I can't type! What I meant to write was: is it worth upgrading to 5.5 U1 (from 5.1 U1) I know 5.5 sucked for a lot of folks - more wondering if going from latest & greatest 5.1 to 5.5 is worth it...
 
Ah, i misread. I wouldn't count on gaining stability from the 5.1 U1 to 5.5 U1 upgrade. Just features.
 
Are you purposely not answering what hardware you're using because half of it isn't on the HCL or are you going to post up all your hardware and storage specs?
 
I'm sorry for not answering asap, I'm living in Belgium and the timezones are different. I'm currently not at my workplace and I can't update you guys on the hardware specs. This will be for tomorrow. What I can say is that I use a trial version of ESXi and I use a HP Proliant Server to host my VM's. I installed the ESXi with special HP tools because I already noticed some problem without those tools.

What I've also done is cloned the VM's by copying the .vmx & .nvram on the datastore and then add the copied VM to the inventory.
 
So your connecting direct to hosts, your not using veeam through a vcenter server? On a trial version of esxi?

Also on hardware that we are not sure if its on the VMware HCL.

What proliant server are you running?
 
and you copied vmx/nvram files, not the disks, and are wondering why things are acting strange?

You need to clone the VM. Not copy a couple parts of it.
 
lopoetve said:
and you copied vmx/nvram files, not the disks, and are wondering why things are acting strange?

You need to clone the VM. Not copy a couple parts of it.
Click to expand...

Need vCenter for cloning, I would advise OP stes up vcenter and uses it for cloning and the connection point for veeam.
 
k1pp3r said:
Need vCenter for cloning, I would advise OP stes up vcenter and uses it for cloning and the connection point for veeam.
Click to expand...

he says he has it in forth post. If he using it though is another question...
 
Here are my hardware specs, if you guys need some additional information please just ask

Storage: HP smart array P6000
ServerModel: Proliant ML370 G5
Processor: INTEL Xeon X5450 @ 3GHz
Network adapter: INTEL 82574L Gigabit Network Conenction
RAM: 32GB total - 4GB (for 1 Virtual Machine)
BIOS: PhoenixBIOS 4.0 Realease 6.0: INTEL - 6040000, 6.00
 
Sturm said:
Hello guys, I've cloned VM's before I've set up a vcenter server, to clone a vm I just followed this tutorial: http://nchrissos.wordpress.com/2013/04/22/cloning-a-vm-without-vcenter-in-esxi-5-1-free-edition/

I do have to say that I skipped the sysprep part.
Click to expand...

Now that you have vCenter setup, I'd go back and recreate your machines that you "cloned" using this method, especially if didn't sysprep any of them. Having duplicate SIDs in the same domain which may be running as the domain controller and exchange server isn't helping things.
 
hello

I'm here with another update.
I was thinking the same way as the previous post, that I made a mistake NOT doing the sysprep part, so I created a new VM from scratch, and installed Veeam on that. Now I tried to backup a server and it worked like a charm.

Now my thread isn't closed yet, has anyone got an understandable explanation for my error or can anyone tell me WHY Veeam acted so weird? I'm just a beginning sysengineer and want to get as much information as possible.

btw, I'm sorry for my grammatical mistakes guys ;)
 
When you say you installed veeam on it, can you explain further?

Veeam is a clientless backup and doesn't require an install on a server that is backed up.
 
k1pp3r said:
When you say you installed veeam on it, can you explain further?

Veeam is a clientless backup and doesn't require an install on a server that is backed up.
Click to expand...

Well I simply installed Veeam on a VM, and backed up another VM (server) with the program. Is it clear now or ?
 
You must log in or register to reply here.
Back
Top