This log job but process for duplication for tape not start and error.
08/08/2023 16:15:22 - Info nbjm (pid=15020) starting backup job (jobid=5924707) for client xxxxxx.xxxxxxx.org.br, policy POL-SEDE-SAPHANA-DEV-XX _DB_SEMANAL, schedule FULL_SAPDEV_SEMANAL 08/08/2023 16:15:22 - Info nbjm (pid=15020) requesting MEDIA_SERVER_WITH_ATTRIBUTES resources from RB for backup job (jobid=5924707, request id:{0A3D746B-4705-41A8-9EA4-B3A10098AC93}) 08/08/2023 16:15:23 - requesting resource stu_disk_xxxxx 08/08/2023 16:15:23 - requesting resource xxxxx.NBU_CLIENT.MAXJOBS.xxxx.xxxxx.org.br 08/08/2023 16:15:32 - granted resource xxxxxx.NBU_CLIENT.MAXJOBS.xxxxx.xxxx.org.br 08/08/2023 16:15:32 - granted resource stu_disk_xxxxxx 08/08/2023 16:15:36 - estimated 0 kbytes needed 08/08/2023 16:15:36 - Info nbjm (pid=15020) started backup (backupid=xxxxx.xxxxxx.org.br_1691522134) job for client ssapsrdadd1.sesisenaisp.org.br, policy POL-SEDE-SAPHANA-DEV-xxxxx_DB_SEMANAL, schedule FULL_SAPDEV_SEMANAL on storage unit stu_disk_xxxxx 08/08/2023 16:15:51 - started process bpbrm (pid=120066) 08/08/2023 16:15:53 - Info bpbrm (pid=120066) xxxxxx.xxxxxx.org.br is the host to backup data from 08/08/2023 16:15:54 - Info bpbrm (pid=120066) reading file list for client 08/08/2023 16:15:54 - connecting 08/08/2023 16:15:56 - Info bpbrm (pid=120066) starting bphdb on client 08/08/2023 16:15:56 - Info bphdb (pid=13570) Backup started 08/08/2023 16:15:56 - Info bphdb (pid=13570) The script </usr/openv/netbackup/ext/db_ext/sap/scripts/sap_hana/SSAPSRDADD1_SHD_TENANTDB_backup.utl> has been approved to run and is stored locally. 08/08/2023 16:15:56 - connected; connect time: 0:00:00 08/08/2023 16:15:56 - Info bphdb (pid=13570) The script </usr/openv/netbackup/ext/db_ext/sap/scripts/sap_hana/SSAPSRDADD1_SHD_SYSTEMDB_backup.utl> has been approved to run and is stored locally. 08/08/2023 16:45:06 - Info bpbrm (pid=120066) validating image for client xxxxxxxx.xxxxxx.org.br 08/08/2023 16:45:07 - Info bphdb (pid=13570) done. status: 0: the requested operation was successfully completed 08/08/2023 16:45:07 - end writing The requested operation was successfully completed. (0)
Backup for disk ok, but not duplication for tape.
I tested SLP for other type backup example MIcrosoft SQL duplication for tape works.
The nbstlutil report shows that all SLPs are completed. Select a backupid that you have not run manual duplication and run the following command. Post the output. bpimagelist -backupid xxxxxxx
sometimes you are referring *DEV* policy, sometimes *PRD* policy. Doublecheck if intended policy/schedules are used for backups.
What is tricky on script based policies like SAP is that when misconfigured, Application Backup schedule from another policy can be used instead of schedule in original policy. For example, when App Backup schedule in original policy wont have open time window at the runtime, NetBackup attempt to use open App Backup schedule from another policy if exists for the same client.
Best to check in Activity Monitor that intended policy/schedules with intended SLP are really used for child backup jobs.
ok. you choose an automatic schedule. this schedule is only for starting the backup and has no value. And no data of course. Please run the same command with a backup id of an "Application backup schedule" backup. (DB_SAPHANA)
I think StefanosM & Michal_Mikulik1 are on the right track - if you do not configure your backup script correctly on the client you can have unintended outcomes.
When the backup is started by the automatic schedule, this initiates a process on the client which starts a backup process from the client (effectively independant of the original job). This backup process connected to the primary server and will perform a best/first match looking for a policy and schedule to use for the backup. So if the backup script on the client doesn't specify the actual policy or schedule to use, NetBackup will find the first matching (SAP) policy that has an application schedule it can use. I suspect that this is what is happening, and the policy it is finding is not using an SLP (or not the one you want).
In the backup script on the client you should be able to specify the policy & schedule names (these are typically done using the variables NB_ORA_POLICY, NB_ORA_SCHED & NB_ORA_CLIENT in the initSID.sap or initSID.utl files. Check the SAP admin guide for more details.
