Applies to: Commvault V11 SP10 and earlier versions.
Symptom
If both a Windows agent and a UNIX agent are installed on a NAS client, there is no direct support for the Schedule Policy and Alerts features. You need to use the following workaround procedure.
Resolution
-
If you want to create a single schedule policy for one file system agent, then you can create a data protection schedule policy.
-
If you want to add subclients from both files system agents to the same schedule policy that you created, then you can edit the associations of the schedule policies with the command line interface.
-
If you want to create a new schedule policy for one of the file system agents and, if the other file system already has a schedule policy, then you must create the schedule policy through the command line interface.
To create a schedule policy with the command line interface and add the subclient associations, use the Save As Script button available in the New Schedule Policy dialog box. The Save As Script operation creates the XML file. Edit this XML file to add associations blocks, one for each subclient that you want to associate with the schedule policy, as in the examples.
In the XML file, under the taskInfo element, add an associations block for each subclient that you want to associate with the schedule policy. The associations block must contain the following information:
-
Subclient name
-
Application name
-
Client name
To create schedule policy with the command line interface, see Creating a Schedule Policy Using the Command Line Interface.
Examples
The following excerpt is an example of an association block for the Linux file system:
<associations>
<subclientName>subclient1</subclientName>
<backupsetName>defaultBackupSet</backupsetName>
<appName>Linux File System</appName>
<clientName>client1</clientName>
</associations>The following excerpt is an example of an association block for the Windows file system:
<associations>
<subclientName>subclient2</subclientName>
<backupsetName>defaultBackupSet</backupsetName>
<appName>File System</appName>
<clientName>client1</clientName>
</associations>