For us staging has performed exceptionally well, our backup window has shrunk considerably, simply because backing up to disk is fast. We use a product call Ataboy, produced by a company called NEXSAN for our disk storage It has 2.5 Tb of storage. They also have one called the ATABeast, 12Tb. I installed a second HBA in the backup server, unders windoze, added a new drive, created a directory called backup, then under legato created devices/volumes that use that storage. Created disk pools, pointed groups to use the disk pools as opposed to tape pools. Then create stages, that monitor the disk volumes and send staged data to the tape pool based on the stage policies. Backups work exaclty the same, issue a save to a group and it puts in on disk. The only problem sometimes is, the when a stage is happening (disk to tape) it locks the disk volume so you can't access it. I resolved this by creating smaller disk volumes (200 GB) as a opposed to larger volumes (>500 Gb). Also the high water mark doesn't work very well, but then again I am still on legate 6.1.x. I am sure some of these issues have been resolved under version 7. Restores are performed exactly the same, whether it is a disk volume or a tape volume, it is a volume, simple. Obviously tape is slower to recover from, and it may not be readily available. Darren -----Original Message----- From: Fuad Arshad [mailto:fuadar@xxxxxxxxx] Sent: Friday, June 11, 2004 9:18 AM To: oracle-l@xxxxxxxxxxxxx Subject: RE: Rman/Legato/Architecture interesting , we are actually thinking about using this. what are your thoughts . how are restores performed if data is moved to tape. "Browett, Darren" <dbrowett@xxxxxxxxxxxx> wrote: Legato has a feature called staging, which we are using. In short, we backup up to disk, then based on age of the files, 2 days, 5 days, 7days, the savesets are moved to tape. Works great. Darren -----Original Message----- From: Stephen.Lee@xxxxxxxx [mailto:Stephen.Lee@xxxxxxxx] Sent: Thursday, June 10, 2004 9:47 AM To: oracle-l@xxxxxxxxxxxxx Subject: RE: Rman/Legato/Architecture I'm not a Legato expert but ... I think a big part of the problem is that during backup, rman can shovel the files into Networker in parallel, but when it is time to restore the files, the parallelism (or most of it) goes away. We have started keeping a copy of the backup on disk as well as on tape. We have just started this for the same reason you have experienced, so we are still experimenting. Our current strategy -- subject to change if somebody comes along with something better -- is to backup to disk; then run a script that uses mminfo to see what is on disk that isn't on tape; then use the save command to send the new files to tape; then delete yesterday's backup from disk. In our case, we have about 1.8 Tb allocated for this. So yeah, we're talking about a wee bit of disk space here. ---------------------------------------------------------------- Please see the official ORACLE-L FAQ: http://www.orafaq.com ---------------------------------------------------------------- To unsubscribe send email to: oracle-l-request@xxxxxxxxxxxxx put 'unsubscribe' in the subject line. -- Archives are at //www.freelists.org/archives/oracle-l/ FAQ is at //www.freelists.org/help/fom-serve/cache/1.html ----------------------------------------------------------------- ---------------------------------------------------------------- Please see the official ORACLE-L FAQ: http://www.orafaq.com ---------------------------------------------------------------- To unsubscribe send email to: oracle-l-request@xxxxxxxxxxxxx put 'unsubscribe' in the subject line. -- Archives are at //www.freelists.org/archives/oracle-l/ FAQ is at //www.freelists.org/help/fom-serve/cache/1.html -----------------------------------------------------------------