Within Cloud CMS sync capabiities are generally referred to as the "transfer system". They allow you to export individual objects, data stores or even collections of these as an archive (ZIP) within a vault. You can then move those archives to storage for backup or move them to new Cloud CMS server instances for restoration or replication.
We have support for transfer within our API, our drivers and also within the user interface. The latter is useful in that you can script it pretty effectively to push content between environments.
Bear in mind that these "transfer" capabilities are not exactly database backup/restore. Instead, they're copying data out of Cloud CMS into a standalone ZIP file and then copying data back into Cloud CMS from that zip file. These are often used for point in time backup of individual content branches, projects or repositories.
However, we do not offer raw database restore/backup within our SaaS offering. The datastores are secure and guarded on our SaaS offering.
If you want access to the raw database (MongoDB), we recommend running Cloud CMS on-premise. In that way, you will own the database and can use your own tooling (or MongoDB's tooling) to dump, import and export databases and snapshot volumes according to your own desired strategies.