Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

All Recent Backups Appear "EXPIRED" through RMAN

1,025 views
Skip to first unread message

sillz

unread,
Oct 16, 2007, 6:34:25 PM10/16/07
to
Hi,

I'm very new to disaster recovery on Oracle. I'm hoping to get some
help recovering our database to a different server using RMAN. We're
doing a disaster recovery drill. The assumption is we have lost our
entire site, and we need to restore the database to a newly built
server that has been set up with the same configuration as production
-- same build, same OS, same Oracle version and patch level, same
partition configuration, etc.

This has been set up in an isolated LAN that has no connection to the
production systems.

We're using Oracle Database Server, Standard Edition version 9.2.0.7.
Windows 2003 SP2. We have created backup sets using autobackup turned
on, archive mode on and Backup Exec as the backup solution. They are
all online backups. We will be updating to 10g early next year, and
it's not an option to do it sooner.

We have created a seed database with the same name as production in
our lab environment. We are at the point where we are ready to
restore our control files. When we run our recovery commands in RMAN,
it cannot locate the autobackups. We force it to search back several
days, but it still cannot locate the autobackup. We even put in last
night's backup from production (updating the control files in the test
lab of course), but the backups cannot be found.

To troubleshoot, I did some listing and crosschecking of the backups
through RMAN on both production and in the lab. In the lab, only the
control files show as EXPIRED. The database backups in the test lab
show as "AVAILABLE," but the control files are also 'EXPIRED'

Both systems are using the exact same control files. I copied them to
the test lab this morning.

I set the DBID in the lab to be the same as prod before mounting the
database.

Here's the output from RMAN in production. I'm really concerned now
because all of the prod backups show as EXPIRED.


RMAN> list backup of controlfile summary;
list backup of controlfile summary;

List of Backups
===============
Key TY LV S Device Type Completion Time #Pieces #Copies Tag
------- -- -- - ----------- --------------- ------- ------- ---
600 B F X SBT_TAPE 05-OCT-07 1 1
605 B F X SBT_TAPE 08-OCT-07 1 1
609 B F X SBT_TAPE 09-OCT-07 1 1
613 B F X SBT_TAPE 10-OCT-07 1 1
618 B F X SBT_TAPE 11-OCT-07 1 1
623 B F X SBT_TAPE 12-OCT-07 1 1
628 B F X SBT_TAPE 15-OCT-07 1 1


RMAN> list backup of database summary;
list backup of database summary;

List of Backups
===============
Key TY LV S Device Type Completion Time #Pieces #Copies Tag
------- -- -- - ----------- --------------- ------- ------- ---
598 B 0 X SBT_TAPE 05-OCT-07 1 1
TAG20071005T200427
603 B 0 X SBT_TAPE 08-OCT-07 1 1
TAG20071008T200352
607 B 0 X SBT_TAPE 09-OCT-07 1 1
TAG20071009T200214
611 B 0 X SBT_TAPE 10-OCT-07 1 1
TAG20071010T200332
616 B 0 X SBT_TAPE 11-OCT-07 1 1
TAG20071011T200429
621 B 0 X SBT_TAPE 12-OCT-07 1 1
TAG20071012T200536
626 B 0 X SBT_TAPE 15-OCT-07 1 1
TAG20071015T200537


RMAN> crosscheck backup of database;
crosscheck backup of database;
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=BE_ioiton6b_1_1 recid=598 stamp=635198667
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=BE_itiu0k98_1_1 recid=603 stamp=635457832
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=BE_j1iu38i6_1_1 recid=607 stamp=635544134
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=BE_j5iu5t0k_1_1 recid=611 stamp=635630613
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=BE_jaiu8hee_1_1 recid=616 stamp=635717070
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=BE_jfiub5sh_1_1 recid=621 stamp=635803537
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=BE_jkiuj30h_1_1 recid=626 stamp=636062737
Crosschecked 7 objects

RMAN> crosscheck backup of controlfile;
crosscheck backup of controlfile;
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=c-11771011-20071005-00 recid=600 stamp=635201185
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=c-11771011-20071008-00 recid=605 stamp=635460079
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=c-11771011-20071009-00 recid=609 stamp=635546291
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=c-11771011-20071010-00 recid=613 stamp=635632821
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=c-11771011-20071011-00 recid=618 stamp=635719117
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=c-11771011-20071012-00 recid=623 stamp=635805984
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=c-11771011-20071015-00 recid=628 stamp=636064774
Crosschecked 7 objects


Does anyone know why all of my recent backups are showing as expired?
These backups were performed on production. I'm running the RMAN
commands both in production and the test lab. In prodcution, RMAN
reports "EXPIRED" for both the control files and the backup.

Here's my show all from RMAN in production:

RMAN> show all;
show all;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F';
# default
CONFIGURE DEVICE TYPE DISK PARALLELISM 1; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; #
default
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO 'D:\ORACLE\ORA92\DATABASE
\SNCFPROD.ORA'; # default

Any thoughts would be really appreciated.

Beth

Jerome Vitalis

unread,
Oct 17, 2007, 3:26:56 AM10/17/07
to
sillz wrote:


> We're using Oracle Database Server, Standard Edition version 9.2.0.7.
> Windows 2003 SP2. We have created backup sets using autobackup turned
> on, archive mode on and Backup Exec as the backup solution.

According to your persistant RMAN configuration, and if you do not
allocate specific tape channels for your backups, we can gather that
Backup Exec is not used directly as a media manager within RMAN. It puts
the backup pieces on tapes afterwards, and it deletes them from disks.
Right?

Then what you observe is normal since the backup pieces aren't at their
original location anymore. Restore them with Backup Exec and run
"crosscheck backup;" once more time.

To prevent such inconsistencies, you can run a "change backup ...
unavailable;" command after Backup Exec deletes the backups from disk.
Then those backups will never expire. Of course, run "change backup ...
available;" after you restore them to disk if you want RMAN to make use of
them.
-----
échangez opinions et commentaires dans les forums de discussion.
http://www.usenetgratuit.com/

sillz

unread,
Oct 17, 2007, 12:03:02 PM10/17/07
to

Thanks Jerome,

I'm not sure what you mean when you say that "BackupExec is not used


directly as a media manager within RMAN."

If I look at the BackupExec job log, here are the RMAN commands -- it
opens a channel for tape:

RUN {
ALLOCATE CHANNEL ch0
TYPE 'SBT_TAPE';
SEND
'BSA_SERVICE_HOST=10.1.1.176,NBBSA_TOTAL_STREAMS=1,NBBSA_JOB_COOKIE={E7A7213E-
A747-4AB9-B162-B7189B5CEB53},NBBSA_DB_DEVICE_NAME=Oracle-Win::\
\servername.mydomain.com\PROD';
BACKUP
INCREMENTAL LEVEL=0
FORMAT 'BE_U'
DATABASE FORCE PLUS ARCHIVELOG FORCE;

RELEASE CHANNEL ch0;
}


We're not backing up to disk and then archiving to tape -- we're
backing up to tape.

We're having problems with BackupExec seeing the server, so we can't
use it to restore right now. We've had a case open with SYmantec for
over a month and thye can't figure it out.

Because we can't use BUE, we've turned to restoring using RMAN.

Any other ideas why all of my backups would be showing as expired?

Beth

sillz

unread,
Oct 17, 2007, 12:12:13 PM10/17/07
to
> 'BSA_SERVICE_HOST=10.1.1.176,NBBSA_TOTAL_STREAMS=1,NBBSA_JOB_COOKIE={E7A721­3E-

> A747-4AB9-B162-B7189B5CEB53},NBBSA_DB_DEVICE_NAME=Oracle-Win::\
> \servername.mydomain.com\PROD';
> BACKUP
> INCREMENTAL LEVEL=0
> FORMAT 'BE_U'
> DATABASE FORCE PLUS ARCHIVELOG FORCE;
>
> RELEASE CHANNEL ch0;
> }
>
> We're not backing up to disk and then archiving to tape -- we're
> backing up to tape.
>
> We're having problems with BackupExec seeing the server, so we can't
> use it to restore right now. We've had a case open with SYmantec for
> over a month and thye can't figure it out.
>
> Because we can't use BUE, we've turned to restoring using RMAN.
>
> Any other ideas why all of my backups would be showing as expired?
>
> Beth- Hide quoted text -
>
> - Show quoted text -

Here's the RMAN output

Recovery Manager: Release 9.2.0.7.0 - Production

Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.


# -----------------------------------------------------------------
# RMAN command section
# -----------------------------------------------------------------

RUN {
ALLOCATE CHANNEL ch0
TYPE 'SBT_TAPE';
SEND

'BSA_SERVICE_HOST=10.10.10.10,NBBSA_TOTAL_STREAMS=1,NBBSA_JOB_COOKIE={E7A7213E-
A747-4AB9-B162-B7189B5CEB53},NBBSA_DB_DEVICE_NAME=Oracle-Win::\
\myserver.mydomain.com\PROD';


BACKUP
INCREMENTAL LEVEL=0
FORMAT 'BE_U'
DATABASE FORCE PLUS ARCHIVELOG FORCE;

RELEASE CHANNEL ch0;
}

connected to target database: PROD (DBID=11771011)

using target database controlfile instead of recovery catalog
allocated channel: ch0
channel ch0: sid=38 devtype=SBT_TAPE
channel ch0: Symantec/BackupExec/1.1.0

sent command to channel: ch0


Starting backup at 16-OCT-07
current log archived
channel ch0: starting archive log backupset
channel ch0: specifying archive log(s) in backup set
input archive log thread=1 sequence=8744 recid=7857 stamp=635990398
input archive log thread=1 sequence=8745 recid=7858 stamp=635990848
input archive log thread=1 sequence=8746 recid=7859 stamp=635991145
input archive log thread=1 sequence=8747 recid=7860 stamp=635991620
input archive log thread=1 sequence=8748 recid=7861 stamp=635992000
input archive log thread=1 sequence=8749 recid=7862 stamp=635992207
input archive log thread=1 sequence=8750 recid=7863 stamp=636012994
input archive log thread=1 sequence=8751 recid=7864 stamp=636015799
input archive log thread=1 sequence=8752 recid=7865 stamp=636015816
input archive log thread=1 sequence=8753 recid=7866 stamp=636015830
input archive log thread=1 sequence=8754 recid=7867 stamp=636015844
input archive log thread=1 sequence=8755 recid=7868 stamp=636020889
input archive log thread=1 sequence=8756 recid=7869 stamp=636021085
input archive log thread=1 sequence=8757 recid=7870 stamp=636021504
input archive log thread=1 sequence=8758 recid=7871 stamp=636022217
input archive log thread=1 sequence=8759 recid=7872 stamp=636022949
input archive log thread=1 sequence=8760 recid=7873 stamp=636026383
input archive log thread=1 sequence=8761 recid=7874 stamp=636028385
input archive log thread=1 sequence=8762 recid=7875 stamp=636029130
input archive log thread=1 sequence=8763 recid=7876 stamp=636030175
input archive log thread=1 sequence=8764 recid=7877 stamp=636030768
input archive log thread=1 sequence=8765 recid=7878 stamp=636033146
input archive log thread=1 sequence=8766 recid=7879 stamp=636040250
input archive log thread=1 sequence=8767 recid=7880 stamp=636040798
input archive log thread=1 sequence=8768 recid=7881 stamp=636042123
input archive log thread=1 sequence=8769 recid=7882 stamp=636047034
input archive log thread=1 sequence=8770 recid=7883 stamp=636051004
input archive log thread=1 sequence=8771 recid=7884 stamp=636062413
input archive log thread=1 sequence=8772 recid=7885 stamp=636064772
input archive log thread=1 sequence=8773 recid=7886 stamp=636076949
input archive log thread=1 sequence=8774 recid=7887 stamp=636077574
input archive log thread=1 sequence=8775 recid=7888 stamp=636078211
input archive log thread=1 sequence=8776 recid=7889 stamp=636078241
input archive log thread=1 sequence=8777 recid=7890 stamp=636078341
input archive log thread=1 sequence=8778 recid=7891 stamp=636078427
input archive log thread=1 sequence=8779 recid=7892 stamp=636078878
input archive log thread=1 sequence=8780 recid=7893 stamp=636079290
input archive log thread=1 sequence=8781 recid=7894 stamp=636099120
input archive log thread=1 sequence=8782 recid=7895 stamp=636100306
input archive log thread=1 sequence=8783 recid=7896 stamp=636102126
input archive log thread=1 sequence=8784 recid=7897 stamp=636102141
input archive log thread=1 sequence=8785 recid=7898 stamp=636102156
input archive log thread=1 sequence=8786 recid=7899 stamp=636105689
input archive log thread=1 sequence=8787 recid=7900 stamp=636111942
input archive log thread=1 sequence=8788 recid=7901 stamp=636126695
input archive log thread=1 sequence=8789 recid=7902 stamp=636130342
input archive log thread=1 sequence=8790 recid=7903 stamp=636133940
input archive log thread=1 sequence=8791 recid=7904 stamp=636148815
channel ch0: starting piece 1 at 16-OCT-07
channel ch0: finished piece 1 at 16-OCT-07
piece handle=BE_jniuln2f_1_1 comment=API Version 2.0,MMS Version
1.1.0.0
channel ch0: backup set complete, elapsed time: 00:02:37
Finished backup at 16-OCT-07

Starting backup at 16-OCT-07
channel ch0: starting incremental level 0 datafile backupset
channel ch0: specifying datafile(s) in backupset
input datafile fno=00010 name=G:\ORACLE\ORADATA\PROD\COMPANY_DATA.DBF
input datafile fno=00012 name=G:\ORACLE\ORADATA\PROD
\APPLICATION_DATA.DBF
input datafile fno=00013 name=G:\ORACLE\ORADATA\PROD
\APPLICATION_DATA02.DBF
input datafile fno=00014 name=G:\ORACLE\ORADATA\PROD
\APPLICATION_DATA03.DBF
input datafile fno=00015 name=G:\ORACLE\ORADATA\PROD
\APPLICATION_DATA04.DBF
input datafile fno=00016 name=G:\ORACLE\ORADATA\PROD
\APPLICATION_DATA05.DBF
input datafile fno=00017 name=G:\ORACLE\ORADATA\PROD
\APPLICATION_DATA06.DBF
input datafile fno=00018 name=G:\ORACLE\ORADATA\PROD
\APPLICATION_DATA07.DBF
input datafile fno=00019 name=G:\ORACLE\ORADATA\PROD
\APPLICATION_DATA08.DBF
input datafile fno=00020 name=G:\ORACLE\ORADATA\PROD
\APPLICATION_DATA09.DBF
input datafile fno=00021 name=G:\ORACLE\ORADATA\PROD
\APPLICATION_DATA10.DBF
input datafile fno=00033 name=G:\ORACLE\ORADATA\PROD
\APPLICATION_DATA11.DBF
input datafile fno=00038 name=G:\ORACLE\ORADATA\PROD
\APPLICATION_DATA12.DBF
input datafile fno=00040 name=G:\ORACLE\ORADATA\PROD
\APPLICATION_DATA13.DBF
input datafile fno=00002 name=G:\ORACLE\ORADATA\PROD\RBS01.ORA
input datafile fno=00031 name=G:\ORACLE\ORADATA\PROD\PLMS_DATA01.DBF
input datafile fno=00022 name=G:\ORACLE\ORADATA\PROD
\APPLICATION_INDEX.DBF
input datafile fno=00023 name=G:\ORACLE\ORADATA\PROD
\APPLICATION_INDEX02.DBF
input datafile fno=00024 name=G:\ORACLE\ORADATA\PROD
\APPLICATION_INDEX03.DBF
input datafile fno=00025 name=G:\ORACLE\ORADATA\PROD
\APPLICATION_INDEX04.DBF
input datafile fno=00026 name=G:\ORACLE\ORADATA\PROD
\APPLICATION_INDEX05.DBF
input datafile fno=00035 name=G:\ORACLE\ORADATA\PROD\DEVELOP_DATA1.DBF
input datafile fno=00036 name=G:\ORACLE\ORADATA\PROD\DEVELOP_DATA2.DBF
input datafile fno=00027 name=G:\ORACLE\ORADATA\PROD
\APPLICATION_INDEX06.DBF
input datafile fno=00039 name=G:\ORACLE\ORADATA\PROD
\APPLICATION_INDEX07.DBF
input datafile fno=00041 name=G:\ORACLE\ORADATA\PROD
\APPLICATION_DATA14.DBF
input datafile fno=00011 name=G:\ORACLE\ORADATA\PROD\COMPANY_INDEX.DBF
input datafile fno=00004 name=G:\ORACLE\ORADATA\PROD\BO_DATA.DBF
input datafile fno=00042 name=G:\ORACLE\ORADATA\PROD
\APPLICATION_DATA15.DBF
input datafile fno=00034 name=G:\ORACLE\ORADATA\PROD\BO.DBF
input datafile fno=00037 name=G:\ORACLE\ORADATA\PROD\MVLOGS01.DBF
input datafile fno=00003 name=G:\ORACLE\ORADATA\PROD\RBS02.ORA
input datafile fno=00043 name=G:\ORACLE\ORADATA\PROD
\APPLICATION_INDEX08.DBF
input datafile fno=00001 name=G:\ORACLE\ORADATA\PROD\SYSTEM01.DBF
input datafile fno=00009 name=G:\ORACLE\ORADATA\PROD\MAT_VIEW02.DBF
input datafile fno=00008 name=G:\ORACLE\ORADATA\PROD\MAT_VIEW01.DBF
input datafile fno=00032 name=G:\ORACLE\ORADATA\PROD\PLMS_INDEX01.DBF
input datafile fno=00007 name=G:\ORACLE\ORADATA\PROD\MAT_INDEX01.DBF
input datafile fno=00005 name=G:\ORACLE\ORADATA\PROD\IMPROM_DATA.DBF
input datafile fno=00006 name=G:\ORACLE\ORADATA\PROD\IMPROM_INDEX.DBF
input datafile fno=00028 name=G:\ORACLE\ORADATA\PROD\STAGING.DBF
input datafile fno=00029 name=G:\ORACLE\ORADATA\PROD\TOOLS01.DBF
input datafile fno=00030 name=G:\ORACLE\ORADATA\PROD\USERS01.DBF
channel ch0: starting piece 1 at 16-OCT-07
channel ch0: finished piece 1 at 16-OCT-07
piece handle=BE_joiuln7c_1_1 comment=API Version 2.0,MMS Version
1.1.0.0
channel ch0: backup set complete, elapsed time: 00:34:35
Finished backup at 16-OCT-07

Starting backup at 16-OCT-07
current log archived
channel ch0: starting archive log backupset
channel ch0: specifying archive log(s) in backup set
input archive log thread=1 sequence=8792 recid=7905 stamp=636151047
channel ch0: starting piece 1 at 16-OCT-07
channel ch0: finished piece 1 at 16-OCT-07
piece handle=BE_jpiulp88_1_1 comment=API Version 2.0,MMS Version
1.1.0.0
channel ch0: backup set complete, elapsed time: 00:00:02
Finished backup at 16-OCT-07

Starting Control File Autobackup at 16-OCT-07
piece handle=c-11771011-20071016-00 comment=API Version 2.0,MMS
Version 1.1.0.0
Finished Control File Autobackup at 16-OCT-07

released channel: ch0

Recovery Manager complete.

Jerome Vitalis

unread,
Oct 17, 2007, 12:51:32 PM10/17/07
to
On Wed, 17 Oct 2007 09:03:02 -0700, sillz wrote:

> I'm not sure what you mean when you say that "BackupExec is not used
> directly as a media manager within RMAN."

Now that you have posted the backup job, it's clear that the RMAN media
manager is actually the BackupExec agent. So you can forget my
assumptions. ;)

It looks like the problem is really specific to BackupExec (software bug
or configuration problem). Maybe you can check with your Backup
administrator in which state the backup pieces are reported on the backup
server.

I've never used the "send" command with Media Managers - the ones I used
worked with parameters specified directly in the allocate/configure
channel command.
A wild guess: the parameters sent to BackupExec during the backup might
not be stored accurately in the repository. If this is the case, you
could try the following job:

RUN {
ALLOCATE CHANNEL ch0
TYPE 'SBT_TAPE';
SEND
'BSA_SERVICE_HOST=10.1.1.176,NBBSA_TOTAL_STREAMS=1,NBBSA_JOB_COOKIE=
{E7A7213E-> A747-4AB9-B162-B7189B5CEB53},NBBSA_DB_DEVICE_NAME=Oracle-Win::
\\servername.mydomain.com\PROD';

crosscheck backup;

RELEASE CHANNEL ch0;
}

and see if it helps finding the pieces.

Jerome

sillz

unread,
Oct 17, 2007, 4:09:23 PM10/17/07
to
On Oct 17, 9:03 am, sillz <beth.sto...@gmail.com> wrote:
> 'BSA_SERVICE_HOST=10.1.1.176,NBBSA_TOTAL_STREAMS=1,NBBSA_JOB_COOKIE={E7A721­3E-

> A747-4AB9-B162-B7189B5CEB53},NBBSA_DB_DEVICE_NAME=Oracle-Win::\
> \servername.mydomain.com\PROD';
> BACKUP
> INCREMENTAL LEVEL=0
> FORMAT 'BE_U'
> DATABASE FORCE PLUS ARCHIVELOG FORCE;
>
> RELEASE CHANNEL ch0;
> }
>
> We're not backing up to disk and then archiving to tape -- we're
> backing up to tape.
>
> We're having problems with BackupExec seeing the server, so we can't
> use it to restore right now. We've had a case open with SYmantec for
> over a month and thye can't figure it out.
>
> Because we can't use BUE, we've turned to restoring using RMAN.
>
> Any other ideas why all of my backups would be showing as expired?
>
> Beth- Hide quoted text -
>
> - Show quoted text -

Also, here's teh RMAN output from BUExec.

Recovery Manager: Release 9.2.0.7.0 - Production

Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.


# -----------------------------------------------------------------
# RMAN command section
# -----------------------------------------------------------------

RUN {


ALLOCATE CHANNEL ch0
TYPE 'SBT_TAPE';
SEND

'BSA_SERVICE_HOST=10.10.10.10,NBBSA_TOTAL_STREAMS=1,NBBSA_JOB_COOKIE={E7A7213E-
A747-4AB9-B162-B7189B5CEB53},NBBSA_DB_DEVICE_NAME=Oracle-Win::\
\myserver.mydomain.com\PROD';


BACKUP
INCREMENTAL LEVEL=0
FORMAT 'BE_U'
DATABASE FORCE PLUS ARCHIVELOG FORCE;

RELEASE CHANNEL ch0;
}

connected to target database: PROD (DBID=11771011)

sillz

unread,
Oct 18, 2007, 12:29:46 PM10/18/07
to
> 'BSA_SERVICE_HOST=10.10.10.10,NBBSA_TOTAL_STREAMS=1,NBBSA_JOB_COOKIE={E7A72­13E-
> input datafile fno=00006 ...
>
> read more »- Hide quoted text -

>
> - Show quoted text -

Thanks Jerome, Sorry about the double post there.

I ran a modified version of the run block you gave me. I had to
allocate a channel for maintenance first. All results come back
expired. This is really perplexing.

I'm wondering now if I should just do my backups from RMAN instead of
Backup Exec.

Here's the output of the commands.

RMAN> allocate channel for maintenance device type SBT_TAPE;

allocated channel: ORA_MAINT_SBT_TAPE_1
channel ORA_MAINT_SBT_TAPE_1: sid=41 devtype=SBT_TAPE
channel ORA_MAINT_SBT_TAPE_1: Symantec/BackupExec/1.1.0

RMAN> RUN {
2> SEND
3>
'BSA_SERVICE_HOST=10.1.1.176,NBBSA_TOTAL_STREAMS=1,NBBSA_JOB_COOKIE=
4> {E7A7213E-> A747-4AB9-B162-
B7189B5CEB53},NBBSA_DB_DEVICE_NAME=Oracle-Win::
5> \\servername.domainname.com\PROD';
6> RELEASE CHANNEL ch0;
7> }


sent command to channel: ORA_MAINT_SBT_TAPE_1

crosschecked backup piece: found to be 'EXPIRED'

backup piece handle=BE_iriu0k2j_1_1 recid=601 stamp=635457620


crosschecked backup piece: found to be 'EXPIRED'

backup piece handle=BE_isiu0k6h_1_1 recid=602 stamp=635457746


crosschecked backup piece: found to be 'EXPIRED'

backup piece handle=BE_iuiu0mfd_1_1 recid=604 stamp=635460078


crosschecked backup piece: found to be 'EXPIRED'

backup piece handle=BE_j0iu38eh_1_1 recid=606 stamp=635544018


crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=BE_j1iu38i6_1_1 recid=607 stamp=635544134
crosschecked backup piece: found to be 'EXPIRED'

backup piece handle=BE_j2iu3alh_1_1 recid=608 stamp=635546290


crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=c-11771011-20071009-00 recid=609 stamp=635546291
crosschecked backup piece: found to be 'EXPIRED'

backup piece handle=BE_j4iu5sqg_1_1 recid=610 stamp=635630417


crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=BE_j5iu5t0k_1_1 recid=611 stamp=635630613
crosschecked backup piece: found to be 'EXPIRED'

backup piece handle=BE_j6iu5v5i_1_1 recid=612 stamp=635632819


crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=c-11771011-20071010-00 recid=613 stamp=635632821
crosschecked backup piece: found to be 'EXPIRED'

backup piece handle=BE_j8iu8h6h_1_1 recid=614 stamp=635716818


crosschecked backup piece: found to be 'EXPIRED'

backup piece handle=BE_j9iu8hap_1_1 recid=615 stamp=635716954


crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=BE_jaiu8hee_1_1 recid=616 stamp=635717070
crosschecked backup piece: found to be 'EXPIRED'

backup piece handle=BE_jbiu8jeb_1_1 recid=617 stamp=635719116


crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=c-11771011-20071011-00 recid=618 stamp=635719117
crosschecked backup piece: found to be 'EXPIRED'

backup piece handle=BE_jdiub5ie_1_1 recid=619 stamp=635803215


crosschecked backup piece: found to be 'EXPIRED'

backup piece handle=BE_jeiub5nk_1_1 recid=620 stamp=635803381


crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=BE_jfiub5sh_1_1 recid=621 stamp=635803537
crosschecked backup piece: found to be 'EXPIRED'

backup piece handle=BE_jgiub88u_1_1 recid=622 stamp=635805983


crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=c-11771011-20071012-00 recid=623 stamp=635805984
crosschecked backup piece: found to be 'EXPIRED'

backup piece handle=BE_jiiuj2me_1_1 recid=624 stamp=636062415


crosschecked backup piece: found to be 'EXPIRED'

backup piece handle=BE_jjiuj2ru_1_1 recid=625 stamp=636062591


crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=BE_jkiuj30h_1_1 recid=626 stamp=636062737

crosschecked backup piece: found to be 'EXPIRED'

backup piece handle=BE_jliuj504_1_1 recid=627 stamp=636064773


crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=c-11771011-20071015-00 recid=628 stamp=636064774

crosschecked backup piece: found to be 'EXPIRED'

backup piece handle=BE_jniuln2f_1_1 recid=629 stamp=636148817


crosschecked backup piece: found to be 'EXPIRED'

backup piece handle=BE_joiuln7c_1_1 recid=630 stamp=636148972


crosschecked backup piece: found to be 'EXPIRED'

backup piece handle=BE_jpiulp88_1_1 recid=631 stamp=636151049


crosschecked backup piece: found to be 'EXPIRED'

backup piece handle=c-11771011-20071016-00 recid=632 stamp=636151050


crosschecked backup piece: found to be 'EXPIRED'

backup piece handle=BE_jriuobee_1_1 recid=633 stamp=636235215


crosschecked backup piece: found to be 'EXPIRED'

backup piece handle=BE_jsiuobi3_1_1 recid=634 stamp=636235331


crosschecked backup piece: found to be 'EXPIRED'

backup piece handle=BE_jtiuodkq_1_1 recid=635 stamp=636237467


crosschecked backup piece: found to be 'EXPIRED'

backup piece handle=c-11771011-20071017-00 recid=636 stamp=636237469
Crosschecked 34 objects

Jerome Vitalis

unread,
Oct 18, 2007, 4:06:21 PM10/18/07
to
On Thu, 18 Oct 2007 09:29:46 -0700, sillz wrote:

> I ran a modified version of the run block you gave me. I had to
> allocate a channel for maintenance first. All results come back
> expired. This is really perplexing.
>
> I'm wondering now if I should just do my backups from RMAN instead of
> Backup Exec.
>
> Here's the output of the commands.

> ...

This really seems to be a problem with the BackupExec agent or its
configuration. I cannot try helping you any further since I don't have
any knowledge on this product.

I think you're right: you should temporarily take the next RMAN backups
to disks (and then to tapes) since you're not sure of the reliability of
the BackupExec agent.
Meanwhile I hope the BackupExec support service can sort this mess out
for you.

Jerome

sillz

unread,
Oct 29, 2007, 2:01:26 PM10/29/07
to
On Oct 18, 1:06 pm, Jerome Vitalis

Jerome was correct. This ended up being an ugly problem with Backup
Exec. The first attempt to restore an Oracle 9i database to a new
host works some of the time. 8 out of 10 of our tests failed on the
first try. Subsequent tries on at least 2 of our Oracle on Windows
systems fail because of some bug in BUExec. The database is not
accessible through the BUE GUI. When we attempted to use RMAN, the
problem is that all backups immediately expire.

When we remove BUE from the the core of the process, it works fine.

We ended up doing the following:

Native backups to disk using RMAN.
Archiving to tape the backup set files, autobackup of controlfile,
init.ora, sqlnet.ora and listener.or. We used a flat file backup in
BUE for this.
Recover all of the flat files and backup set files to the new host
using BUE.
Restoring using Native RMAN.

I'd be curious to know if anyone out there using BUE 11g and Oracle on
Windows is having the same problem.

Symantec re-created the issue in their lab, but we haven't heard from
them in over a week. A colleague also replicated the issue in his
lab.

If you're using BUExec 11g, Oracle and Windows, then I'd check and
double-check your restore procedures.

Hopefully you don't have the same problem we had.

Beth

sillz

unread,
Oct 29, 2007, 2:04:37 PM10/29/07
to
On Oct 18, 1:06 pm, Jerome Vitalis
<vitalismanN05...@gmail.com.invalid> wrote:

Sorry, that's BUE version 11D not G.

sillz

unread,
Dec 6, 2007, 1:13:07 PM12/6/07
to
To anyone who is interested: Symantec acknowledged this is a bug in
version 11D. The problem is that BUE is recognizing case sensitivity
in the Oracle database name on Windows. If the database was created
in upper case, then BUE will add that information to the catalog in
upper case. If you then create a brand new Oracle database with the
same name in lower case and try to restore the original database, BUE
will recognize this as a new server. I cannot associate the catalog
items for the original server with this database because of the
difference in case.

The fix in a restore situation is to create your Oracle 'seed'
database using the same case as the original.

Symantec is working on a patch for this and will include it in their
next release.

0 new messages