I need help tuning our rman backups with 11g
DBAsupport.com Forums - Powered by vBulletin
Results 1 to 4 of 4

Thread: I need help tuning our rman backups with 11g

  1. #1
    Join Date
    Nov 2000
    Location
    Pittsburgh, PA
    Posts
    3,997

    I need help tuning our rman backups with 11g

    We have almost 70 databases spread across over 40 servers, running 9.2.0.8, 10.2.0.4 and 11.2.0.7. We are in the process of upgrading our Oracle Financials databases from 9.2.0.8 to 11.1.0.7. Our servers are a mixture of Sun Solaris 5.8, 5.9, 5.10, Red Hat Linux 4 and 5 and one or two HPUX boxes. We are NFS mounting volumes from one of two storage servers that have 25TB of storage each.

    We are running full RMAN backups of the database using a single channel to the NFS mount. Under 9i the best case backup was almost 600GB to the NFS mount in 3 hours 40 minutes. But the average backup is a little over 6 hours. Once we move a database to 11g, the backup can be up to 17 hours. We are not using io slaves and we do have asynchronous io turned on by default.

    I am looking for ideas on what I can do to both identify the bottleneck and shorten the amount of time the backup takes. We may at some point look at doin incremental backups, but we should be able to get a full backup in less than 7 hours, especially since we are using compression on the 11g backups which should reduce the amount of io traveling to the NFS mount.

    Thanks in advance, Brian
    this space intentionally left blank

  2. #2
    Join Date
    Jul 2002
    Location
    Lake Worth, FL
    Posts
    1,459

    Cool 11g backups

    For the 11g backups use a) Compressed backup b) at least 4 channels.

    For 9i and 10g use a) At least 4 channels, b) Block tracking.
    "The person who says it cannot be done should not interrupt the person doing it." --Chinese Proverb

  3. #3
    Join Date
    Nov 2000
    Location
    Pittsburgh, PA
    Posts
    3,997
    Here is the command we use. This is a part of our rman backup script. We also have a config script that sets parallelism to 1. One of the other DBA's had better luck with Parallelism set to 4, large_pool_size =256M, dbwr_io_slaves set = 4.

    Code:
    # storage server was used to store the backup.
    run {
       set command id to '${SERVERNAME}';
       configure channel device type disk format '${BACKUPDIR}/%d_%Y_%M_%D_%t_%s_%c_%p';
       backup ${COMPRESSION} database
       tag '${CURR_TIME}'
       format '${BACKUPDIR}/%d_%Y_%M_%D_%t_%s_%c_%p'
       include current controlfile
       plus archivelog;
    
       configure Controlfile autobackup off;
    }
    this space intentionally left blank

  4. #4
    Join Date
    Jul 2002
    Location
    Lake Worth, FL
    Posts
    1,459

    Thumbs up Parallelism 4 + block-tracking

    The 9i and 10g average backup time for ~600G/900G seems within range for a 4 cpu server using NFS.
    Try Full backup + incremental level 0 using "block-tracking".
    PS: Compression in 10g only increases the backup time.

    Code:
    ALTER DATABASE ENABLE BLOCK CHANGE TRACKING 
      USING FILE '/mydir/rman_change_track.f' REUSE;
    For 11g the way to go is compressed backups, our 6-8 hour 10g backups were reduced to two hours after the migration to 11g for ~900G database.

    "The person who says it cannot be done should not interrupt the person doing it." --Chinese Proverb

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  



Click Here to Expand Forum to Full Width