Problem

STATUS CODE 241: Oracle backups fail with a NetBackup Status Code 241 (the specified schedule is the wrong type for this request).

Error
the specified schedule is the wrong type for this request

Solution
Overview: Oracle backups fail with a NetBackup Status Code 241 (the specified schedule is the wrong type for this request). Troubleshooting: Review the schedule names of the Oracle policy on the master server. Log files: N/A Resolution: If the Oracle Recovery Manager (RMAN) script specifies the NB_ORA_SCHED keyword, its value must be the name of a schedule with a type of "Application Backup." On the master server, from the command line, run the bppllist command (found in the /usr/openv/netbackup/bin/admincmd directory on a UNIX/Linux master, or the <install_path>\veritas\netbackup\bin\admincmd directory on a Windows master) as shown (bold added for emphasis):
bppllist -U -allpolicies -----------------------------------------------------------Policy Name: Policy Type: Active: <SNIP> Schedule: Type: Default-Application-Backup <=Note the name Application Backup <= Note the type <oracle_policy> Oracle yes

The value for the NB_ORA_SCHED keyword, if specified, must be the name of the schedule in an Oracle policy which is of type "Application Backup". So, in the above example, since the

schedule that is of type "Application Backup" is named "Default-Application-Backup", the value for the NB_ORA_SCHED keyword must be "Default-Application-Backup". If a template is being used, the same information applies. In the "Schedule" parameter, specify the name of the schedule which is of the type "Application Backup".

Problem
STATUS CODE 241: SQL backups exit with NetBackup (tm) Status Code 241: the specified schedule is the wrong type for this request.

Error
Exit Status Code 241: the specified schedule is the wrong type for this request

Solution
Overview: Attempts to backup SQL databases fail with a NetBackup Status Code 241 (the specified schedule is the wrong type for this request). Troubleshooting: Review the existing SQL policies, and enable the dbclient log file on the SQL server. Log files: In the dbclient log file on the SQL server, the following information is observed (bold added for emphasis): In this log snip, the dbclient process makes a query to bprd, sending the parameters client=optsrv4 policy=SQL schedule=NONE.
03:11:04.490 [2612.2320] <2> logconnections: BPRD CONNECT FROM 146.142.104.51.3133 TO 146.142.104.51.13724 03:11:04.490 [2612.2320] <2> vauth_authentication_required: ..\libvlibs\vauth_comm.c.799: no methods for address: no authentication required 03:11:04.490 [2612.2320] <2> vauth_connector: ..\libvlibs\vauth_comm.c.199: no methods for address: no authentication required 03:11:04.490 [2612.2320] <2> bprd_connect: no authentication required 03:11:04.490 [2612.2320] <2> vnet_check_vxss_client_magic_with_info: ..\libvlibs\vnet_vxss_helper.c.776: Ignoring VxSS authentication: 2 0x00000002 03:11:04.490 [2612.2320] <2> vnet_check_vxss_client_magic_with_info: ..\libvlibs\vnet_vxss_helper.c.932: Not using VxSS authentication: 2

0x00000002 03:11:04.490 [2612.2320] <4> VxBSAGetPolicyInfo: INF - request string: <optsrv4 SQL NONE> 03:11:04.662 [2612.2320] <4> VxBSAGetPolicyInfo: INF - Policy Info:STD 03:11:04.662 [2612.2320] <4> CDBbackrec::CDBbackrec: INF - Use standard backup method with policy <SQL>.

Then the dbclient process confirms the policy is read from the batch file ,but there is nothing being returned for the schedule name.
03:11:05.068 [2612.3324] NBBSA_POLICY 03:11:05.068 [2612.3324] 03:11:05.068 [2612.3324] NBBSA_SCHEDULE 03:11:05.068 [2612.3324] <4> VxBSAGetEnv: INF - entering GetEnv <4> VxBSAGetEnv: INF - returning - SQL <4> VxBSAGetEnv: INF - entering GetEnv <4> VxBSAGetEnv: INF - returning -

Finally, the dbclient process indicates the master returned the schedule name 'Full'.
03:11:05.068 [2612.3324] <4> dbc_GetScheduleNameFromConfig: master's schedule= <Full>

Resolution: In this particular case, the registry on the SQL server needed to be modified to have the incorrect values removed. Warning: Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. Great care should be taken when making changes to a Windows registry. Registry modifications should only be carried-out by persons experienced in the use of the registry editor application. It is recommended that a complete backup of the registry and workstation be made prior to making any registry changes. On the SQL server, open the registry (Start > Run > regedit) and navigate to the following registry key:
HKEY_LOCAL_MACHINE\Software\VERITAS\NetBackup\CurrentVersion\Config

Find the entries for BPBACKUP_POLICY and BPBACKUP_SCHED. Set both of these keys to have a value of "any" in the registry. Additionally, it is possible to set the schedule name in the backup script, using the keyword NBSCHED. Please refer to the NetBackup for Microsoft SQL server Administrator Guide (refer to the Related Documents section below) for more information on the use of this keyword.