Execute the rman command "show all;" on the source database and present the output here. It would also be useful to know how much memory, how much CPU is available on the target; We could therefore give you ways to exploit multiple CPU and larger memory structure to get the restore done quicker. Just because the machines are identical hardware-wise doesn't mean they are configured the same. Look at Windows system configuration for number of CPU and memory, and swap space, etc. All of these could impact run time. ----- Original Message ----- From: "Jeffrey Beckstrom" <JBECKSTROM@xxxxxxxxx> To: "oracle-l-freelists" <oracle-l@xxxxxxxxxxxxx>, "Brandon Allen" <Brandon.Allen@xxxxxxxxxxx> Sent: Monday, November 30, 2009 12:51:59 PM GMT -06:00 US/Canada Central Subject: RE: Duplicate function is a lot longer than a backup We have one channel configured. Backups are on disk. Servers are identical. Compression is being used for the backups. Jeffrey Beckstrom Database Administrator Greater Cleveland Regional Transit Authority 1240 W. 6th Street Cleveland, Ohio 44113 >>> "Allen, Brandon" <Brandon.Allen@xxxxxxxxxxx> 11/30/09 1:37 PM >>> A few questions come to mind: Are you backing up to disk or tape? What degree of parallelism (i.e. how many concurrent channels) for both the backup and the restore/duplicate? Is the disk or CPU significantly slower on the target server? Are you using compression? Regards, Brandon Privileged/Confidential Information may be contained in this message or attachments hereto. Please advise immediately if you or your employer do not consent to Internet email for messages of this kind. Opinions, conclusions and other information in this message that do not relate to the official business of this company shall be understood as neither given nor endorsed by it. -- Michael Fontana Sr. Technical Consultant Enkitec M: 214.912.3709 enkitec oracle_certified_partner -- //www.freelists.org/webpage/oracle-l