RE: Restore/Duplicate takes a lot longer to restore than backup
Date: Wed, 6 Jan 2010 13:40:28 -0600
Well, a restore/duplicate recreates the datafiles (and their sizes) so a big component of the time required is writing the new datafiles. So, lets say you have multiple datafiles that are several gigabytes in size, they take a bit of time to write out. In a backup, you're only reading blocks of data out of datafiles and backing up those blocks. Right?
Sr. Oracle DBA
Ingram Barge Company
Nashville, TN 37205
CONFIDENTIALITY NOTICE: This e-mail and any attachments are confidential and may also be privileged. If you are not the named recipient, please notify the sender immediately and delete the contents of this message without disclosing the contents to anyone, using them for any purpose, or storing or copying the information on any medium.
From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Jeffrey Beckstrom
Sent: Wednesday, January 06, 2010 1:34 PM
To: oracle-l-freelists; oracle-db-l
Subject: Restore/Duplicate takes a lot longer to restore than backup
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?
Greater Cleveland Regional Transit Authority 1240 W. 6th Street
Cleveland, Ohio 44113