8 Replies Latest reply on Mar 19, 2015 3:53 PM by Jim Sculley

    Restoring from Backups

    Jim Sculley

      After a spectacular failure of the File Version Upgrade Tool I am faced with the task of restoring from backups.  However, I have some serious concerns.  If I upgraded my database and archive server to SQL Server 2014 and EPDM 2015, do I have to revert back to SQL Server 2008 and EPDM 2013 before restoring the database and file archive from backups?  Do I have to basically uninstall everything and re-install as though I am installing SQL Server 2008 and EPDM 2013 for the first time?

       

      Jim S.

        • Re: Restoring from Backups
          Jeff Sweeney

          Did you have the File Version Upgrade tool create new versions? If not, I don't think there is a reason to roll your database back. Perhaps you can get by with only restoring your archive server?

           

          If so, there is a chance EPDM 2013 will read data from SQL 2015, as long as you didn't update the database to the 2015 format.

           

          Either way, this is a big issue, I think you need to contact your VAR, a forum isn't going to get detailed enough information.

            • Re: Restoring from Backups
              Jim Sculley

              The FVUT was set to make new versions and move the revisions.  See my other post below for gory details.

               

              I was waiting on a call back from our VAR when I posted the question.  They did get back to me and the solution was to leave SQL Server and SW/EPDM 2015 installed.  After restoring the archive files and database, you simply have to upgrade the file vault database (see page 111 of the Installation Guide).  I did this last night and it seems to have worked.  There is some residual mess left over on client workstations because I think they have some local copies (that the File Version Upgrade Tool left behind) that are 'newer' than the restored backup files.  A 'Get Latest Version' seems to correct that issue.

               

              Jim S.

            • Re: Restoring from Backups
              Jeff Sweeney

              This may be a topic for another thread, but I'd love to learn more about the "spectacular failure" ...an opportunity to learn for your misery I guess.

                • Re: Restoring from Backups
                  Jim Sculley

                  This was a plain vanilla by-the-book Upgrade from SW2013 to SW2015.  Prior to beginning, the servers has their OS upgrades to Windows Server 2008 R2.  SQL Server was upgraded from 2008 to 2014.  I started the FVUT at about 9 AM Sunday.  There were about 100,000 files.  The work was split into 16 work instruction files and I had 8 machines performing the upgrade.  The FVUT settings were all defaults (new version, move revision, rebuild files, etc).  Our vault is not exotic.  Simple SolidWorks files with no pasted references or anything like that.

                   

                  I ran the FVUT to upgrade to 2013 a couple years back and the process was fast and error-free. This time, the process was incredibly slow.  The SW portion was quick, the slave machines were opening and saving files quickly.  When the time came or things to be checked in, it all slowed to a crawl.  I could stare at a progress bar for 5 minutes and not see it move one pixel.  The first 8 work instruction sets took nearly 8 hours.  When I looked at the logs, they all looked about like this:

                   

                  [1/5/2015 12:03:00 PM] 8333 files successfully converted.

                  [1/5/2015 12:03:00 PM] 14 files failed to convert.

                  [1/5/2015 12:03:00 PM] 2495 files failed to check in.

                   

                  About 8k files converted, with 2k failing to check in.  Every slave machine had the same sort of problem:

                   

                    

                  BATCHSUCCESSFAILDIDN'T CHECK IN
                  176332434
                  282342575
                  3855422501
                  4879522383
                  5824022442
                  6821312929
                  789492551
                  8914712807
                  98333142495
                  1088982519
                  1178822509
                  1285592441
                  13912612811
                  1488852473
                  1597312722
                  1681802578
                  TOTAL1373592341170
                  17616PARTS
                  4063ASSEMBLIES
                  19473DRAWINGS

                   

                  When things started going wrong, the logs started to look like this:

                  ===================================

                  [1/5/2015 8:16:53 AM] ERROR: Failed to check in file 'E:\_EPDM\Engineering\Projects\123456-TEST PROJECT\4. Mechanical WIP\423616.SLDASM'. File is not converted.

                  [1/5/2015 8:16:53 AM] The file format is not recognized.

                  [1/5/2015 8:16:53 AM] ERROR: Failed to undo check out for file 'E:\_EPDM\Engineering\Projects\123456-TEST PROJECT\4. Mechanical WIP\423616.SLDASM'.

                  [1/5/2015 8:16:53 AM] The file format is not recognized.

                  =====================================

                   

                  So, when it was all over, there were 35k files (about one in four) left checked out.  And ten users sitting on their thumbs all day Monday.  SW support has requested that I send them the entire vault (400 GB) and database and didn't really have any suggestions for me other than restore from backup.

                   

                  Jim S.

                    • Re: Restoring from Backups
                      Jeff Sweeney

                      Ouch. <virtual pat on the back>

                       

                      Did you try to manually check in the files? "The file format is not recognized." usually means the document manager could not read the file, though often times I find that to be a false negative. Did you notice if indeed the files were corrupted in some way?

                       

                      I wonder if the client's document managers were still 2013 and could not read the files as they were getting upgraded....did you notice anything interesting about the client 2015 upgrades?

                        • Re: Restoring from Backups
                          Jim Sculley

                          I did not want to check in the files because (as Brian says below) the revisions would not be moved.  I left it all as is and restored from backup.  I have the 'bad' database and file archive for forensic purposes.  Looking at one file that was processed by my client machine, no corruption was found and the file was successfully converted to 2015.  The document manager DLL files on the clients are showing file version 23.1.1.2.

                           

                          Here's a log file trimmed down to represent a single file (CUSTOM MAGNET MOUNT.sldasm).  I shortened the paths to make things easier to read and the areas of '...' are just names of files before and after the CUSTOM MAGNET MOUNT.sldasm file.

                           

                          =============================================================================================================

                          [1/4/2015 8:23:03 AM] Upgrade process started at 1/4/2015 8:23:03 AM

                          [1/4/2015 8:23:03 AM] PDMWE 2015 build number '745'

                          [1/4/2015 8:23:03 AM] File Vault Upgrade Tool Settings:

                          [1/4/2015 8:23:03 AM] Files of type: <All SW file types>

                          [1/4/2015 8:23:03 AM] Look in folder: E:\_EPDM

                          [1/4/2015 8:23:03 AM] Include SubFolders: 1

                          [1/4/2015 8:23:03 AM] Create new version of files and move revision

                          [1/4/2015 8:23:03 AM] Save pre-2003 drawings with "Automatic update of BOM": 1

                          [1/4/2015 8:23:03 AM] Ignore files containing missing references: 0

                          [1/4/2015 8:23:03 AM] Do complete rebuild (Ctrl+Q) on files: 1

                          [1/4/2015 8:23:03 AM] Process files already in target format: 0

                          [1/4/2015 8:23:03 AM] Activate all configurations before saving: 0

                          [1/4/2015 8:23:03 AM] Number of work instruction files to create: 16

                          [1/4/2015 8:23:03 AM] Shared location for work instruction files: \\us-nor-epdmarcv\Latest Admin Images\WorkInstructions

                          [1/4/2015 8:23:03 AM] Batch 1:

                          ...

                          ...

                          ...

                          [1/4/2015 8:23:03 AM] E:\_EPDM\...\CUSTOM MAGNET MOUNT.sldasm    Version :4

                          ...

                          ...

                          ...

                          [1/4/2015 8:25:25 AM] Internal batch 1: Clearing local cache...

                          [1/4/2015 8:25:36 AM] Done!

                          [1/4/2015 8:25:36 AM] Upgrading files in batch 1.

                          [1/4/2015 8:25:36 AM] 881 files total in batch, of which 881 are to be upgraded:

                          ...

                          ...

                          ...

                          [1/4/2015 8:25:36 AM] E:\_EPDM\...\CUSTOM MAGNET MOUNT.sldasm - Version 4

                          ...

                          ...

                          ...

                          [1/4/2015 8:25:37 AM] Internal batch 1: Checking out files...

                          [1/4/2015 8:25:43 AM] Done!

                          [1/4/2015 8:25:43 AM] Internal batch 1: Upgrading files...

                          ...

                          ...

                          ...

                          [1/4/2015 8:50:10 AM] File 'E:\_EPDM\...\CUSTOM MAGNET MOUNT.sldasm' opened at '1/4/2015 8:50:10 AM'.

                          [1/4/2015 8:50:10 AM] File 'E:\_EPDM\...\CUSTOM MAGNET MOUNT.sldasm' saved at '1/4/2015 8:50:10 AM'.

                          ...

                          ...

                          ...

                          [1/4/2015 9:12:56 AM] Done!

                          [1/4/2015 9:12:56 AM] Internal batch 1: Checking in files...

                          [1/4/2015 9:14:44 AM] ERROR: Failed to check in file 'E:\_EPDM\...\CUSTOM MAGNET MOUNT.sldasm'. File is not converted.

                          [1/4/2015 9:14:44 AM] The file format is not recognized.

                          [1/4/2015 9:14:44 AM] ERROR: Failed to undo check out for file 'E:\_EPDM\...\CUSTOM MAGNET MOUNT.sldasm'.

                          [1/4/2015 9:14:44 AM] The file format is not recognized.

                          ...

                          ...

                          ...

                          [1/4/2015 9:14:47 AM] Done!

                          [1/4/2015 9:14:47 AM] Updating revision tags...

                          [1/4/2015 9:14:47 AM] Done!

                          [1/4/2015 9:14:47 AM] Finished upgrading batch 1 at 1/4/2015 9:14:47 AM.

                          ...

                          ...

                          ...

                          [1/4/2015 9:14:48 AM] E:\_EPDM\...\CUSTOM MAGNET MOUNT.sldasm - Version -25163587 failed to unlock, file was not migrated.

                          ...

                          ...

                          ...

                          [1/4/2015 9:14:51 AM] Internal batch 2: Checking out files...

                          ...

                          ...

                          ...

                          BATCHES 2 THRU 1835 APPEAR HERE

                          ...

                          ...

                          ...

                          [1/4/2015 11:35:35 PM] Done!

                          [1/4/2015 11:35:35 PM] Finished upgrading batch 1835 at 1/4/2015 11:35:35 PM.

                          [1/4/2015 11:35:36 PM] Finished upgrading files.

                          [1/4/2015 11:35:36 PM] The following files were not converted due to error:

                          [1/4/2015 11:35:36 PM] E:\_EPDM\...\CUSTOM MAGNET MOUNT.sldasm - Version 4

                          ...

                          ...

                          ...

                          [1/4/2015 11:35:40 PM] Total of 10067 files processed:

                          [1/4/2015 11:35:40 PM] 7633 files successfully converted.

                          [1/4/2015 11:35:40 PM] 2434 files failed to check in.

                          ==================================================================

                           

                          As logs files go, this one isn't very useful.

                           

                          Another side effect of this fiasco is that all the client machines are littered with files that are marked as locally modified.

                           

                          Jim S.

                        • Re: Restoring from Backups
                          Brian McEwen

                          Sorry to hear that.

                          I have had the FVUT fail to check-in as well, but I think it was more of a got stuck issue, and then nothing after a certain point was checked in.  It was only roughly 1000 files. I ended up just checking them in manually... After manual check-in the files that were in Released state lost the database revision stamp, I think it doesn't get moved until check-in. I fixed some, but since you can't search by database ("Local") revision I'm sure I missed some and they still say "no revision".

                          • Re: Restoring from Backups
                            Jim Sculley

                            So, SolidWorks finally got back to me with an answer on this.  They say that this problem will occur if you have blocked log ins from the EPDM Admin tool.  Since the Installation Guide states 3 different times: "Make sure that no users are working in the old file vault", the Block Logins option seems like a wise choice.  Apparently it is not.  There is an SPR (560194) which is marked as Closed...Inactive.  It recommends this:

                             

                            ========================

                            If you want to block logins for users - create a group and assign the administrative permission "Refuse login" - then add all users temporarily to that group. This will prevent users from logging in.

                            ========================

                             

                            It would appear that this was the source of my problem, but I would like more confirmation.  I would appreciate it if someone could upload the log files from their successful use of the FVUT when upgrading to 2015. Preferably form someone who used multiple client machines.  I'm looking for the log files from one client, which should look something like this:

                             

                            Upgrade 54A93E61 Batch 1.log

                            Upgrade 54A93E61 Batch 1 Errors.log

                             

                            I would like to compare a successful client log with my unsuccessful one.

                             

                            Jim S.