Vault 2015 restore, products not supported error

[Anonymous]

Hi everyone, I was trying to set up a test Vault and am running into a problem loading my restore, i am getting a "Restore failed because the backup has products that are not supported by the server". I have looked through my back up folder which is very easy as I only have a few files in there and I am not seeing anything out of place. So I had 2015 Vault Server set up with 2 vaults inside, I have not rolled it our to my design team yet (currently in a un-vaulted environment) and was only using it as a testing ground. I created a backup this morning and then restored it successfully. Please with how it was going I decided to make the jump to 2016 before I roll it out to everyone. I uninstalled vault 2015 and sql express 2008 and begin installing vault 2016 which automatically installed sql 2016. 2016 was unable to restore my back up to do a "file store" error that I could not fix. I uninstalled them and reinstalled 2015 leaving sql 2012. when I tried to restore it then it first gave me the error. Realizing i had made the back up on sql 2008 i prompted uninstalled 2012 and reinstalled 2008. I still got the error when trying to restore my vault, so I started digging. I went through my back up and found some "filestoreinfo.fsg" in my two vaults that had a more recent time stamp than my back up files so i removed those from the folder thinking they were created by either vault 2016 or sql 2012 and didn't belong. It did nothing and I still cannot restore my backup. Anyone have any ideas on how to fix this cluster?

[Anonymous]

I forgot to mention I also have tape drive back ups from yesterday that I could use... but I don't know which files I would need to resurrect.

[minkd]

A snippet from the ADMS-Console log would help identify the specific cause, but my best guess is that you made the backup from a higher tier of vault (i.e. Vault Workgroup or Vault Pro) and are trying to restore to a lower tier server (ie: Vault Basic). If that is the case you will need to restore a server that is the same tier or a higher tier.  You can migrate from Vault Basic to Vault Pro, but not the other way.

-Dave

[paul.gunn]

Hi,

Usually this error (products not supported ) means that you are trying to install a backup from a higher product edition. e.g. you have Vault basic installed but are trying to restore a backup from Vault workgroup or professional. Possibly you installed the wrong edition of Vault server in your test environment?

Paul

[Anonymous]

Thanks for the responses guys, sadly it is not a product level issue. I only have vault basic currently for both 2015 and 2016. I have been waiting to purchase and implement workgroups until after I had this set up and could do training on vault with my designers. Attached is a snipped image of the console log from a restore I tried this morning.

[Anonymous]

looks like I can't attache the snipped image to any of my posts... so here it is. 6/8/2015 7:30:00 AM ==== DataManagement.Common.Logging: DISABLED ==== 6/8/2015 7:30:00 AM ==== Logging initiated: Core server version 19.0.49.0 ==== 6/8/2015 7:30:00 AM Connectivity.Request.Common.RequestLibrary - RequestRuntimeStart() 6/8/2015 7:30:00 AM Connectivity.Request.Vault.RequestLibrary - RequestRuntimeStart() 6/8/2015 7:30:00 AM Connectivity.Request.Foundation.RequestLibrary - RequestRuntimeStart() 6/8/2015 7:30:00 AM Connectivity.Request.Document.RequestLibrary - RequestRuntimeStart() 6/8/2015 7:30:05 AM Checking if a migration is necessary. 6/8/2015 7:30:11 AM All vaults and libraries have already been migrated. 6/8/2015 7:30:21 AM Restore operation will delete current datasets and file stores. Would you like to restore now? Choosing 'No' will stop this operation. 6/8/2015 7:30:28 AM ================================================================== 6/8/2015 7:30:28 AM RESTORE PROGRESS: The server console is currently in the process of restoring a backup set. Please wait... 6/8/2015 7:30:28 AM ================================================================== 6/8/2015 7:30:29 AM Restore failed because the backup has products that are not supported by the server. 6/8/2015 7:30:29 AM Connectivity.Application.VaultManager.ServiceException: RestoringUnsupportedProducts [223] ---> Connectivity.Core.Exceptions.CoreException: RestoringUnsupportedProducts [223] Server stack trace: at Connectivity.Core.Operations.BackupSource..ctor(String backuppath) at Connectivity.Core.Services.KnowledgeMasterService.RestoreWithBackup(String restorePath, String toFSLocation, String toDBDataLocation, String toDBLogLocation, OnProgressDelegate onProgress) at System.Runtime.Remoting.Messaging.Message.Dispatch(Object target) at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg) Exception rethrown at [0]: at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at Connectivity.Core.Services.KnowledgeMasterService.RestoreWithBackup(String restorePath, String toFSLocation, String toDBDataLocation, String toDBLogLocation, OnProgressDelegate onProgress) at Connectivity.Application.VaultManager.KnowledgeMasterService.RestoreWithBackup(String restorePath, String toFSLocation, String toDBDataLocation, String toDBLogLocation, String user, String pass, OnProgressDelegate onProgress) --- End of inner exception stack trace --- at Connectivity.Application.VaultManager.ProgressCommand.Execute() at Connectivity.Application.VaultManager.RestoreVaultCommand.DoRestore(String restorePath, Boolean isRestoreDirectory, LoginInfo dbLogin, String toFSLocation, String toDBLocation)

[Anonymous]

So I have decided to just scrap the vaults I had made in 2015 and will just start over in 2016. Since it was a test vault anyway I will have no real data loss, but I need to restore a custom content center library I created. It is currently a dbbak file(from my backup files), any idea how to convert/migrate that?

[minkd]

If you still have the system from where the backup was made, the easiest (and preferred) thing to do would be:

1) On original system, use the ADMS-Console to export the content center library (a mdf & a ldf file are exported).

2) On new system, use the ADMS-Console to import the content center library.

If the original system is not available, then you will need SQL Studio:

1) Restore the dbbak file to SQL using SQL Studio.

2) Detach the the resulting library (mdf & ldf file) using SQL Studio.

3) Import the mdf/ldf for the library using ADMS-Console.

This procedure will work for content center library databases, but not with Vault databases.

-Dave

[Anonymous]

Thank you for your response, I was able to restore my "original" back up file finally! I had to remove some files that were added to folders, and edited the XML file to remove all of the other libraries except for my custom one. Then went back through my file store folders and found an .ipt and .ipj file that had very long file names, unlike all of my other files. I suspected that was possibly a change with 2012 sql or 2016 vault so I deleted the files. Then the restore worked. I am not sure which one of the changes I made fixed it, but it restored all my settings, user accounts, both vaults, and my library. Interestingly though the 1 assembly, made up of 3 parts would check out and load just fine, but when I would try to check it back in it would crash everytime. I am not so concerned about that as I have not been able to recreate the error with newly generated parts/assemblies. Thanks again for your help!

[minkd]

Based on what you have described, you are probably in an unsupported state; so even though some things may appear to work now, you may find down the road that obscure errors occur that no-one will be able to solve.

Therefore, I think it would be in your best interest to make things right while you still can.  You mentioned there was only test data in the vault (so that it could be thrown away).  With that in mind I would do the following (all in ADMS-Console):

1) Detach the content libraries you want to keep.

2) Delete any vaults.

3) Delete the knowledge vault master.

4) Create a new knowledge vault master.

5) Create a new vault.

6) Attach the library(s) detached in step 1.

This will make sure future backups do not think other products are involved, and that the database schema and configuration are correct for use with Vault Basic.

-Dave

[Anonymous]

Thank you Dave. Since I will be going to a workgroup level vault in the next few weeks would you still recommend your course of action?

[minkd · Accepted solution]

Unless I'm misunderstanding the steps you went through to migrate, you probably have a more damaged vault than you think.  If the data in it is just test data so the value of trying to preserve it is low, then I would start as clean as possible for production.

If your vault has any residual Vault Workgroup schema or settings already, then it could fail to upgrade ... if you're lucky.  Worse case it could appear to work fine and you don't discover the damage until you start using some feature months later.  Fixing the damage at that point will likely be costly, if it can be done at all.

The content libraries should be unaffected by vault product tier so no worries there.

And once you have the new setup I recommend making a backup, and making sure it can restore without any issues.  You should never have to modify any files in the backup to get it to restore.

-Dave

[Anonymous]

I ended up starting over, I was able to recover my custom library via my damaged back up restore and then copied and saved those flibrary iles, in multiple locations, just in case. Then uninstalled Vault all together and started over. I have backed up the vault and successfully restored from it and will be rolling it out to my designers to learn this week. Thank you for your help.

I did have to migrate the 2015 library over to 2016 which was more cumbersome than it really should be, but I made it through that. It does seem silly that I have to use Vault and Inventor to migrate something, oh well.