Hi!
customer has this big Oracke DB (50TB). Intellisnap is not an options now. weekly tape out. disk storage is a HSX.
Any specific recommendation for this scenario?
Incremental forever? synthetic fulls? any other thoughts?
Regards,
Pedro
Solved
40TB Oracle DB backup strategy / best practice
+12- Explorer
Best answer by Darwin Allens
- Hello Pedro,
We can assist with the tweaks, for that we need at least 2 full backup run on DB.
And CV logs for analysis which will help us understand how environment is behaving and what values can be tweaked
BOL @ https://documentation.commvault.com/2022e/expert/20811_best_practices_for_oracle.html - RMAN compression
The BFS value
The Commvault compression option
| Parameter | Recommendation |
|---|---|
| LARGE_POOL_SIZE | Set the LARGE_POOL_SIZE parameter by using the following formula: LARGE_POOL_SIZE=number of allocated channels * (16 MB + ( 4 * size of tape buffer)) If you do not set the LARGE_POOL_SIZE parameter, the Oracle software allocates the buffer from the shared pool. |
| BACKUP_TAPE_IO_SLAVES | Set the BACKUP_TAPE_IO_SLAVES parameter to true so that RMAN uses the System Global Area (SGA) for the buffer allocation, which prevents resource contention. |
- Vaulter
Hi Pedro,
We have below options
- Run everyday incremental ( Off business Hrs.) With oracle block track change enable
- Weekly Full ( When less load on DB )
- Archive logs as per business requirement
If the backups are moved to tape weekly depending on what is retention is set . We can implement selective online full to keep the backups intact for recovery
BOL @
https://documentation.commvault.com/2022e/expert/11727_selective_online_full_backups.html
A selective online full operation includes the data and archive logs. Any log job you start within the time frame of the selective online full operation is linked to the selective online full job. These logs and the selective online full are then considered as one entity within the software. They are copied to synchronous and selective copies together during auxiliary copy operations and are aged together. If any part of the selective online full is missing from a copy, the full backup is not considered as a valid full and is not counted as a cycle during data aging.
Let us know if we answered your question
+12- Explorer
Hi Pedro,
We have below options
- Run everyday incremental ( Off business Hrs.) With oracle block track change enable
- Weekly Full ( When less load on DB )
- Archive logs as per business requirement
If the backups are moved to tape weekly depending on what is retention is set . We can implement selective online full to keep the backups intact for recovery
BOL @
https://documentation.commvault.com/2022e/expert/11727_selective_online_full_backups.html
A selective online full operation includes the data and archive logs. Any log job you start within the time frame of the selective online full operation is linked to the selective online full job. These logs and the selective online full are then considered as one entity within the software. They are copied to synchronous and selective copies together during auxiliary copy operations and are aged together. If any part of the selective online full is missing from a copy, the full backup is not considered as a valid full and is not counted as a cycle during data aging.
Let us know if we answered your question
Hello Darwin,
Thanks for the reply.
I was thinking more of some specific recommendations. The ones that you listed are kind of what we already do for the majority of workloads.
Since the DB is big, backup windows sometimes is an issue. So I was wondering if there were any tweaks and tips for Oracle specificaly.
Regards,
Pedro
- Vaulter
- Answer
- Hello Pedro,
We can assist with the tweaks, for that we need at least 2 full backup run on DB.
And CV logs for analysis which will help us understand how environment is behaving and what values can be tweaked
BOL @ https://documentation.commvault.com/2022e/expert/20811_best_practices_for_oracle.html - RMAN compression
The BFS value
The Commvault compression option
| Parameter | Recommendation |
|---|---|
| LARGE_POOL_SIZE | Set the LARGE_POOL_SIZE parameter by using the following formula: LARGE_POOL_SIZE=number of allocated channels * (16 MB + ( 4 * size of tape buffer)) If you do not set the LARGE_POOL_SIZE parameter, the Oracle software allocates the buffer from the shared pool. |
| BACKUP_TAPE_IO_SLAVES | Set the BACKUP_TAPE_IO_SLAVES parameter to true so that RMAN uses the System Global Area (SGA) for the buffer allocation, which prevents resource contention. |
Readiverse Academy Certifications
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.