Scheduled XML backups: which description best captures their usefulness and limitations?

Scheduled XML backups: which description best captures their usefulness and limitations?

• A. Useful for large production sites; not recommended as a backup method
• B. Useful for small sites, test sites, or in addition to database and directory backups; not recommended to rely on this backup method for production sites
• C. Not recommended for any production use
• D. The primary disaster recovery method

Answer: (B)

Scheduled XML backups function as an export of Confluence content that can be automated to run regularly. They’re most useful for small sites or test environments, and they can be handy as a supplementary copy of content for migration or targeted restoration. However, they aren’t a primary disaster recovery method for production sites. They often don’t capture everything you’d need for a full recovery—such as user accounts, groups, permissions, configuration, and possibly some attachments—and restoring from XML exports tends to be more manual and time-consuming than restoring from a full database and attachments backup. So, use XML backups to augment a broader backup strategy, not as the sole production backup.

Scheduled XML backups function as an export of Confluence content that can be automated to run regularly. They’re most useful for small sites or test environments, and they can be handy as a supplementary copy of content for migration or targeted restoration. However, they aren’t a primary disaster recovery method for production sites. They often don’t capture everything you’d need for a full recovery—such as user accounts, groups, permissions, configuration, and possibly some attachments—and restoring from XML exports tends to be more manual and time-consuming than restoring from a full database and attachments backup. So, use XML backups to augment a broader backup strategy, not as the sole production backup.