I would like to echo Luiz's comments.
Setting up a cron job to copy, zip and scp your <confluence_home> to another is a great idea. For a full production backup you will need to do the same thing with the confluence database.
The XML backup utility built into Confluence can be a resource hog as the size of your instance grows. It is a good idea to have the process that backs up your product be external to the product. This give you an extral layer of protection through abstraction
You can change the time of daily Confluence backup, please follow this link -
Aslo I hope you find this link useful too https://www.adaptavist.com/display/Plugins/Backup+Manager
In addition to the previous comments, if you have a large instance would be also recommended to take a look at our production backup strategy to better understand how to approach a backup strategy in this kind of environment:
Hi my Community friends! For those who don't know me, I'm a product marketer on the Confluence Cloud team - nice to meet you! For those of you who do, you know that I've been all up in your Co...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs