brbackup + oracle + ASM to disk

[Former Member]

Good morning people,

after struggling for some hours with this, I think that I'm missing something while setting up backup through brbackup for a database stored in ASM.

Normally for RAC/ASM databases I rely on plain RMAN, but this time the customer wants to use brbackup to track backups from SAP.

The landscape is as follows:

- RDBMS + SAP server running on RHEL 6.5

- Oracle 11.2.0.4 latest patches

- Brtools 7.40 patch 6

- Database stored in ASM

Whenever I try to run a backup to disk as I would do with a database stored on a regular filesystem I get the following message:

$> brbackup -u / -p initDEVclean.sap -d disk -t online -m all
BR0051I BRBACKUP 7.40 (6)
BR0055I Start of database backup: beovhugt.and 2014-09-26 08:46:31
BR0484I BRBACKUP log file: /oracle/DEV/sapbackup/beovhugt.and
BR0477I Oracle pfile /oracle/DEV/sapprof/initDEV.ora created from spfile /oracle/DEV/112/dbs/spfileDEV.ora
BR1805I Oracle spfile /oracle/DEV/sapprof/spfileDEV.ora created from pfile /oracle/DEV/sapprof/initDEV.ora

BR0280I BRBACKUP time stamp: 2014-09-26 08:46:32
BR0319I Control file copy created: /oracle/DEV/sapbackup/cntrlDEV.dbf 20267008

BR2011E Only RMAN backups supported for ASM database files

BR0056I End of database backup: beovhugt.and 2014-09-26 08:46:32
BR0280I BRBACKUP time stamp: 2014-09-26 08:46:32
BR0054I BRBACKUP terminated with errors

And it only allows me to run a backup through brbackup if it uses rman_disk or rman_stage , which, by design, only backup to tape through the SBT library provided by SAP (already installed as stated in note 142635)

I already tried using both of the following parameter sets in initDEVclean.sap profile file:

backup_dev_type = rman_util | rman_disk | rman_stage

for backup types rman_disk or rman stage

and

backup_dev_type = disk
disk_copy_cmd = rman | rman_set

for backup type disk (which fails with the above error message)

Has anybody managed to perform a simple RMAN backup to local disk, using brbackup, in an ASM stored database?

many thanks

Jordi

[tomislav_bobanovic · Accepted solution]

Hi Jordi,

please read SAP note 1598594 for parameters which must be set in your initSID.sap profile regarding ASM.

Additional parameters I used were:

backup_dev_type = rman_disk

compress = no

tape_copy_cmd = rman

disk_copy_cmd = rman_set

rman_channels = 12

rman_filesperset = 5

asm_root_dir = ASM

_rem_sql_call = yes

_remote_exec = ssh

_remote_copy = scp

Command I use is:

brbackup -p init<SID>.sap -d disk -t online -m full -k yes -e 12 -o dist,time -l E -u /

Br

Tomislav

[Former Member · Accepted solution]

Hello there,

I did follow the note 1598594 and note 1627541, and actually the configuration was ok for the asm_* parameters, the issue was with the line:

backup_dev_type = disk
disk_copy_cmd = rman | rman_set

Checking with a colleague here at $WORK we managed to make it work with

backup_dev_type = disk
disk_copy_cmd = rman

and then it did work flawlessly.

Thanks for your answer!

[Former Member · Accepted solution]

hello,

I m using RMAN and brtools into exadata, and work fine.

do you using with version brtools ? and wich Backup Media ? disk .. netbackup TSM ??

Thanks

Sandro Lobo