Best Practices for restoring SAC Story when migrating between tenants

[aeshirley]

Recently we implemented multiple tenants within our SAC system. Before utilizing the Dev, QA, and Prod tenants we would like to have processes in place for migrating the stories, models, ect.
We were wondering what the best practices are to restore a Story/Model in Production if there was an issue with the QA migrated version? If the issues happens between Dev and QA, you can use the Prod version to restore Dev/QA to the original version without the issues. But once the Story/Model goes to Prod, how can we revert back to a version that does not have errors/issues?

[DebjitSingha]

Hello aeshirley,

Assuming all three of your environments are in same region (for content network based approach; eg. us10 in tenant URL) and not under EU region, you can use -

1. Content network based LCM
2. File System based LCM

At present, there are no provision of versioning. What this means once imported system wont offer you to rollback the changes. So, in your scenario if your changes are move all the way to PROD (from Dev and QA) then system wont let you roll back changes.

One way to address this is to always take local file backup before moving them another tenant. Say you ware moving changes to PROD, before performing transport (via content network or file system), you take a local backup using menu > Transport > Export and keep that file in case you need to roll back to previous state/ version.

Now keep in mind this option works only until your system remain in same version (or N+1; where N is the version of source system, say DEV). So, your local back becomes useless if your PROD gets updated during QRC system upgrade.

Idly we want to have a streamlined transport process with standard functionality like transport versioning and rollback options. Similar options are available in all ABAP based environments and BOBI systems as well. Here is an enhancement request where you can vote and add comments or create a new one for transport versioning-

provide change management tool (for custom content migration) for SAC like STMS for SAP ABAP

Thanks,

Debjit

[William_Yu]

Hi aeshirley,

I would recommend you to watch below webinar.

https://event.on24.com/wcc/r/2449273/7B04E5CCB15F9BA5CDFB81475CDBA109?

Best regards, William