Best practice resource group or normal backup job

GREGD — Wed, 04 Jun 2025 12:50:34 GMT

what would i do with sql backup.I have sap server for quality sapq1,sapq2 and production sapp1,sapp2. All 4 servers have sepperatly volumes.

all for servers should be backup on the same time at 2 o clock full db

i create a resource group quality which include sapq1 and sapq2 and resource group production which include sapp1 and sapp2.

but its this ok? Or should i make 4 seperate job each server one job.

seperrate job means that i can also make backup only of one server. But on another side at 2?o clock 4 jobs started normally by rg only 2

what is there best practice?

Re: Best practice resource group or normal backup job

Spaceball — Thu, 14 Feb 2019 13:09:42 GMT

You can solve this using resource groups, as long as you do not need any server individual pre/post scriptings or server individual parameter.
I use post-scripting for truncating db2 archivelogs. Therfor I need the db-name as a parameter on each server.

(/.../.../script.sh <dbname> )

I can not do this using the resource group solution.

topic Re: Best practice resource group or normal backup job in Data Protection

Best practice resource group or normal backup job

Re: Best practice resource group or normal backup job