Verified Answers

If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it!  Learn more

  • State Not Answered
  • Replies replies
    3
  • Subscribers subscribers
    165
  • Views views
    103
  • Users 0 members are here
Related
Options

CBT to migrate data from 10.60 to latest

SupportTools

Hi Team,

We have an old SA version 10.60 is getting migrated with the latest version in a new build server and now we want move the OLD SA data to the new SA

packages.

policy

software policy 

folders etc.

I have gone through the CBT guide but i still have some questions before i start.

cbt -e <content_dir> -f <filter_file> -cf <target_core_config> 

from the above command i know -e should be provided with the folder path where it has been exported.

-f filter file to be given under the path opt/opsware/cbt/filters/

can you please guide me what is the -cf option and what is should be using.

Also is there any other way to copy the data from OLD to new at once.

Thanks

  • 0  

    Hello,

    Without -cf will automatically use "/opt/opsware/cbt/cfg/default.properties"

    If you require any changes, either modify the default or create your own based on it

  • 0 in reply to lazarmi

    Hi lazarmi

    Thanks for the quick help. Can I know on what basis i should creating the new property file.

    Also can you guide if I can download all the required filters at once and move to new SA.

    This will help me to complete migration.

    Thanks 

  • 0   in reply to SupportTools

    Already said that this is the basis "/opt/opsware/cbt/cfg/default.properties". You may don't want to keep password within the default file,hence you may create a file you can better protect, for instance.

    As a best practice, recommendation, migrating everything/all at the same time is not a good approach! First, because you won't need everything, second, will take longer and is harder to debug in case of any failures.

    So, do not export things that you can recreate (patch metadata, patches, RPMs for patching purposes, compliance policies that you can import from MPP) and export only what's really required (this is a good timing for you to do housekeeping)

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.