Comprehensive data protection for all workloads
Post Reply
ross.fawcett
Lurker
Posts: 2
Liked: never
Joined: Mar 02, 2011 2:39 am
Full Name: Ross Fawcett
Contact:

SQL Error Upgrading 6.0 to 6.1

Post by ross.fawcett » Jun 11, 2012 6:36 am

Hey all,

Has anyone seen an error like this during a Veeam upgrade of 6.0 to 6.1

Image

Host OS: Server 2003 SP2 32bit
SQL Ver: 2005 Express SP4

ross.fawcett
Lurker
Posts: 2
Liked: never
Joined: Mar 02, 2011 2:39 am
Full Name: Ross Fawcett
Contact:

Re: SQL Error Upgrading 6.0 to 6.1

Post by ross.fawcett » Jun 11, 2012 7:43 am

Resolved.

Fixed by removing the entries from the dbo.VMssVMS table within the Veeam Database.

I believe these are related to a mounted data PowerNFS data store? No VM's were mounted but the data store was still active.

In either case, in future it would be nice if the installer checked these things if they are known gotchas, especially as once you have started the install you can't exactly launch the console to disable it.

Gostev
SVP, Product Management
Posts: 24826
Liked: 3579 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: SQL Error Upgrading 6.0 to 6.1

Post by Gostev » Jun 11, 2012 8:31 pm

No, active vPowerNFS datastore has nothing to deal with this issue. The dbo.VMssVMS table holds the list of active Instant VM Recovery processes, as long as there is some content in this table, the setup program will not be able to modify the table as required (see 2nd bullet under common upgrade issues in the sticky Known Issues topic). Thanks!

CaterhamKing
Novice
Posts: 6
Liked: never
Joined: Jun 27, 2011 9:55 am
Contact:

Re: SQL Error Upgrading 6.0 to 6.1

Post by CaterhamKing » Jul 02, 2012 4:23 am

Also saw this issue today. Seems that an Instant Recovery session did not clear down from the database, although it was no longer present according to the GUI. We checked this specifically before starting the upgrade. We could see the problematic row in the table, so backed up the DB and removed with :

delete from VmssVms;

Upgrade then went ahead as planned.

Post Reply

Who is online

Users browsing this forum: No registered users and 21 guests