Orchestrated backup of Alfresco application (not Cold Backups) via workflow

Last post 06-28-2019, 4:22 PM by Egg. 4 replies.
Sort Posts: Previous Next
  • Orchestrated backup of Alfresco application (not Cold Backups) via workflow
    Posted: 06-03-2019, 4:26 PM
    • Egg is not online. Last active: 10-19-2019, 11:01 AM Egg
    • Not Ranked
    • Joined on 02-15-2019
    • Rio de Janeiro, Brazil
    • Newcomer
    • Points 15

    Hi, Folks, 

    Can someone point me any documentation on how to set up Commvault workflow to do a orchestrated backup of Alfresco application as the procedure below? 

    Stop Alfresco.
    Backup the database Alfresco.
    Backup the Alfresco dir.root directory in its entirety.
    Store both the database and Alfresco dir.root backups together as a single unit. For example, store the backups in the same directory or compressed file.
    Start Alfresco.

    Two Linux clients. One hosts the application and the other hosts the database. Agents already installed and doing regular backups. I think that it should be possible even with different clients/agenst (a bunch of Bash scripts to stop (PreScan)/start (PostBackup) Alfresco and probably some Commvault scripts), but maybe there is a workflow to do that. 

    Commvault v11 SP13+

     


    Braga, Eduardo
    Backup Administrator
  • Re: Orchestrated backup of Alfresco application (not Cold Backups) via workflow
    Posted: 06-05-2019, 7:43 AM

    You don't need a workflow. Just use pre commands to stop Alfresco, backup database, and start Alfresco in a post command. Choose the directories and files you want to protect in this subclient.

  • Re: Orchestrated backup of Alfresco application (not Cold Backups) via workflow
    Posted: 06-27-2019, 4:23 PM
    • Egg is not online. Last active: 10-19-2019, 11:01 AM Egg
    • Not Ranked
    • Joined on 02-15-2019
    • Rio de Janeiro, Brazil
    • Newcomer
    • Points 15

    Thank you very much, but a I need one more thing. Consider that the app and the database are on different servers/clients. 

    Stop Alfresco app hosted on client1.
    Backup the database Alfresco hosted on client2.
    Backup the Alfresco dir.root directory in its entirety hosted on client1.
    Start Alfresco app hosted on client1.

    Braga, Eduardo
    Backup Administrator
  • Re: Orchestrated backup of Alfresco application (not Cold Backups) via workflow
    Posted: 06-27-2019, 5:33 PM
    • efg is not online. Last active: 10-22-2019, 2:17 PM efg
    • Top 10 Contributor
    • Joined on 02-02-2010
    • CommVault Tinton Falls NJ
    • Master
    • Points 1,678

    Hi Egg,

    Here is how you can set this up...   I'm assuming that BOTH client1 & 2 are Commvault clients with agents installed...

    Create a backup script from the database agent on client2 but SAVE the script to client1 using the "Save as script" feature in Commvault.  Scripts can be run from ANY CV client.  Be sure to save the script as a "Synchronous" script.   This way the script will WAIT for the backup to complete before exiting.  You may also need to "tweak" the script as these scripts are saved as 2 files...  the script and the "input" XML file.  Tweak the script and add the FULL path to the location of the XML file, as the "save as script" process assumes everything will be run from the same directory.

    Then on client1 create a script that stops the Alfresco app, and then calls the backup script for client2

    Then in the subclient configuration on client1 point to the Alfresco root dir for content, and put the "shutdown & backup script" in as a pre-scan script.  This way any files generated during the shutdown of the app will get picked up during the scan phase of the FS client.

    In the "post-backup" script block, add the script used to start the application back up.

    Now schedule the backup from client1 at the appropriate time. (no need to schedule client2)

    So with this configuration the flow will be as follows

    1. Client1 backup starts...
    2. Pre-Scan kicks in and stops the application and then triggers the DB backup (in commvault) on client2.  Since that is configured as a syncronous process, it will wait for the client2 backup to complete before continuing.
    3. Pre-script completes, Scan runs and completes
    4. Backup runs and completes
    5. Post backup script starts application back up on client1
    Let us know if this helps...

    Ernst F. Graeler
    Senior Engineer III
    Development
  • Re: Orchestrated backup of Alfresco application (not Cold Backups) via workflow
    Posted: 06-28-2019, 4:22 PM
    • Egg is not online. Last active: 10-19-2019, 11:01 AM Egg
    • Not Ranked
    • Joined on 02-15-2019
    • Rio de Janeiro, Brazil
    • Newcomer
    • Points 15

    Great awsner! I'll consider it as thread resolved. Thank you. 


    Braga, Eduardo
    Backup Administrator
The content of the forums, threads and posts reflects the thoughts and opinions of each author, and does not represent the thoughts, opinions, plans or strategies of Commvault Systems, Inc. ("Commvault") and Commvault undertakes no obligation to update, correct or modify any statements made in this forum. Any and all third party links, statements, comments, or feedback posted to, or otherwise provided by this forum, thread or post are not affiliated with, nor endorsed by, Commvault.
Commvault, Commvault and logo, the “CV” logo, Commvault Systems, Solving Forward, SIM, Singular Information Management, Simpana, Commvault Galaxy, Unified Data Management, QiNetix, Quick Recovery, QR, CommNet, GridStor, Vault Tracker, InnerVault, QuickSnap, QSnap, Recovery Director, CommServe, CommCell, SnapProtect, ROMS, and CommValue, are trademarks or registered trademarks of Commvault Systems, Inc. All other third party brands, products, service names, trademarks, or registered service marks are the property of and used to identify the products or services of their respective owners. All specifications are subject to change without notice.
Close
Copyright © 2019 Commvault | All Rights Reserved. | Legal | Privacy Policy