RMAN standardization

[suhas_k_p]

Hi Tim,

We are standardizing the RMAN environment. The requirement is to gather detailed information on RMAN scripts which helps to accomplish this tasks.
The requirement is to thoroughly go through the scripts which are already in place and enhance the scripts and to come up with a fool proof action plan.
This is to overcome all the odds if we are hit by a major issue related to backup failures or restores.
I am new bee to RMAN with limited basic knowledge on RMAN. Please kindly help me with the above factors or as much information on RMAN which can be useful to fulfill the requirement.
Will be eagerly waiting for your response. Please kindly do the needful.

Regards,
Suhas

[Tim...]

Hi.

If there were an easy way to define the "perfect" backup and recovery solution don't you think it would be the default option in Oracle?

The reality is every database has potentially different B&R requirements, which means standardizing on one method throughout your company can be a gross oversimplification and therefore compromise your recovery. That's not to say you shouldn't. I just mean you have to know the consequences.

If you want something simple and consistent, my starting point would be:

- All databases in archivelog mode.

- All databases use block change tracking.
http://www.oracle-base.com/articles/10g ... al_backups

- All databases use incrementally updated backups.
http://www.oracle-base.com/articles/10g ... ed_backups

- Pick a recovery window (like 7 days) and apply the incremental backups to the image copies keeping them at the right age to allow for your recovery window (like 7 days old).

- After the first image copy backup, you will never need to do a full backup again. Just do incrementals and apply them to the backup image copies.

That is about as simple as you can make things, while keeping the backups efficient and quick.

Like I said, standardizing can be an issue, so don't follow anyones advice without using your brain!

Cheers

Tim...

[suhas_k_p]

Hi Tim,
Thank you so much for getting me to a good start. I agree the potentiality and the requirement varies across each database. I think i was not clear about the requirement.
I observed that the status is ENABLED for v$block_change_tracking. The incremental backup is taking place and the recovery window is set.
In order to thoroughly screen the scripts which are already in place, as there are lot of parameters and options that are used in RMAN.I think RMAN is a very complicated tool and to be used very carefully.
I want to make sure this would not hamper the database performance or has any adverse affect on the database.

Do we have any check lists to be followed for a smoother and successful backup, recovery and restore. So that i can make sure that every thing is in place now and we can recover from a situation.

Regards,
Suhas

[Tim...]

Hi.

If you are using block change tracking and incremental backups, this is about as efficient as you are going to get. The only other thing to consider is the level of parallelism. The higher the degree of parallelism, the fast it will go, but the more server resource it will take.

Cheers

Tim...

[suhas_k_p]

Thanks a ton Tim..If i come across anything will reply to this thread. Thank you so much.

Regards,
Suhas

[Tim...]