In automating backup processes for Tableau Server, what strategy should be implemented to balance system performance and data recovery needs?

The optimal strategy for automating Tableau Server backups involves balancing performance impact with recovery needs. Scheduling backups to run nightly during off-peak hours is the industry-standard best practice. This approach minimizes performance degradation for users during peak business hours, as the backup process is resource-intensive. It also provides a recent, daily recovery point (a low Recovery Point Objective, or RPO), ensuring that a maximum of 24 hours of work is at risk in the event of a failure. This strategy effectively balances the two critical requirements of system availability and data protection.

A. Hourly backups are excessively frequent for a full Tableau Server backup, which can take significant time and resources, leading to severe and constant performance degradation for users.

C. Monthly backups create an unacceptably large window for data loss. A Recovery Point Objective (RPO) of up to 30 days is inadequate for nearly all production environments.

D. RAID (Redundant Array of Independent Disks) provides hardware fault tolerance against disk failure, but it is not a backup. It does not protect against data corruption, accidental deletion, or logical errors.

1. Tableau Server Documentation: In the "Back Up Tableau Server Data" guide

it is explicitly recommended to perform backups during non-business hours. The documentation states

"We recommend that you run the backup process on a regular basis (daily

for example)

during non-business hours... The backup process can use a lot of server resources. If possible

you should run it during non-business hours."

Source: Tableau Help

"Back Up Tableau Server Data

" section "Create a backup using the TSM CLI."

2. Tableau Server Documentation: The "Server Maintenance" guidelines reinforce the need for a structured backup plan as a core administrative task. It emphasizes creating a script for automation

which is typically scheduled for off-peak times.

Source: Tableau Help

"Tableau Server Administrator Guide

" section "Server Maintenance."

3. University Courseware: General principles of system administration and disaster recovery planning advocate for scheduling resource-intensive tasks like backups during periods of low system utilization. This minimizes contention for resources and impact on interactive users.

Source: Carnegie Mellon University

Computing Services

"Data Backup and Recovery Best Practices

" section "Scheduling Backups." (This document outlines the principle of off-peak scheduling to minimize performance impact

a universal best practice applicable to Tableau Server).