RE: Monthly RMAN Long Term Backup

Hi Steve,
I understand what you are saying and I brought this up to the powers that be who told me to do this. It is just supposed to be a snapshot to satisfy some security requirement.

Sallie A. Cottingham, OCP
Database Administrator
Comptroller of the Treasury
Technology Solutions
425 Rep. John Lewis Way N. | Nashville, TN 37243 sallie.cottingham_at_cot.tn.gov<mailto:sallie.cottingham_at_cot.tn.gov> | Direct Line 615.401.7962

[A picture containing food Description automatically generated]

From: Steve Harville <steve.harville_at_gmail.com> Sent: Monday, March 8, 2021 6:21 PM
To: ilsuonogiallo_at_gmail.com
Cc: Sallie Cottingham <Sallie.Cottingham_at_cot.tn.gov>; ORACLE-L <oracle-l_at_freelists.org> Subject: Re: Monthly RMAN Long Term Backup

"to be run monthly to get a full backup of the database and keep that backup for a year"

This is a bad policy. A backup is supposed to allow recovery to a point in time with zero data loss. These monthly backups will never be used like backups are meant to be used. They could be dangerous to your database if someone restores them without knowing what they are doing. If there is a justified reason to store snapshots you should just do an export and keep that however long is needed.

On Mon, Mar 8, 2021 at 6:55 PM Andrea Monti <ilsuonogiallo_at_gmail.com<mailto:ilsuonogiallo_at_gmail.com>> wrote: Hi Sallie
Your long term retention backup will contain spfile, control file, and the archivelog needed to make the full backup consistent. The doc says that

You can use BACKUP<https://docs.oracle.com/cd/B28359_01/backup.111/b28273/rcmsynta007.htm#RCMRF107> ... KEEP to create a backup that is both all-inclusive and exempt from the backup retention policy<https://docs.oracle.com/cd/B28359_01/backup.111/b28270/glossary.htm#i432137>. The backup is all-inclusive because every file needed to restore and recover the database is backed up to a single disk or tape location. The KEEP option also specifies that the backup should be exempt from the retention policy either forever or for a specified period of time.

And you can double check with rman list backup command.

Pleae be aware that archival backup can not be used to restore and open resetlogs a db,but can not be used to *duplicate* the database. You can find details, explanation and workaround bere:

https://yawod.wordpress.com/2020/04/09/rman-archival-backup-part-1/#rman_archival_backup

Regards,
A

Il Lun 8 Mar 2021, 22:34 Sallie Cottingham <Sallie.Cottingham_at_cot.tn.gov<mailto:Sallie.Cottingham_at_cot.tn.gov>> ha scritto: Hi –
I currently have a daily full RMAN backup job that runs each evening and one additional job that runs every 2 hours to backup the archive logs. My setup is that the full backup is kept for a recovery window of 14 days and for the archive log files, once they have been backed up twice they are deleted.

I have a new requirement for a new job to be run monthly to get a full backup of the database and keep that backup for a year. I’ve been researching this and found that to do this I can use the ‘keep until time sysdate +365’ to accomplish this. My understanding is that by using the ‘keep until’ parameter RMAN will backup the database as well as any archive logs needed for a consistent backup. And spfile/control file as well?

I’m trying to understand how the archive logs backups work in this situation. When the monthly backup is run and needed archive logs are included in the backup is that counted against the 2 that I normally want to keep? And also could there be a situation where a needed archive log might have already been backed up twice and therefore been deleted? These monthly backups are going to be written to DDBoost at our DR site and so I’m wanting to be double sure that I know everything needed for a restore is included – but also that I haven’t done anything that would upset my normal backup routine.

Any insight would be helpful – Thanks!

Sallie A. Cottingham, OCP
Database Administrator
Comptroller of the Treasury
Technology Solutions
425 Rep. John Lewis Way N. | Nashville, TN 37243 sallie.cottingham_at_cot.tn.gov<mailto:sallie.cottingham_at_cot.tn.gov> | Direct Line 615.401.7962

--
http://www.freelists.org/webpage/oracle-l




image/png attachment: image001.png