Hi Christian,
Glad to hear global configs helped and we understand managing lots of configs can be challenging. One thing I would definately do in your case is either use the scServer and scAgent that way your config files are central or another strategy I have seen customers use to get everything central without agent is install scServer on NFS share, then you can mount it on all your backup hosts. Using this strategy would allow you to remove wrapper scripts. You would still need two configs for your case 1) oracle data 2) arhchive logs but you could run the oracle archive log backup from oracle data config as NTAP_POST_CMD01, for example:
NTAP_POST_CMD01=/path/to/snapcreator --profile oracle --config arch --action snap --policy daily --verbose --global
You can also have the logs or config dirs located outside of SC install path with --log_dir and --config_dir options, that helps mostly with security / access
You cannot get away from needing two configs, even if oracle backup process worked within one config you would still need second config since you are running archive log backups more frequently and not backing up database at that time. Most customer do this, once a day daily backup of oracle data + archive logs and multiple times a day just archive log backups.
do you know how to get rid of the 1 minute sleeping after snapvault trasnfer has been startet?
"NetApp Snapvault Update on destination flr04:/vol/flr10_t11g_1/ora is running, status transferring! Sleeping 1 minute"
This is hard coded so using SnapVault means Snap Creator must wait until it is complete and every 60 seconds it checks, that is how it works, here is process:
1. snapvault update
2. check every minute until snapvault update is complete
3. when complete create snapvault snapshot, locking changes in snapshot on secondary
4. SC will check for any errors including transfer errors which is nice. SnapVault will go idle but that doesnt mean it is successful
Alternatives to SnapVault managed by SC:
1. Protection Manager - SC can register snapshot in PM and it can then do snapvault, SC can even kick off the PM backup job
2. SnapVault scheduler - SC supports create filer scheduler compliant snapshots. You can configure snapvault schedule on the filer and use the NTAP_SNAPVAULT_SNAPSHOT=Y option to enable this
In both cases SC takes consistent snapshot and then PM or snapvault scheduler on filer are responsible for snapvault. If you use these options you dont need to set SNAPVAULT_VOLUMES and SNAPVAULT_UPDATE=N.
Let me know if this helps
Keith