I don’t think this is achievable by the in-built scheduling. But you can write a workflow to trigger the backups on these two servers one after the other and schedule this workflow.

Curious what is the use case though.

Thanks,

Sunil-

@0ber0n This could be something that you accomplish with a post script.

Save as a script the second client machine backup type you like. Place that in the post backup script section for server1 and ocne complete it will kick off the backup.
https://documentation.commvault.com/2023e/expert/save_as_script_overview.html
https://documentation.commvault.com/2023e/expert/pre_processes_and_post_processes_overview.html

You could also leverage commandline functions and add them into a native script that you create.

Otherwise @Sunil recommendation of workflow would be best option.

Hi @Scott Reynolds 

I guess Pre/Post Script is not supported by Always on SQL Subclient, it is greyed out. this couldn’ t be achievable by post script.

@Sunil 

When backup runs at the same time, there is heavy CPU usage on the server. The first backup can sometimes lag, so unfortunately it cannot be clear in the time we put between two backups. The most logical thing is to have a sequential backup, when the first backup is finished, let the second one run.
Is it possible to achieve this with Workflow, how can I do it?