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
- Client1 backup starts...
- 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.
- Pre-script completes, Scan runs and completes
- Backup runs and completes
- Post backup script starts application back up on client1
Let us know if this helps...
Ernst F. Graeler
Senior Engineer III