NetWorker Backup Tool for MS-SQL Databases for SAP

[Former Member]

Hi,

With refrence to SAP Note SAP Note 1048382. There is an option available in DB13 transaction to backup SQL server databases using third party backup software. This feature requires third party vendor backup tools to create a backup stored procedure with the SAP naming convention in the MSDB database. This is a restricted procedure and works only with the small set of parameters of the backup command. If third party backup tools are installed with the necessary stored procedure as required by SAP to enable backup of SQL Server databases, then third party backup procedure is the default option for backup. This option will be selected as the default backup procedure for all the scheduled backup jobs. There is an option available in the DB13 main calendar to enable or disable the third party backup procedure. The user has an option in the parameter selection screen to select Native Backup or third party vendor tools to backup SQL server databases. An user exit is provided in the SAP backup procedures so that third party backup procedures are called from SAP procedures if third party backup is selected to backup the SQL server databases. The third party backup stored procedures are called with the backup parameters selected by the user in the DB13 parameter selection screen. Like SAP CCMS jobs, the third party backup stored procedures are called from the SQL Server Agent Jobs created by the DB13 Transaction.

Anbody have exepience with User Exit provided by EMC/NetWorker/Legato Backup Tool !!???

I will really appreciate if anyone can shed some light on this topic.

Tx & Rg

Rayees Palot

[markus_doehr2 · Accepted solution]

We use Networker (7.0 SP3) to backup our full landscape - including non-SAP systems. Since we wanted to have one source to check if the backups were working we refrained from using DB13 in each system. We use the networker itself to schedule.

Backing up a SAP system is not just backing up the database but also the profiles, trans directories etc. So you would have to look up in two places (SAP-system + Networker) if you have everything to restore in case of a disaster recovery.

Backing up itself works flawlessly.

Markus

[Former Member · Accepted solution]

Dear Mr.Markus,

I totally agree with the following point

"Backing up a SAP system is not just backing up the database but also the profiles, trans directories etc. So you would have to look up in two places (SAP-system + Networker) if you have everything to restore in case of a disaster recovery. "

Using Networker OS agent we will be performing OS + SAP/SQL System directories & files. Our real concerned area is if we perform databse backup through Networker SQL Agent we will not able to monitor job status and logs through SAP DBACOCKPIT/DB13 tool from SAP.

We are looking forward how to trigger backup jobs from SAP using DB13 and Networker SQL Moudle Backup Tool.

Once again thank you for sharing your expierence and thougts.

Rayees Palot

[Former Member · Accepted solution]

Hi,

We trigger our SAP/SQL server systems with Netbackup and the database and transaction backup logs are shown in DB12. So, there is no need to trigger the backups from DB13. I guess it should be the same with Networker.

Regards,

Olivier