Upgrade practices
Posted: Fri Dec 15, 2023 10:28 am
During upgrades, our procedure is generally as follows:
- Perform undo checkout on any files that have been left checked out, this includes private state files
- If undo checkout fails (usually because the file has the same name as a vault file), delete from vault
- Backup PDM system
- Upgrade PDM system
Our procedure gives the vaults an annual cleanup and prevents files from being left checked out for many years. Of course there are many users who do not understand that local and private state files are not actually saved on the server. Depending on user-specific settings the undo-checkout/deleted files are either left local in user vault views or deleted automatically. We have never experienced great backlash from this procedure (from ~600 users), I suspect because most of these files have long been forgotten by the creating user.
I am curious whether anybody else performs this type of maintenance either during the upgrade or before/after. I cannot think of a technical reason why the files need to be checked in prior to an upgrade. Of course if all files are checked in, a subsequent server backup is ensured to contain 100% of data, including that which would otherwise languish only in user vault views. But the system will still upgrade, and the user data will still remain on their machine, if this is not done, correct?
- Perform undo checkout on any files that have been left checked out, this includes private state files
- If undo checkout fails (usually because the file has the same name as a vault file), delete from vault
- Backup PDM system
- Upgrade PDM system
Our procedure gives the vaults an annual cleanup and prevents files from being left checked out for many years. Of course there are many users who do not understand that local and private state files are not actually saved on the server. Depending on user-specific settings the undo-checkout/deleted files are either left local in user vault views or deleted automatically. We have never experienced great backlash from this procedure (from ~600 users), I suspect because most of these files have long been forgotten by the creating user.
I am curious whether anybody else performs this type of maintenance either during the upgrade or before/after. I cannot think of a technical reason why the files need to be checked in prior to an upgrade. Of course if all files are checked in, a subsequent server backup is ensured to contain 100% of data, including that which would otherwise languish only in user vault views. But the system will still upgrade, and the user data will still remain on their machine, if this is not done, correct?