Archive log backup from non default location

[Former Member]

Hi

can we backup archive log files from non default location.

we have moved archive files from our /oracle/<SID>oraarch location to other location on disk manually to avoid oraarch getting to 100%

how can we configure brarchive to take backup of these files from this new location, else there will be a gap of archive files backup?

Thanks

[former_member185031]

Brtools read the information from initSID.sap file. So you have to change the location on that files to take the backup.

Regards,

Subhash

[Former Member]

hi

Since this is a temporary location , and backup from this is needed in exceptional cases , can we use brtools options to take backup without modifying initSID.sap?

Thanks

[former_member185031]

You have to modify the initSID.sap file.There is no other option as far as i know. After taking the backup you can again change it back to actualy path. You need not to shut down the Database for that.

Regards,

Subhash

[Former Member]

Subhash

we take backup to tape directly.

archive_copy_dir option is used for taking backup from disk

which option to use in our case?

Thanks

[former_member185031]

That is correct. Just define the new temporary location of your archive file there and start BRTOOLS. Once it copied all the archive files on your tape then set the original Archive location once again.

Regards,

Subhash

[volker_borowski2]

That is correct. Just define the new temporary location of your archive file there and start BRTOOLS. Once it copied all the archive files on your tape then set the original Archive location once again.
> 
> 
> Regards,
> Subhash

Hi Subhash,

I think you are wrong and I hope such a setup will never ever be possible at all.

I can think of no parameter that would make such behavior a valid one.

No initSID.sap parameter can take care about what would be the SOURCE of a SAVE run.

This will allways be Oracle to tell SAP where to pick up the logs.

Otherwise (!!) it would be possible to configure brarchive in a way where the runs

complete successfully without actually saving relvant logfiles. I would consider this

to be a very bad error in design.

The only way would be a staged backup, but in this case brarchive need to do

the staging first (and log this action in archSID.log) to process the move to tape later,

but the stageing was done manually in this case.

As for the original problem: Save the relevant logs with sepearte tools and keep

good track on these until your backup cycle is complete.

Volker

[Former Member]

Hi Volker

What do mean by 'backup' by separate tools?

Does this mean , i cannot get brtools to backup my archive log files which have been temporarily moved to a non default location?

Thanks

[volker_borowski2]

Hi,

unfortunately I am not aware of this feature.

You might be able to move them back and save them then, but only,

if a previeous run does not have them tagged as "no found".

In this case you would need to rename archSID.log, to make brarchive

re-read these logs that are already processed from brarchives point of view.

But this will move the old information of archSID.log out of visibility from

the brtools and you surely do not like to have it this way.

So how many of these are there? 4GB -> Burn them to a DVD (binary copy) or do a "tar" to a seperate tape.

and you are fine. If your archive area is to small, consider to use a

brarchive -f

next time you run a big-logging-job

This will continously save logs as they come in.

Volker