Sync between two different MB version

Hi,

When user uploads an asset into MB 8.1 it must replicate in v4.6.2 and vice versa. This will help us in using 4.6.2 and 8.1 parallel in production till 8.1 is live and stable. Is this possible?

Thanks

Find more posts tagged with

Comments

Reji Varghese

Theoritically you should be able to do it. Never done it myself.

For the assets replication, you only need to take care of the SQL database and the MBDataDirectory.

So, if you have a mirrored SQL database on 4.6.2 and 8.1, that part is solved.

Now for the MBDataDirectory, you might consider placing the directory on a shared drive or a NAS storage.

Give this a thought and may be there are other ways to do it.

Shravan

Thank you information. I will do some research on it. Not sure if can use same datadirectory for both instances. May have some issues like data integrity.

Reji Varghese

Or, you can use replication technologies to replicate the MBDatadirectory.

Shravan

Yes. Nice thought.

tposton

What is the use case to run two systems in production? That is not a recommended solution nor am I sure that can be fully supported. The MBDatadirectory must be independent for each instance using it. You risk significant corruption otherwise.

Shravan

To avoid downtime till new MB goes live.Asset migration from existing to prod is atleast 10 days effort including testing. In these days user may upload few assets in old MB . And these has to present in new MB.

Migrateduser_427

We did the upgrade to hardware first, then upgraded MB in place (only one system) from 4.6 to VMB 7. Since the Legacy clients still worked, this meant users were only interrupted for a few days over weekend during the time to upgrade and index the assets into IDOL (deep zoom previews, IDOL summary, ect.).

However, knowing what I know now, I would have kept both systems running separately.

Having two systems and just migrating assets as needed (drawing a line in the sand as it is said), would help in having a clean fresh start in a whole new world of DAMs. At some point you will see usage of the old system declining. Set a threshold for minimum usage of the old system then completely retire it when it is met.

A caveat this is my experience against our use cases. I do like to apply this theory when looking to enhance functionality.

This is what I would have done if doing the upgrade:

Anything in the old system stays there. Build out the new system and begin uploading in the new system after all the new structure is implemented (use cases, permissions, folders, structured metadata taxonomies, workflows, ect). Stop uploading in the old system.

The main reason I say this, there are many folders and permissions which do not apply well in the new MB 8. Using collections, and saved search collections make folder taxonomy obsolete (now folders are only for permissions and asset administers).

All assets need to have structured metadata as their taxonomy rather than folder based taxonomy.