Thanks, Murray. We've come to the conclusion that we'll let someone else
debug util_file_online and go with util_file. We started the other way
because our online redo log files were too small - but they've been
re-sized for our 'go-live'. We're expecting to have 120 GB of SAP
database in a year - right now it's 62 GB.

TomK

>----------
>From:  Nicholas, Murray, Haltek/AU[SMTP:MurrayNi AT HALTEK.COM DOT AU]
>Sent:  Tuesday, December 23, 1997 7:42 PM
>To:    ADSM-L AT VM.MARIST DOT EDU
>Subject:       Re: SAP/R3 online backup with backint & ADSM
>
>Tom,
>
>I happily used backint for ADSM on Win-NT to make online and offline
>backups, archive the redo logs and restore the same using SAPDBA to
>recover a database four days into an online upgrade.  All worked
>without a hitch.
>
>However, I note that you said "type=util_file_online" not
>"type=util_file".  When I last checked I found that this feature
>worked nicely for the database backup but took nearly 30 minutes to
>back up the seven little control/admin files needed to form a complete
>backup set for SAP.  ADSM/backint support said they did not officially
>support the "_online" extension.  Removing the extension allowed ADSM
>to back up those seven files in about one minute.
>
>The difference between the two is in when brbackup puts the
>tablespaces into backup mode: with "_online" specified, each
>tablespace is put into backup mode just before it is backed up and
>comes out of backup mode when the backup is complete; with
>"type=util_file", all tablespaces to be backed up are put in backup
>mode before starting to back up the first and they all stay in backup
>mode until the last one is backed up.  In either case you can run
>brbackup -t online.
>
>If you are getting peculiar results (and not just a DBA misreading the
>one letter differences as suggested by another responder) I would
>suggest you try with "type=util_file" and run a "brbackup -t online"
>to see if the problem goes away.
>
>Murray Nicholas
>IT Systems Consultant
>Galeforce Information Services Pty Ltd
>email:  murray AT galeforce.bu.aust DOT com
>
>----------
>>----------
>>From:  Kauffman, Tom[SMTP:KauffmanT AT NIBCO DOT COM]
>>Reply To:      ADSM: Dist Stor Manager
>>Sent:  Tuesday, December 23, 1997 6:45 AM
>>To:    ADSM-L AT VM.MARIST DOT EDU
>>Subject:       SAP/R3 online backup with backint & ADSM
>>
>>Our DBA looked at the log file generated by BRBackup for an on-line
>>backup and got quite nervous -- sveral tablespaces had been switched
>>into and out of backup mode more than once. Based on previous
>experience
>>and Oracle documentation, he has a strong feeling that the online
>>backups are not valid.
>>
>>Have any of you used BRBackup, Backint, and ADSM to do an on-line
>backup
>>(type=util_file_online) followed by a restore? If so, did the backup
>put
>>any tablespace in backup mode more than one time during the run? Did
>you
>>have any problems?
>>
>>We're running SAP/R3 3.0F with the 3.1H kernel upgrade, Oracle 7.3.3
>>(the reason for the kernel upgrade), ADSM 2.1.5.13 (server) and
>2.1.5.6
>>(client); we've seen this behavior with Backint 2.1.2.1, 2.1.2.7,
>2.1.3,
>>and 2.2.0.
>>
>>So far, the response from Oracle has been that this is not valid;
>SAP
>>indicates that this is a Backint issue, and the Backint support
>group
>>indicates that Backint is working as designed and has been SAP
>certified
>>for some time.
>>
>>Us? We're a bit nervous-like, and will be until we get a chance to
>run
>>tests of our own.
>>
>>TIA -
>>
>>Tom Kauffman
>>Sr. Technical Analyst
>>NIBCO, Inc
>>
>>kauffmant AT nibco DOT com
>>
>