Planning Analytics

Planning Analytics

Get AI-infused integrated business planning

 View Only

  • 1.  Help with Migrating PAW Content from Windows Server 2016 to 2019

    Posted Tue August 06, 2024 09:50 AM

    Hi all,

    I'm planning to install IBM Planning Analytics Workspace (PAW) on a fresh Windows Server 2019 and need to migrate my existing content, books, and apps from Windows Server 2016.

    Could someone please guide me on the following:

    1. How to migrate PAW content (books, apps, etc.) from Windows Server 2016 to the new installation on Windows Server 2019.
    2. How to determine the location of the PAW content and where it is stored.

    Any resources, documentation, or tips would be greatly appreciated!

    Thank you!



    ------------------------------
    Asgeir Thorgeirsson
    ------------------------------


  • 2.  RE: Help with Migrating PAW Content from Windows Server 2016 to 2019

    Posted Tue August 06, 2024 03:36 PM

    Asgeir,

    You just have to run the PAW backup.ps1 script on the Windows 2016 server, copy the backup folder and files to the other server, then run restore.ps1 <copied folder>  on the Windows 2019 server. Then validate. If the Windows 2016 PAW version is on the older side you will have some visible changes in reports.

    Here is the IBM documentation: https://www.ibm.com/docs/en/planning-analytics/2.0.0?topic=local-back-up-restore-planning-analytics-workspace



    ------------------------------
    Walter Coffen
    Technology Manager
    QueBIT Consulting, LLC
    ------------------------------

    Original Message


  • 3.  RE: Help with Migrating PAW Content from Windows Server 2016 to 2019

    Posted Wed August 07, 2024 10:05 AM

    Thank you @Walter Coffen, I will use this method. :)

    Does anyone know how and where the PAW data is stored, eg. what kind of an object contains the PAW data within the container?



    ------------------------------
    Asgeir Thorgeirsson
    ------------------------------

    Original Message


  • 4.  RE: Help with Migrating PAW Content from Windows Server 2016 to 2019

    Posted Wed August 07, 2024 11:20 AM

    PAW uses several different databases to store its content. Don't edit the working data files, but by default on Windows, the hidden folder C:\ProgramData\docker is the main Docker folder, under which a C:\ProgramData\Docker\volumes folder exists for the long term storage of data from the containers. It contains the PAW data files for four of the five databases from which the backup.ps1 generates zip files; bss.zip, mongo.zip, mongo_db.zip, redis.zip. The fifth backup file, mysql.zip, appears to be a table level extract from the bss Derby database and is for support of a distributed PAW. Typically, the \docker\volumes\ folder is mapped to a data storage drive (D:\ or E:\) right after the Docker installation rather than leaving it on the C:\ drive so your \docker\volumes\ folder is probably not under C:\ProgramData\. If you can't find it, the C:\ProgramData\docker\config\daemon.json configuration file will have the "data-root" parameter that defines the non-default docker location. I believe PAW has to stop for all the working PAW data to get written to the various databases that support it.



    ------------------------------
    Walter Coffen
    Technology Manager
    QueBIT Consulting, LLC
    ------------------------------

    Original Message


  • 5.  RE: Help with Migrating PAW Content from Windows Server 2016 to 2019

    Posted Wed August 07, 2024 02:43 AM

    Hi Asgeir,

    you can also go with the lifecycle manager (Administration -> lifecycle management) to transfer the books and apps from old to new installation.



    ------------------------------
    Dominik
    ------------------------------

    Original Message


  • 6.  RE: Help with Migrating PAW Content from Windows Server 2016 to 2019

    Posted Wed August 07, 2024 09:05 AM

    Agree. Lifecycle Manager is good if you just want to surgically move books, apps and plans and clean house, so to speak. I think it is limited to 100 assets though, but that may change in a Q4 release.

    But a restore from a backup also captures any folder structures you may have created, permissions on those folders, users, groups, group assignments, personal items for all users not just yourself, in a word, everything. But Lifecycle Manager will give you a "start over" if you want to take the opportunity to get rid of or abandon old, unused items in order to have a new "clean" environment for your shiny, new server. Maybe the folders and groups should be deliberately re-built rather than be exactly like the old server. A new server is always a good time to audit the existing structures.

    One note of caution, the restore eliminates everything in the target of the restore, it does not merge if you are trying to preserve new assets on the new server, but you could use Lifecycle Manager to get any really-new items backed up from the new server before the restore, then use Lifecycle Manager to add them back.

    Also, if the old PAW is older than 87, you won't be able to use Lifecycle Manager to migrate Workbenches, and if older than 81, you also won't be able to migrate Apps and Plan.



    ------------------------------
    Walter Coffen
    Technology Manager
    QueBIT Consulting, LLC
    ------------------------------

    Original Message