Forum Discussion
AltostratusAPM Policy Migration Between Standalone TMOS 17.1.3 Systems
Hi everyone,
We're migrating a single production APM policy from an i4600 to an r4600 appliance. Both systems are running TMOS 17.1.3, and the new appliance will not be part of the existing DSC cluster.
We tried exporting/importing only the APM policy, but the import fails because referenced objects are missing on the target system. A full UCS restore would also migrate many unused objects that we don't want.
Is there a supported way to:
Analyze an APM policy and list all required dependencies before import?
Export/import only the APM Customization GUI (HTML/CSS/JavaScript templates)?
Migrate a single APM policy without restoring the entire APM configuration?
Any recommended best practices for this scenario would be appreciated.
Thanks in advanced!
4 Replies
- Juergen_Mang
MVP
I always exporting/importing only the APM policy and create the missing objects before by hand.
Try an import -> Look through the logs -> Create the missing objects -> Try again
pakiThanks Juergen for your reply.
That was my assumption as well and it looks like this is the most practical approach. I was hoping there might be a way to migrate only the APM Customization GUI independently from the rest of the policy, but it seems that isn't supported.
Thanks for confirming the recommended workflow.
Hello paki
In simple policies export/import will automatically recreate the referenced objects, e.g. Active Directory.
But indeed some objects, e.g. kerberos keytab, might be needed to be created by handAs for Customization you can manually copy/paste from Access>Profiles/Policies/Customization>Advanced
- paki
Thank you everyone.
I successfully migrated the policy.
Thanks again for your help!
