This content has been marked as final. Show 40 replies
No, we only have tape backup on tape.
2 days to recover a database is quite a bit ... I assume you tried direct database to database data pump and that it takes longer than 2 days, right?
Are you compressing your tape backups?
I think the tape backup did have compression on EMC level.
Are you using VTL?
What is the size of your database?
Edited by: Valentin Minzatu on Sep 26, 2012 12:35 PM
Size of the database is a little over 1tb.
1 day to restore 1TB sounds a very long time to me. I can backup over network my home computer that has much more storage than that in a matter of hours.
I would look into why is the restore so slow. Maybe you can upload some stats, including RMAN restore script and log, and some details about the physical layout (disk, cpu's, memory)?
we have no control over the storage, no privileges. But I can upload some restore logs.
my question is what is the alternative?
Are you maxed out on the number of channels during restore?
echo "Starting : `date`"
+ echo Starting : Tue Sep 25 15:51:18 CUT 2012
Starting : Tue Sep 25 15:51:18 CUT 2012
rman target / << EOD
#set until time "to_date('25-Sep-11 08:00:00','DD-MON-YYYY HH24:MI:SS')";
allocate channel t1 type 'SBT_TAPE';
allocate channel t2 type 'SBT_TAPE';
allocate channel t3 type 'SBT_TAPE';
allocate channel t4 type 'SBT_TAPE';
Recovery Manager complete.
echo "Ending : `date`"
+ echo Ending : Tue Sep 25 22:58:14 CUT 2012
Ending : Tue Sep 25 22:58:14 CUT 2012
It takes 7 hours not a full day then :)
In theory, if you had a single Gb interface you should be able to transfer 1TB in ~3h (lots of assumptions there). Is that the case? How many CPU's you have on that machine?
well, that is a day to us, we don't work 24 hrs. I currently want to ditch this method of refresh.
any good alternative you can suggest?
You have lots of limitations and my understanding of your environment could be a lot better...
That being said and assuming that your restore is slow due to tape speed, can you not copy the standby over (I assume it is in sync with prod) and change the name?
how to not copy the standby over and not change the name?
That was a question: can you copy the standby database?
I am not sure. I am thinking why cannot we just do a transportable tablespace? then try to figure out a way to switch db to that certain piont of time?