000016350 - How to: Manually clean up backups on an RSA Data Protection Manager 3.5 appliance

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000016350
Applies ToRSA Data Protection Manager 3.5 hardware appliance
RSA Data Protection Manager 3.5 virtual appliance
IssueManually clean up backups on a Data Protection Manager 3.5 appliance.
Backups are not being purged according to the specified retention period.
The backup destination is full.
ResolutionTo manually force Oracle to clean up old backups, do the following:
su - oracle

rman target /

catalog start with '/opt/rsa/setup/sh/backup/mount' noprompt;

crosscheck backup;

crosscheck backup of archivelog all;

delete backup of archivelog all completed before 'sysdate-5';

@/opt/rsa/setup/sql/backup_cleanup.sql

Note: You may need to run the catalog command multiple times until no new backup files are found.
NotesIf you run into corrupted backups that cannot be cataloged and deleted by RMAN, you can use the following steps to clean them up:
su - oracle

rman target /

spool log to '/opt/oracle/catalog.txt';

catalog start with '/opt/rsa/setup/sh/backup/mount' noprompt;

spool log off;

exit

exit

cd /opt/oracle

grep -B1 "RMAN-07517: Reason: The file header is corrupted" catalog.txt | grep -v "RMAN-07517" | awk '{print "rm -f " $3}' > /tmp/rm.sh

sh /tmp/rm.sh
Legacy Article IDa67878

Attachments

    Outcomes