on 08-16-2012 2:13 PM
My dear fellows
I'm looking into some sort of cheap (i.e. not going down the High Availability route unless I have to) resilience for SAP/Oracle backup and redo log locations.
Looks like Oracle's LOG_ARCHIVE_DEST_1
/ LOG_ARCHIVE_DEST_
2 functionality will allow me to switch redo log location if oraarch fills up, or if DEST_1 becomes unavailable so that's great.
So now I'm looking at the same for backups. I notice that I can specify alternative targets with backup_root_dir in the initSID.sap file, like so (I'm using Solaris):
backup_root_dir=(/backup,/backup2)
and the SAP documentation says that will work in the event of /backup filling up. Great. However, on this system, /backup is rather large. What's more likely is that /backup, an NFS filesystem on a fairly flaky server, will become unavailable.
So the question is, given the above backup_root_dir configuration, will my SAP backup flip to /backup2 if /backup disappears? The documentation doesn't appear to give the answer.
I can try it out of course, but it's tricky to emulate vanishing servers...
Thanks for any help! Chris
Hi Chris,
backup_root_dir does not provide alternative location. It provides, parallel disk backup option. Check the document, below;
http://help.sap.com/saphelp_nwpi71/helpdata/en/47/0b9a93434f57dde10000000a1553f7/content.htm
Best regards,
Orkun Gedik
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
91 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.