4 Replies Latest reply: Apr 1, 2013 3:29 AM by mseberg RSS

    RMAN backup and SGA

    Andy.....!
      Hi all,

      OS : RHEL 5.7 64bit
      DB : 11.2.0.2. SE 64bit

      On Oracle docs I read that for RMAN backup and restoration large pool is used.
      Is there any view from which we can check that RMAN processes uses memory from shared pool or large pool?

      AND how we can come to know that how much amount of memory is used for RMAN backups?

      I have one more confusion with backup_tape_io_slaves paramater..

      This parameter is must be true if we are using duplexed backup but apart from from that is there any use of this parameter?



      Regards,
      Andy.

      Edited by: Andy.....! on Mar 30, 2013 4:29 PM

      Edited by: Andy.....! on Mar 30, 2013 4:34 PM
        • 1. Re: RMAN backup and SGA
          mseberg
          Hello;

          The BACKUP_TAPE_IO_SLAVES parameter is used to keep tape continuously moving by simulating asynchronous tape I/O.

          Transfer rate can also be seen at Oracle level with V$BACKUP_SYNC_IO and V$BACKUP_ASYNC_IO.
           SET lines 200
           col filename FOR a40
           SET pages 50
           
           SELECT
               a.device_type, 
               a.TYPE, 
               s.status, 
               s.mbytes_processed AS "Total MB", 
               a.filename, 
               ROUND(a.bytes/(1024*1024)) AS "Size MB", 
               TO_CHAR(a.open_time,'dd-mon-yyyy hh24:mi:ss') AS open_time,
               ROUND(a.elapsed_time/100) AS "Time (s)", 
               ROUND(a.elapsed_time/100) AS "Elapsed (s)", 
               ROUND(a.effective_bytes_per_second/(1024*1024)) AS "MB/s"
             FROM 
               v$backup_async_io a, v$rman_status s
             WHERE 
               a.rman_status_recid = s.recid
             ORDER BY 
               a.use_count;
          I don't believe there is any other used of this parameter.

          You can try looking at these to get memory information :
          select * from v$shared_pool_advice;
          select * from v$sga_target_advice;
          As far as memory goes the simple thing is to use ASMM so Oracle will automatically size and adjust memory for you.

          Best Regards

          mseberg
          • 2. Re: RMAN backup and SGA
            Dude!
            You might want to keep the following in mind:

            The SGA large pool is only used if you set DBWR_IO_SLAVES for disk and/or BACKUP_TAPE_IO_SLAVES for tape buffering. If LARGE_POOL_SIZE is not set it will get memory from the shared pool. If the server cannot get enough memory, it will allocate buffers from PGA and use synchronous I/O and you will see a message in the alert log.
            • 3. Re: RMAN backup and SGA
              Andy.....!
              Hi mseberg/Dude,

              Thanks for reply.
              :)


              I am using ASSM.
              Right now I am taking RMAN backup on tape as well as on Disk also..
              I have checked both the views that is V$BACKUP_SYNC_IO and V$BACKUP_ASYNC_IO.

              In V$BACKUP_SYNC_IO it is showing TAPE backup info and in V$BACKUP_ASYNC_IO it is showing Disk backup info..

              Parameter backup_tape_io_slaves set to false and dbwr_io_slaves value is 0..

              So what is advisable for my system?
              Should I set parameter backup_tape_io_slaves to true?
              AND
              What is difference between ASYNC and SYNC?


              Please suggest..

              Regards,
              Andy.
              • 4. Re: RMAN backup and SGA
                mseberg
                Hello;

                Asynchronous is advantageous because a server process can perform more than 1 Input/Output operation at a time. So you want to use V$BACKUP_ASYNC_IO since Red Hat supports asynchronous.

                On backup_tape_io_slaves you can test it on your system and see if your times improve for tape. They either do or don't, EFFECTIVE_BYTES_PER_SECONDS (V$BACKUP_ASYNC_IO) should be at a rate close to the capacity of your backup device.

                Since you are already using ASSM you don't have to do much. You can try to tune this for hours and hours, but mostly likely its a waste of time.

                Worth noting V$BACKUP_ASYNC_IO only holds information since your last instance restart. Same with the other but you are asynchronous so there should be no need to use it.

                Best Regards

                mseberg