A database administrator manages a database server that is running low on disk space. A lot of backup files are stored on the server's disks. Which…

The most appropriate and professional action is to adhere to the established backup retention policy. This policy is designed to balance the need for data recovery with storage costs and compliance requirements. By deleting only the backup files that are older than the period specified in the policy, the administrator ensures that all necessary recovery points are preserved while safely reclaiming disk space. This is a standard, repeatable, and defensible procedure for managing backup lifecycle and storage capacity.

A. Move all the backup files to external disks.

This only relocates the problem without addressing the lifecycle management of old backups. It is also a best practice to store backups on separate media from the start, not as a reaction.

B. Delete all the backup files containing data that is rated as classified.

This is dangerous and counterintuitive. Classified data is often the most critical to protect and recover, making its backups essential. Deleting them would likely violate security and compliance policies.

D. Delete all the backup files except for the most recent one.

This is extremely risky as it eliminates the ability for point-in-time recovery. If the most recent backup is corrupt or an issue went unnoticed before it was taken, all recovery options are lost.

1. Microsoft SQL Server Documentation: In the documentation for Backup and Restore of SQL Server Databases

maintenance plans are described. A key task is the "Maintenance Cleanup Task

" which "removes files related to maintenance plans

including database backup files... You can configure this task to delete files based on a specified age." This directly supports deleting files based on a retention policy (age).

Source: Microsoft Docs

"Maintenance Cleanup Task". Section: "Options".

2. Oracle Database Documentation: The Oracle Recovery Manager (RMAN) tool uses a configurable retention policy to determine which backups are no longer needed. The CONFIGURE RETENTION POLICY command sets the rules for obsolescence. The DELETE OBSOLETE command then removes backup files that are no longer required to meet this policy.

Source: Oracle Database Backup and Recovery User's Guide

19c. Chapter 10

"Configuring the RMAN Environment: Advanced Topics". Section: "Configuring a Backup Retention Policy".

3. PostgreSQL Documentation: The official documentation discusses strategies for backup and recovery

emphasizing the importance of a planned policy. It notes

"Whatever your backup and recovery plan is

test it... Consider how long you need to retain your backup archives." This highlights that retention duration is a core component of a proper backup strategy.

Source: PostgreSQL 14 Documentation. Chapter 26

"Backup and Restore". Section 26.1

"SQL Dump".

4. University Courseware: In database administration courses

backup and recovery strategies are a core topic. Course materials emphasize creating policies that define backup frequency

type

and retention period to ensure business continuity while managing storage resources effectively.

Source: Cornell University

CS 5320

"Introduction to Database Systems". Lecture notes on "Database Recovery

" which discuss the necessity of policies for managing archival logs and backups.