Re: Restore/Duplicate takes a lot longer to restore than backup
From: Howard Latham <howard.latham_at_gmail.com>
Date: Wed, 6 Jan 2010 19:53:51 +0000
Message-ID: <713d96d11001061153n1d3759cfia02ff85033302ada_at_mail.gmail.com>
We have found that the compression causes the restore to take MUCH MUCH MUCH longer. It seems that the decompression algorithm is very slow. WE abandoned compression so we could get a database back quicker - 3 hours instead of 18.
Date: Wed, 6 Jan 2010 19:53:51 +0000
Message-ID: <713d96d11001061153n1d3759cfia02ff85033302ada_at_mail.gmail.com>
We have found that the compression causes the restore to take MUCH MUCH MUCH longer. It seems that the decompression algorithm is very slow. WE abandoned compression so we could get a database back quicker - 3 hours instead of 18.
On 06/01/2010, Jeffrey Beckstrom <JBECKSTROM_at_gcrta.org> wrote:
> We are doing a compressed backup of a 200G database in about 2 hours. When
> we run the duplicate command, we copy the production backup files to the
> local disks of the target server. We then run the RMAN duplicate command
> and it takes over 6 hours. Is it reasonable that a restore/duplicate from a
> compressed backup takes that much longer than the actual backup? Is there
> anything that can be done to speed up the process?
>
>
> Jeffrey Beckstrom
> Database Administrator
> Greater Cleveland Regional Transit Authority
> 1240 W. 6th Street
> Cleveland, Ohio 44113
>
-- Howard A. Latham -- http://www.freelists.org/webpage/oracle-lReceived on Wed Jan 06 2010 - 13:53:51 CST