Today we have following Environment:
- A Oracle Cluster with 10 Oracle DB Ressourcegroups in activ/passiv mode (All DBs runs normally on one Clusternode).
- One snapcreator configfile with all DBs defined and run again the Clusternode, where hold all the Oracle DB ressources.
- We have 3 snapcreator Schedules (daily,wekly,monthly) for this configfile.
- In the Protection Manager we have one Dataset.
Generally this Environment run smoothly :-), but we have following restrictions:
- When we move one DB Ressourcegroup from one Node to the other, we have to edit everytime both configfiles (Node1: Remove Volumes/DB, Node2: Add Volumes/DB)
- One PM Dataset per Clusternode with RessorcePools = Nearstore Volumes and snapvault are generated automatic. We have a long retention on the nearstore and so its horrible when
a DB Ressourcegroup is moved from one Clusternode to the other or a DB is moved to another Server, because this gives new snapvault relationsships in another Volume (because its another Dataset with its own Nearstore Volumes).
Future Design we want to implement for flexibility reasons:
- The ability to move the Ressourcegroups separate without edit the configfile in snapcreator.
- One Dataset in Protection Manager per DB Ressourcegroup (10 DB instances = 10 Datasets).
For reach this flexibiliy we must have one Configfile for every DB and then we run the configfile against the DB Ressourcegroup and not the Clusternode (Backup runs then without editing any config).
In this Case we have 10 Configfiles instead 1 configfile
Question about this implementation:
- Does this mean, that we need three Schedules for every configfile (10 configs with 3 Schedules per config = 30 Schedules). Or gives a solution, where I can start all the configs with one Schedule
- Can I start all the Schedules (fe 10 daily) to the same time, because for some DB instances the same snapcreator client is involved (because this instances runs on the same physical Node) ....
- Is someone out there with such a kind of configuration?
I hope you understand my explanation 🙂