On Tue, May 25, 2010 at 4:54 PM, Dean
<dean.deano AT gmail DOT com> wrote:
Are you sure RMAN actually knows about the tape an image is on? If it does, that is just silly. It should just ask for a backupid, then NBU will give it the correct tape, regardless of whether it's a duped or vault copy or whatever. I've always been sure that that's the way it worked (Although, I'm not a DBA and don't know that much about RMAN).
I think you're right, it just keeps the Media ID.
It's been a few months since I have looked closely at it.
Regarding vaulted tapes: RMAN will not know that a tape has been vaulted,
so it will have the wrong media ID for requesting the tape.
If the tapes are restored into the NBU catalog, RMAN will then ask for the
correct backup pieces by name.
This not an issue with RMAN, as the API has that capability, at least
according to the docs.
It just has not been implemented by Veritas.
This would bear further investigation, as that situation may have changed
since I last looked into it.
Does RMAN also track disk STUs? I know in our environment, we write all our Oracle archive log backups to a DSSU, then they get moved out to tape and deleted from the DSSU within a day or so. We restore regularly (to development), and it always works fine, regardless of whether the archive log backups are still on disk or have been moved to tape. Does that mean RMAN is aware of the destage process? I highly doubt it.
There is a way for RMAN in later version to track backups that are staged to disk and
then backed up on to tape.
I have never used it, and don't know any details about it.
