Instance Naming |
Each application in the KM uses a naming convention to differentiate the particular instance. BEX_SERVER Application Instance Naming There is only one instance of the BEX_SERVER application class and this is labeled Symantec Backup Exec. BEX_ALERT Application Instance Naming Instances of the BEX_ALERT application class are labeled with the time they were generated in Backup Exec, in the format “YYYY/MM/DD HH:MM:SS“ (e.g. “2009/07/18 21:30:00“). BEX_DRIVEPOOL Application Instance Naming Instances of the BEX_DRIVEPOOL application class are named as per the Backup Exec drive pool (e.g. ‘All Drives’). BEX_DRIVE Application Instance Naming Instances of the BEX_DRIVE application class are named as per the physical Backup Exec drive (e.g. ‘HP 1’). BEX_JOB_CONTAINER Application Instance Naming There is only one instance of the BEX_JOB_CONTAINER application class and this is labeled BEX_JOBS. BEX_JOB Application Instance Naming Instances of the BEX_JOB application class are named as per the defined Backup Exec job (e.g. ‘Exchange Servers - Full’). BEX_JOB_DETAIL Application Instance Naming Instances of the BEX_JOB_DETAIL application class are labeled with the date and time the Backup Exec job started in the form ‘YYYY/MM/DD HH:MM:SS’ (e.g. ‘2001/11/07 14:56:06’). A 24-hour clock is used for the time information. In some extreme circumstances, when the date information cannot be obtained from the required log file, the instance name will be of the form ‘- HH:MM:SS’ (e.g. ‘- 14:56:06’). BEX_MEDIASET Application Instance Naming Instances of the BEX_MEDIASET application class are named as per the defined Backup Exec media set (e.g. ‘Exchange Servers - Monday’). BEX_SERVICE Application Instance Naming Instances of the BEX_SERVICE application class are named as per the Backup Exec service (e.g. ‘Backup Exec Server v8.0’). |