This content has been marked as final. Show 8 replies
Hello;1 person found this helpful
Would consider something like this :
Sunday Level 0
Monday Incremental 1
Tuesday Incremental 1
Wednesday Cumulative Incremental
Thursday Incremental 1
Friday Incremental 1
Saturday Incremental 1
You have do a Level 0 every now and then because the Incremental 1's are worthless without it. You could go every other weekend if you had to, but I would avoid if possible.
The other option is Data Guard and off load the backup to the Standby.
Hello,1 person found this helpful
No matter what the database size is, backing it up is prioritized. Only thing that can help out is carrying out the L0 backup when the load is less (during business off hours). You can take L0 backup on Sundays and L1 backups on the remaining days.
1 person found this helpful
Now, in an situation where DB is in use 24 * 7 and size in few TB’s then how to plan for backup’s. I mean every weekend level 0 won’t be possibleYou can use rman feature to roll forward image copies. In this case you need to perform level 0 database backup only once.
Where there are good number of users or where there is business lose due to slow performance. What would be the RMAN backup Strategy
In which case you only have one copy of the backup or all your eggs in one basket as they say.
does a tablespace level bacup depends upon a level 0 backup ?
I mean, if i take a tablepsace level backup on Monday and on tuesday if i have to recover that tablespace, will it be possible to restore that tablespace from Monday's backup and apply archives generated till now for that particular tablespace ?
If you are talking about tablespace point in time recovery beware you cannot recover from a dropped tablespace.
TSPITR does not depend upon a full but has several limits.
You want to recover dropped tablespaces. In fact, RMAN can perform TSPITR on dropped tablespaces even when a recovery catalog is not used.
This is starting to show some age, but worth a look :
You may have already seen this one : ( Backing Up and Recovering VLDBs )
Edited by: mseberg on Feb 6, 2013 1:52 PM
Edited by: mseberg on Feb 6, 2013 1:58 PM
1 person found this helpful
and apply archives generated till now for that particular tablespace ?As you are doing "complete" recovery to the current point in time .... yes you can use such tablespace backups.
In fact, tablespace backups is also a strategy when dealing with large databases.
Say you have 5 tablespaces.
Each week day you run a separate Tablespace backup.
On Sunday, if you can, you run a full database backup. If you do not have time for full database backups on Sunday, you stick to Tablespace backups such that the gap between two backups of the tablespace is not very large (e.g. a week).
Of course, you must consider the ArchiveLogs and ensure that you have multiple (separate Tapes) backups of ArchiveLogs (you don't want a tape error on restore of archivelogs to prevent you from recovering a tablespace !).
Hemant K Chitale
In which case you only have one copy of the backup or all your eggs in one basket as they say.No. You can have many levels 0 updatable backups.