nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Steps to check content store after upgrade

LucyLee

Hi ,

We are planning to upgrade from Teamsite 7.1 to TS7.5,

Please let us know if there are any specific steps to be followed to check if the contents in the content store are the same after upgrade

Is there a way we can record the contents are same after and before upgrade as we are doing the upgrade for a bank

Thanks,

Lucy

Find more posts tagged with

Comments

Adam Stoller

Is this on Windows or Unix?

Are you doing an in-place upgrade or a fresh-install-on-new-server-and-transfer upgrade?

For Unix you could run [check]sum on all the files within the backing store before and after the upgrade - but the problem is that if the upgrade involves any modifications to the backing store (e.g. for improved efficiency), then those might show up as differences but that wouldn't mean that anything went wrong - so it's a questionable means of verification.

For either OS - you should run iwfsck on the backing store before and after the upgrade to verify that the consistancy of the backing store is, and remains, good.

nipper

Also check the release notes. I don't think there was a direct upgrade from 7.1 to 7.5

LucyLee

Hi Ghoti,

Thanks. The box is windows and it is a fresh install of 7.5 where we have to migrate the content store

Is there a way we can get a report or a log that says that all contents have been migrated

That way we can produce the same to prove that all contents are successfully migrated

Thanks,

Lucy

Adam Stoller

Well, if you use iwmigrate and store the output (STDOUT and STDERR) into a log file - you'll have a record of the importing process - but I don't think it gives you a complete record of all the files and their respective versions - and it will only tell you that the data was migrated it won't give you a real comparison between source and target (if the migration is successful it means that source and target should be identical - at least as far as the amount of history that was migrated)

Other than that - you can produce your own "surface" comparison by running a script to record all the files in the staging area of all the branches on your source server (or before upgrading a single-server) and then run the same on the target server (or after upgrading a single-server) and comparing that output. If you do this you can choose the level of detail you want to record for each file and then make sure the output is sorted the same way so that you can get a reasonable comparison.