topic Advise on Backup stratergy as database has numerous nologging tables in Geodatabase Questions https://community.esri.com/t5/geodatabase-questions/advise-on-backup-stratergy-as-database-has/m-p/860115#M5661 <HTML><HEAD></HEAD><BODY><P>We have our main production database running with numerous nologging operations. the current backup and recovery strategy is :hotbackup early sunday morning when there is less activity in the database (less nologging operations) and&nbsp; archive backup twice daily.<BR />since we have so many tables with nologging our test restore and recovery results were not promising,as part of our test we restored hotbackupfiles and did a roll forward using the archive logs though I'm able to recover and open the database..it has number of corrupt blocks as expected.</P><P>I understand the performance gains provided by nologging operations however at the same time we want a robust backup and recovery solutions if need arises.</P><P>It is actually hard to find a time(db used in&nbsp;by end users in diff time zones)&nbsp;when there are nologging operation to take a hotbackup as nologging is not confined to specific set of tables/tablespaces or any ETL or batch jobs.</P><P>I plan to implement RMAN level 0 every sunday and incremental every day.....as mentioned we have difficulty in finding time to run the backup when there are nologging operations.</P><P>Could you please advise on the best approach on how to handle backup and recovery?</P></BODY></HTML> Fri, 18 May 2018 16:48:04 GMT esrionlinerN 2018-05-18T16:48:04Z Advise on Backup stratergy as database has numerous nologging tables https://community.esri.com/t5/geodatabase-questions/advise-on-backup-stratergy-as-database-has/m-p/860115#M5661 <HTML><HEAD></HEAD><BODY><P>We have our main production database running with numerous nologging operations. the current backup and recovery strategy is :hotbackup early sunday morning when there is less activity in the database (less nologging operations) and&nbsp; archive backup twice daily.<BR />since we have so many tables with nologging our test restore and recovery results were not promising,as part of our test we restored hotbackupfiles and did a roll forward using the archive logs though I'm able to recover and open the database..it has number of corrupt blocks as expected.</P><P>I understand the performance gains provided by nologging operations however at the same time we want a robust backup and recovery solutions if need arises.</P><P>It is actually hard to find a time(db used in&nbsp;by end users in diff time zones)&nbsp;when there are nologging operation to take a hotbackup as nologging is not confined to specific set of tables/tablespaces or any ETL or batch jobs.</P><P>I plan to implement RMAN level 0 every sunday and incremental every day.....as mentioned we have difficulty in finding time to run the backup when there are nologging operations.</P><P>Could you please advise on the best approach on how to handle backup and recovery?</P></BODY></HTML> Fri, 18 May 2018 16:48:04 GMT https://community.esri.com/t5/geodatabase-questions/advise-on-backup-stratergy-as-database-has/m-p/860115#M5661 esrionlinerN 2018-05-18T16:48:04Z