8 Replies Latest reply on Jun 19, 2018 7:56 AM by Mac Readhead

    Managing 2 Vaults, PDM 2016 & 2018

    Mac Readhead

      Good Morning Forum:

       

      We have been using the same vault since ~2009 and it has some backend issues, so we are planning on creating an entirely new 2018 vault/Archive server/SQL backend. The current vault is 2016 and our SolidWorks installs are 2015/2016. I've got a few questions about migration of data and administration of 2 vault versions. Once the 2018 vault is running smoothly we plan on decommissioning the 2016, but for the transition period, I'd like to have a few things ironed out.

       

      1. Exporting some of the filecards/variables/Workflows to the new Vault. - Will there be an issue exporting a cex from 2016 and importing in 2018?
      2. Transferring current vault files to new vault. - Can we move them to a non-vault location, and then import into a new vault while maintaining metadata & references(assuming variable names are the same)?
      3. Can the 2018 Administration tool access and administrate a 2018 and 2016 vault?
      4. Will a desktop with the 2018 PDM client be able to access a vault running on a 2016 backend?

       

      I'm hoping that I will not have to upgrade the old vault to 2018 during this process, but I have a feeling that It might be required.

      **I should mention I know that SW2015 is not officially supported for a 2018 PDM client. It will be phased out as well.

        • Re: Managing 2 Vaults, PDM 2016 & 2018
          Michael Dekoning

          I'm almost positive you'll need to upgrade to 2018 before doing any of this. Clients and admin tool must be on the same version.

          Of possible you should upgrade your 2016 system to 2018 and move the server components. There is information on how to do this on the PDM installation guide.

          • Re: Managing 2 Vaults, PDM 2016 & 2018
            Martin Solem

            Hi,

             

            Throwing in some support for what Michael Dekoning is saying.

            • Exporting some of the filecards/variables/Workflows to the new Vault. - Will there be an issue exporting a cex from 2016 and importing in 2018?

            Probably not. I've done this on a few occasions and it has always worked when going from older to newer version. (Not always successful the other way around.)

             

            • Transferring current vault files to new vault. - Can we move them to a non-vault location, and then import into a new vault while maintaining metadata & references(assuming variable names are the same)?

            When you do this you can move directly from one vault to another, or you can use a temporary storage area. The important thing is to maintain the folder structure for all references. Also, when you are done, break the old reference path by uninstalling the old vault view or rename a top-level folder to "xxxx_old" or something similar, otherwise SOLIDWORKS is going to find those files and open them. Make sure you test this and understand what is going on.

             

            • Can the 2018 Administration tool access and administrate a 2018 and 2016 vault?

            No.

             

            • Will a desktop with the 2018 PDM client be able to access a vault running on a 2016 backend?

            No.

             

            • When we first started using PDM Standard, we were using a vault server on 2018 and all the clients were on 2017.

            It may not have been officially supported, but it certainly worked!

            This doesn't work, but it may appear so if you are using SOLIDWORKS 2017 and SOLIDWORKS PDM Client 2018 on the same computer. PDM has backwards compatibility for SOLIDWORKS files and the PDM Add-in for SOLIDWORKS.

             

            Btw, i also tried to import the CEX file you attached, and it looked fine in my 2018 SP3 vault.

             

            Is the old vault beyond moving, upgrading and reconfiguration to adjust to your current department/company's way of handling files and processes? While i too like the idea of starting fresh, I would still go a long way to keep the old vault, keeping history, and everything that has worked fine up until now. Importing a large amount of data into a new vault is a lot of work

             

            BR

            Martin

              • Re: Managing 2 Vaults, PDM 2016 & 2018
                Mac Readhead

                Good Morning Martem:

                 

                Thanks for the fantastic answer!

                The reason we're starting fresh is we're joining our ways of doing work with our parent companies' to better fit their system. Almost all of the old links will be irrelevant, if not damaging to the new system if it went through our new workflow. Previously there was intent to use a workflow but it never managed to happen, so there's tens of thousands(almost 4TB) of files sitting at WIP.

                 

                We've toyed with the idea of keeping the old vault around, and simply having access to 2, but I don't want anyone to accidentally be using the old vault's resources, dated as they are. Most of our work is "one and done" custom, so we rarely need to access previous work, nor would we be able to utilize it with our top down design approach. We'd likely have the old data as an archive with the same folder structure.