vCenter recovery - using Veeam "NOT recommended"

VMware specific discussions

Re: vCenter recovery - using Veeam "NOT recommended"

Veeam Logoby albertwt » Tue Oct 18, 2016 5:16 am

rreed wrote:I didn't change anything about the VM. Same IP. A different vswitch but everything else unchanged. I haven't had time to go and fight w/ it any, I'll report back when I do.


Yes please, I'm interested to hear if the VCSA 6.0 is supported by Veeam 9.0 or not ?
--
/* Veeam software enthusiast user & supporter ! */
albertwt
Expert
 
Posts: 621
Liked: 20 times
Joined: Thu Nov 05, 2009 12:24 pm
Location: Sydney, NSW

Re: vCenter recovery - using Veeam "NOT recommended"

Veeam Logoby PTide » Tue Oct 18, 2016 7:04 am

Yes, it is supported. As foggy's already mentioned you can also use Veeam for VCSA 6.0 backups and restores, however one has to keep in mind that VCSA uses vPostgres database thus requires some additional steps to be performed in order to make a consistent backup.

Thank you.
PTide
Veeam Software
 
Posts: 3252
Liked: 273 times
Joined: Tue May 19, 2015 1:46 pm

Re: vCenter recovery - using Veeam "NOT recommended"

Veeam Logoby lando_uk » Tue Oct 18, 2016 11:53 am

Hi Foggy,
I'm sorry to keep going on but your VMware KB link says "The backup of the vPostgres database is not required when performing a backup using a supported method. "

So is a standard Veeam v9 backup a `supported method` or not?

Also VMware says "This article is only supported for backup and restore of the vPostgres database to the same vCenter Server Appliance. Use of image-based backup and restore is the only solution supported for performing a full, secondary appliance restore"

So this is saying that if you're restoring for DR, image based backup is the way to go.

You understand that we don't want to and shouldn't need to (according to VMware) run any post backup scripts or stop vcsa for a constant backup.

Thanks
lando_uk
Expert
 
Posts: 247
Liked: 18 times
Joined: Thu Oct 17, 2013 10:02 am
Location: UK
Full Name: Mark

Re: vCenter recovery - using Veeam "NOT recommended"

Veeam Logoby Pat490 » Tue Oct 18, 2016 11:57 am 1 person likes this post

vSphere 6.5 has just been announced at VMworld Europe with new backup capabilities!
https://blogs.vmware.com/vsphere/2016/1 ... e-6-5.html
Pat490
Expert
 
Posts: 140
Liked: 24 times
Joined: Tue Apr 28, 2015 7:18 am
Location: Germany
Full Name: Patrick

Re: vCenter recovery - using Veeam "NOT recommended"

Veeam Logoby PTide » Tue Oct 18, 2016 12:22 pm

So is a standard Veeam v9 backup a `supported method` or not?
According to VMware documentation it is supported only if the following requirements are met:

- it is full backup (no increments)
- VMware tools are installed
- VM uses FQDN with correct DNS resolution, or is with a static IP
- no snapshots
- no FT

All other cases are unsupported and might require extra steps to ensure backup consistency.

Also,
Thanks
PTide
Veeam Software
 
Posts: 3252
Liked: 273 times
Joined: Tue May 19, 2015 1:46 pm

Re: vCenter recovery - using Veeam "NOT recommended"

Veeam Logoby rreed » Tue Oct 18, 2016 1:22 pm

Veeam uses snapshots to do its backups, doesn't it?
VMware 6
Veeam B&R v9
Dell DR4100's
EMC DD2200's
EMC DD620's
Dell TL2000 via PE430 (SAS)
rreed
Expert
 
Posts: 354
Liked: 72 times
Joined: Tue Jun 30, 2015 6:06 pm

Re: vCenter recovery - using Veeam "NOT recommended"

Veeam Logoby Vitaliy S. » Tue Oct 18, 2016 1:56 pm

Yes, that's correct, but what Pavel tried to say "VMs that have existing snapshots", nothing to do with the way a backup job is done.
Vitaliy S.
Veeam Software
 
Posts: 19974
Liked: 1145 times
Joined: Mon Mar 30, 2009 9:13 am
Full Name: Vitaliy Safarov

Re: vCenter recovery - using Veeam "NOT recommended"

Veeam Logoby orangep7 » Mon Nov 07, 2016 9:24 am

Quick Update:

I ran into the same issue again this weekend when having to restore the same vCenter again (due to a failed in place upgrade). "Entire VM" restore kept failing and in order to recover the VM in the end I had to perform a "Restore VM files" job instead. New Case # 01969511 has been opened and support bundle has been Ftp'd.

Whilst troubleshooting the Restore failures I ruled out the following:

-Tried different transport modes on the Veeam Proxy
-Tried different credentials
-Tried different Veeam proxies, including a new Proxy
-Tried restoring to different hosts
-Made sure the Veeam proxy was on the same host that I was restoring vCenter to
-There were no orphaned HotAdd disks on the affected VM or any of the proxies.
-AutoMount was disabled in the Veeam VM Guest OS.
-Hardware versions were OK
-iSCSI controller had less than 15 disks attached
-The Veeam VM had been restarted in order to clear any possible locks
-The host was not a Standalone server
-Same cluster
-The VBKs were ‘full active’ and contained no snapshots

In order to have any confidence that vCenter is still fully protected I obviously need to understand why the latest Restores failed - so we'll see what Support come back with.
orangep7
Influencer
 
Posts: 18
Liked: 1 time
Joined: Tue Aug 26, 2014 10:10 am
Full Name: James Serjeant

Re: vCenter recovery - using Veeam "NOT recommended"

Veeam Logoby rreed » Mon Nov 07, 2016 5:52 pm

In further testing and closer scrutiny, ours (VC and PSC both) seem to restore fine to a test environment, albeit we have not yet tried to do a live restore to make sure it connects to hosts, talks on the network, etc. properly. We will find a later quiet time that we can power down our live VCSA's and do a live test.
VMware 6
Veeam B&R v9
Dell DR4100's
EMC DD2200's
EMC DD620's
Dell TL2000 via PE430 (SAS)
rreed
Expert
 
Posts: 354
Liked: 72 times
Joined: Tue Jun 30, 2015 6:06 pm

Re: vCenter recovery - using Veeam "NOT recommended"

Veeam Logoby tsightler » Mon Nov 07, 2016 9:32 pm 3 people like this post

Just want to say that I've restored probably 100+ vCenter servers over the past 5 years (a lot of these were for a handful of customers testing this specific DR scenario), in both test and production customer environments, and I've never had an issue with not being able to recover the vCenter assuming the backup was properly made (i.e. included the database).

I did have one very complex issue with vSphere 5.5 because the inventory database itself was outside of the SQL database. We had to stop the inventory service and use file level recovery to restore some older backups, but we were finally able to get the inventory database to start and run properly. This was important because, while it's completely possible to create a fresh inventory database, in vSphere 5.5 all of the tag information was stored there, and this customer made heavy use of tags. I'm pretty sure in vSphere 6 that tags information is now in the main vCenter database.

Regardless, restoring vCenter is a "special" event. While you can backup vCenter with Veeam using the vCenter connection, it is obviously impossible to restore using this method since, to restore vCenter you must power vCenter off, but it is obviously impossible to communicate with a powered off vCenter, so it creates a significant chicken-and-the-egg problem.

The solution is to determine which specific host the vCenter VM is currently registered against, temporarily add that host to the Veeam console via IP address as a standalone ESXi host, and then chose and advanced restore and restore either the VM disks or entire VM, mapping the resources to the standlone hosts. The reason you have to add the host by IP address, rather than by name, is because the Veeam console will not allow you to have the same host added twice, once via vCenter and again by direct host, so adding the host by IP address is a little bit of a trick.
tsightler
Veeam Software
 
Posts: 4874
Liked: 1821 times
Joined: Fri Jun 05, 2009 12:57 pm
Full Name: Tom Sightler

Re: vCenter recovery - using Veeam "NOT recommended"

Veeam Logoby albertwt » Thu Nov 10, 2016 10:12 am

foggy wrote:That confuses me, since vCSA is a Linux appliance and doesn't support VSS.


Does this means that the new VMware VCenter Standard Appliance version 6.0 and above backup is not supported by Veeam 9.0 yet ?
--
/* Veeam software enthusiast user & supporter ! */
albertwt
Expert
 
Posts: 621
Liked: 20 times
Joined: Thu Nov 05, 2009 12:24 pm
Location: Sydney, NSW

Re: vCenter recovery - using Veeam "NOT recommended"

Veeam Logoby foggy » Thu Nov 10, 2016 10:19 am 1 person likes this post

No, this means that you need to use pre-freeze/post-thaw scripts to get a consistent backup of Linux VMs (or go crash-consistent otherwise).
foggy
Veeam Software
 
Posts: 15303
Liked: 1133 times
Joined: Mon Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson

Re: vCenter recovery - using Veeam "NOT recommended"

Veeam Logoby albertwt » Thu Nov 10, 2016 10:25 am

Thanks Alex for the clarification, so where can I find the script for that pre-freeze/post-thaw scripts ?
Does this means that during the backup window, there might be some outage since the script kicks in :roll:
--
/* Veeam software enthusiast user & supporter ! */
albertwt
Expert
 
Posts: 621
Liked: 20 times
Joined: Thu Nov 05, 2009 12:24 pm
Location: Sydney, NSW

Re: vCenter recovery - using Veeam "NOT recommended"

Veeam Logoby foggy » Thu Nov 10, 2016 12:43 pm 1 person likes this post

albertwt wrote:Thanks Alex for the clarification, so where can I find the script for that pre-freeze/post-thaw scripts ?

Should be some generic script to prepare database for the backup.

albertwt wrote:Does this means that during the backup window, there might be some outage since the script kicks in :roll:

This implies a short period of time when the database is stopped.
foggy
Veeam Software
 
Posts: 15303
Liked: 1133 times
Joined: Mon Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson

Re: vCenter recovery - using Veeam "NOT recommended"

Veeam Logoby dellock6 » Fri Nov 11, 2016 10:05 pm

Actually, Postgres has continous log save, so any transaction is simply re-played upon restart if it is missing. This means that there is no real need to put the filesystem or the database in a consistent state. Per postgres documentation:

“We do not need a perfectly consistent file system backup as the starting point. Any internal inconsistency in the backup will be corrected by log replay (this is not significantly different from what happens during crash recovery). So we do not need a file system snapshot capability, just tar or a similar archiving tool.”
Luca Dell'Oca
EMEA Cloud Architect @ Veeam Software

@dellock6
http://www.virtualtothecore.com
vExpert 2011-2012-2013-2014-2015-2016
Veeam VMCE #1
dellock6
Veeam Software
 
Posts: 5138
Liked: 1381 times
Joined: Sun Jul 26, 2009 3:39 pm
Location: Varese, Italy
Full Name: Luca Dell'Oca

PreviousNext

Return to VMware vSphere



Who is online

Users browsing this forum: No registered users and 1 guest