cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Community Tip - You can change your system assigned username to something more personal in your community settings. X

vault file movement after upgrade (Source system don't shutdown when upgrade)

ssupport
7-Bedrock

vault file movement after upgrade (Source system don't shutdown when upgrade)

Version: Windchill 12.1

 

Use Case: Hi, I have successfully upgraded from Windchill 11.0 to Windchill 12.1. The next problem is, windchill 11.0 (Source system) is not turned off and is still running for work while the upgrade is running. So there are additional CAD and PART example files. How do I transfer additional files during the upgrade process? Is it possible to move the vault according to the difference between the old vault and the current vault?


Description:

this is the difference between source vault and target vault

 

 

Source System :

 

WhatsApp Image 2024-10-24 at 09.00.20.jpeg

 

 

Target System :

WhatsApp Image 2024-10-24 at 09.00.19.jpeg

 

ACCEPTED SOLUTION

Accepted Solutions
avillanueva
22-Sapphire II
(To:ssupport)

Help us understand something, is it still running? If so, shut the source down so as not to cause further issues. The big thing with upgrades is the DB must be inline with the vaults. Not the end of the world but you could end up with missing files or in some cases, extra files that cause issues when writing new data to the vaults. There are standard validation scripts that you can run on vaults or folders which will validate that each file the database says should be there are there and it should be as simple to move in the missing files with the same timestamps. What should have happened is when you did your upgrade, you shutdown the source to freeze it until its complete.

 

Next question, did you make a complete copy of the vaults from source to target? Or are they using the same location? If it was a copy and source was still running, you might get extra files. It really depends on when the database extract was taken. That is the key part since what is in those vaults need to align. If you took the DB extract and users kept working, the work then did after that point is not in the DB extract so any files they added to the vault are stuck with the source. Adding them to the vault will not help since DB did not have a record of that. Recommend running WContentVerify Tool

 

View solution in original post

2 REPLIES 2
avillanueva
22-Sapphire II
(To:ssupport)

Help us understand something, is it still running? If so, shut the source down so as not to cause further issues. The big thing with upgrades is the DB must be inline with the vaults. Not the end of the world but you could end up with missing files or in some cases, extra files that cause issues when writing new data to the vaults. There are standard validation scripts that you can run on vaults or folders which will validate that each file the database says should be there are there and it should be as simple to move in the missing files with the same timestamps. What should have happened is when you did your upgrade, you shutdown the source to freeze it until its complete.

 

Next question, did you make a complete copy of the vaults from source to target? Or are they using the same location? If it was a copy and source was still running, you might get extra files. It really depends on when the database extract was taken. That is the key part since what is in those vaults need to align. If you took the DB extract and users kept working, the work then did after that point is not in the DB extract so any files they added to the vault are stuck with the source. Adding them to the vault will not help since DB did not have a record of that. Recommend running WContentVerify Tool

 

TomU
23-Emerald IV
(To:ssupport)

Was this a 'test' upgrade or your final 'production' upgrade?  For a test upgrade, it's fine to leave the original system running and people still using it, but for the production upgrade you need to shut down the original source system, copy the data to the new system, and the run the upgrade manager process.  Do not start the old system back up or allow anyone to use it after the production upgrade.  If you do, any changes made to the old system will not be propagated to the new system (unless you repeat the upgrade process all over again.)

Announcements


Top Tags