Job warnings after upgrade to v7

Hyper-V specific discussions

Job warnings after upgrade to v7

Veeam Logoby sho » Wed Aug 21, 2013 8:45 am

I thought I'd post about my experience and findings of upgrading our B&R v6.5 installation to v7.

Our setup is pretty basic as follows....

    Veeam running on a physical 2008R2 box backing up to local storage
    No separate backup proxy servers
    One backup job to backup all 24 VMs running on a 2008R2 Hyper-V cluster
    VMs are a mix of Svr 2008R2 and 2012

After upgrading B&R to v7 (very straight forward process) I found that I was getting the following warning on all of my 2012 VMs in the B&R backup job log...

Guest processing skipped (check guest OS VSS state and integration components version)

Looking in the Application Event Log on the affected VMs I see the following error...

Code: Select all
Log Name:      Application
Source:        vmicvss
Date:          20/08/2013 21:14:39
Event ID:      13
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      ****************.internal
Description:
Windows cannot perform an online backup of this system because scoped snapshots are enabled. To resolve this, disable scoped snapshots by creating the following registry value on this computer:
    PATH: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SystemRestore\
    DWORD: ScopeSnapshots
    Value: 0
 Incorrectly editing the registry may severely damage your system. Before making changes to the registry, you should back up any valued data on the computer.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="vmicvss" />
    <EventID Qualifiers="49154">13</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2013-08-20T20:14:39.000000000Z" />
    <EventRecordID>3860</EventRecordID>
    <Channel>Application</Channel>
    <Computer>TGS-SCVMM.tgs.internal</Computer>
    <Security />
  </System>
  <EventData>
  </EventData>
</Event>


Interesting to note that these errors also exist before I performed the v7 upgrade to B&R but no warnings were ever shown in v6.5.

I have today added the registry key given in the above error to one of my 2012 VMs and will see what change this brings when the backup job next runs.
sho
Novice
 
Posts: 6
Liked: never
Joined: Wed Mar 21, 2012 12:47 pm
Full Name: Stuart

Re: Job warnings after upgrade to v7

Veeam Logoby sho » Fri Aug 23, 2013 8:43 am

Well after applying the registry entry given above to a test 2012 guest VM, backup of this VM completed successfully. Therefore yesterday I applied the registry entry to all of my 2012 guest VMs and this morning Veeam is showing all backups as being successful.

Interesting to note that before applying these changes backup jobs would sometimes complete with warnings and other times complete with errors.
sho
Novice
 
Posts: 6
Liked: never
Joined: Wed Mar 21, 2012 12:47 pm
Full Name: Stuart

Re: Job warnings after upgrade to v7

Veeam Logoby foggy » Fri Aug 23, 2013 10:07 am

Stuart, thanks for sharing your observations, much appreciated. Looks like proper handling of such situations was implemented in v7, while previous versions did not include this logic and hence did not produce any warnings.
foggy
Veeam Software
 
Posts: 14742
Liked: 1079 times
Joined: Mon Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson

Re: Job warnings after upgrade to v7

Veeam Logoby pthmpson » Thu Sep 05, 2013 10:29 pm 2 people like this post

I got the same error message (check guest OS VSS state and integration components version) after upgrading to Veeam v7.
I just did what the error message said and upgraded the Integration Components on each of my Hyper-V VMs to v6.2.9200.16433 - all of my backups worked after that.

Phil
pthmpson
Lurker
 
Posts: 1
Liked: 2 times
Joined: Fri Aug 30, 2013 3:51 am
Full Name: Philip Thompson

[MERGED] Veeam and Exchange 2013 hyper-v VM

Veeam Logoby dockx » Wed Sep 18, 2013 7:05 am

Hi,

Another problem arose: trying to backup an Exchange 2013 VM but getting following error (while enable application-aware image processing is on). Hyper-V integration services is installed on the Hyper-V host.

Guest processing skipped (check guest OS VSS state and integration components version)
Unable to create snapshot (Microsoft Software Shadow Copy provider 1.0) (mode: Crash consistent). Details: Guest processing skipped (check guest OS VSS state and integration components version)
Error: Guest processing skipped (check guest OS VSS state and integration components version)

If I go into advanced settings and and turn on 'Disable application procession', then Veeam backups the VM, but the logs aren't truncated.

Do I need to install something on the Exchange virtual machine?

Any golden advice?

Kind regards,
D.
dockx
Novice
 
Posts: 9
Liked: never
Joined: Tue Aug 27, 2013 11:53 am

Re: Veeam and Exchange 2013 hyper-v VM

Veeam Logoby foggy » Wed Sep 18, 2013 7:22 am

Does the VM guest OS have dynamic disks by any chance?
foggy
Veeam Software
 
Posts: 14742
Liked: 1079 times
Joined: Mon Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson

Re: Veeam and Exchange 2013 hyper-v VM

Veeam Logoby dockx » Wed Sep 18, 2013 7:39 am

No, fixed .vhd.
dockx
Novice
 
Posts: 9
Liked: never
Joined: Tue Aug 27, 2013 11:53 am

Re: Veeam and Exchange 2013 hyper-v VM

Veeam Logoby foggy » Wed Sep 18, 2013 7:52 am

Do you have any related messages in the Windows Event Log? What are the OS versions of both Hyper-V host and guest VM?
foggy
Veeam Software
 
Posts: 14742
Liked: 1079 times
Joined: Mon Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson

Re: Veeam and Exchange 2013 hyper-v VM

Veeam Logoby dockx » Wed Sep 18, 2013 8:34 am

The VEEAM host is server 2012 and has the following in Event Viewer:
Error Session Backup Exchange has been completed.

Exchange (guest) is a server 2012 and has following in the Event Viewer:
Code: Select all
Windows cannot perform an online backup of this system because scoped snapshots are enabled. To resolve this, disable scoped snapshots by creating the following registry value on this computer:
    PATH: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SystemRestore\
    DWORD: ScopeSnapshots
    Value: 0
 Incorrectly editing the registry may severely damage your system. Before making changes to the registry, you should back up any valued data on the computer.


Hyper-V host is a 2008R2 Enterprise server and has no relevant events in the log...

Maybe it has something to do with those scoped snapshots?
dockx
Novice
 
Posts: 9
Liked: never
Joined: Tue Aug 27, 2013 11:53 am

Re: Veeam and Exchange 2013 hyper-v VM

Veeam Logoby v.Eremin » Wed Sep 18, 2013 8:39 am

According to our customers’ experience, applying registry key solves the issue, indeed. Thanks.
v.Eremin
Veeam Software
 
Posts: 13266
Liked: 968 times
Joined: Fri Oct 26, 2012 3:28 pm
Full Name: Vladimir Eremin

Re: Job warnings after upgrade to v7

Veeam Logoby dockx » Wed Sep 18, 2013 9:03 am

dockx
Novice
 
Posts: 9
Liked: never
Joined: Tue Aug 27, 2013 11:53 am

Re: Job warnings after upgrade to v7

Veeam Logoby foggy » Wed Sep 18, 2013 9:10 am

You're welcome. We're currently preparing the KB article for this issue.
foggy
Veeam Software
 
Posts: 14742
Liked: 1079 times
Joined: Mon Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson

Re: Job warnings after upgrade to v7

Veeam Logoby mathao » Fri Oct 04, 2013 7:02 am

When will the KB be available? We have the same issue with servers 2003's VMs since the upgrade.
Unable to create snapshot (Microsoft Software Shadow Copy provider 1.0) (mode: Crash consistent). Details: Guest processing skipped (check guest OS VSS state and integration components version)
mathao
Lurker
 
Posts: 1
Liked: never
Joined: Fri Oct 04, 2013 6:50 am

Re: Job warnings after upgrade to v7

Veeam Logoby Vitaliy S. » Fri Oct 04, 2013 11:17 am

Have you tried to apply the suggestions mentioned above?
Vitaliy S.
Veeam Software
 
Posts: 19558
Liked: 1102 times
Joined: Mon Mar 30, 2009 9:13 am
Full Name: Vitaliy Safarov

Re: Job warnings after upgrade to v7

Veeam Logoby Simonx182 » Wed Oct 23, 2013 7:05 am

I have the same problem on 1 VM of our Hyper-V 2008 R2 infrastructure.
The failing VM runs Server 2008 R2 and has Fileserver (DFS) and DHCP Role on it. All other vm's with 2008 R2 run properly.
Already tried to add the registry key to the failing guest VM, as mentioned before, no change. Do I have to reboot the guest VM after creating the registry key?

In the meantime I've configured that functional VSS processing is not required for this VM, so it creates at least a basic backup.
What else can I do to solve this problem ASAP? Open ticket with Veeam Support?

Regards Simon
Simonx182
Influencer
 
Posts: 13
Liked: 3 times
Joined: Thu May 31, 2012 4:01 am
Full Name: Simon Tauber

Next

Return to Microsoft Hyper-V



Who is online

Users browsing this forum: No registered users and 5 guests