The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
The dashboard is the home page of the administration site and provides several parameters and graphs key monitoring features.
The dashboard includes the following sections:
System Monitor—Displays the system status and time stamp and includes the following subsections:
Meetings and Users—Status of meetings in progress and usage. Displays the number of meetings currently in progress and the number of distinct participants (usage). The status LED indicates whether the meetings in progress and usage are under or over the configured alarm threshold. A green status LED indicates under the configured threshold while red indicates over the configured threshold. See Viewing and Editing Alarms for more information about configuring alarms.
Alarm icon—Select the Alarm icon to view and edit the alarm threshold settings you have configured. Alarm thresholds are displayed on the Alarms page in numerical form. By default, alarm thresholds are displayed as a percentage. See Viewing and Editing Alarms for more information about configuring alarms.
You can configure alarms for the following:
Meetings In Progress—Indicate when current meetings are experiencing issues.
Usage—Total number of distinct users using the system. Occasionally participants are in multiple sessions, but participants are only counted once.
Storage—Recording and database backup storage space used.
Note | The storage alarm appears if you have configured a storage server. See Adding an NFS or SSH Storage Server for more information. Meeting recording is disabled if the storage usage is over the threshold. |
Log Partition—Amount of space used to store the Application Audit Log.
Note | If an Auditor is configured for your system, this alarm is only visible to the Auditor. |
License Usage—Percentage of permanent licenses assigned to host users.
Grace Licenses—Indicates whether grace licenses are assigned to host users.
Data Center—Lists the name of each data center, whether Maintenance Mode is on or off, the amount of storage used for each data center, and the status of data replication. See About the Data Center Information Displayed on the Dashboard for more details.
Meeting Trend—A graph of the number of meetings held on the system during a specified time. Use the From and To fields to set the time for the meeting trend information and for the meetings displayed in the Meetings list. You can select a point on the Meeting Trend graph to list the meetings on the Meetings list that occurred during the time specified on the graph. To view meetings that occurred during a specific time of day, mouse over the graph and select the desired time.
Meeting Search—Find a meeting by entering specific search criteria, such as meeting number, meeting topic, or a date range.
Meetings—The total number of meetings that occurred during the selected time, the meeting topics, hosts, numbers of participants, and the state of the meeting. If a data point has not been selected from the Meeting Trend graph, all meetings for the time period are shown. You can sort each column of information in the Meetings list, and the meetings are displayed in order by state: In progress, Ended, and Not started.
Selecting a Meeting Topic in the list displays details of the meeting, including: Meeting number, start time, end time, general status, and indicates if the meeting has been analyzed in detail. Prior to analysis, the Status parameter shows the overall status of the meeting as it relates to quality. Select Analyze Meeting Detail to perform a detailed analysis of the meeting and generate a log. After the log has been compiled, the general Status of the meeting might change based on the detailed investigation performed by the analysis. The date and time the log was generated is displayed and you are sent email with the log file download information. You can also download the log from the dashboard by selecting Download Log.
Note | If a meeting is not attended by the meeting host, the meeting is terminated 30 minutes after last participant exits the meeting, regardless of the scheduled end time, and shows as being in progress until this time expires. |
Maintenance—Schedules a maintenance window announcing when maintenance mode will be turned on and off. See Scheduling a Maintenance Window and About Maintenance Mode for more information.
Last System Backup—Time and date that the last backup was taken; the filename, size, and location of the backup; and the date and time of the next backup. It also notifies you if the backup failed and the date of the first backup attempt if one has not been created yet. A separate backup link is provided for each data center.
Note | Only appears if you have configured a storage server. |
System—Displays the maximum number of users who can simultaneously participate in meetings, the version number, product URL, whether public access is allowed, if it is a high availability system, and the number of user licenses. Select View More to go to Configuring Your System.
Users—Displays the number of active users, whether Directory Integration is configured, when the next synchronization will occur (if configured), and the selected type of authentication. Select View More to go to Editing Users.
Settings—Shows the maximum number of participants allowed in each meeting, audio type, and whether or not WebEx HQ video is enabled. Select View More to go to Configuring Settings.
The System Monitor section of the dashboard displays status information for the data centers that comprise your system. If you have a single data center system, the data center name automatically assigned by the system is CWMS System, but the status information is dynamically updated for the single data center. In a multi-data center system, each data center is listed in a separate row by the name you entered during the join data center process and the status information is dynamically updated separately and displayed for each data center.
Good—All components of the data center are working properly. No system-generated email messages sent to the administrator.
Partial Service—Some of the components of the data center are not working properly, but the data center is providing service. The system sends an email to the administrator indicating that this data center needs attention.
Blocked—The system has blocked service on this data center and is redirecting all activity to another data center. The system sends an email to the administrator to indicate that service is down, data is being redirected to another data center, and this data center needs attention.
Down—The operation of a data center has degraded to the point where it can no longer provide reliable service and failover to an operational data center is in progress. The system sends an email to the administrator to indicate that service is down, data is being redirected to another data center, and this data center needs attention.
In a Multi-data Center (MDC) environment, some components are capable of cascading, so the disabled service on this data center might be provided by another data center. This is not an indication of overall system status; it applies only to the status of this data center.
Blocked or Down and Maintenance Mode is on—The data center status continues to show that the data center is blocked. When Maintenance Mode is turned off AND all components are again up and running, the status changes.
Unreachable—Another data centers cannot communicate with this data center. The system sends an email to the administrator asking them to check the network connectivity between the data centers.
Maintenance—Indicates whether a data center has Maintenance Mode turned On or Off.
Storage—The amount of storage used on the storage server connected to each data center. Not Configured displays If a storage server is not connected to the system.
Data Replication—Indicates whether data replication is occurring between the data centers in an MDC system.
When a data center is in the Blocked or Down state, users might experience the following:
In-progress meetings are automatically moved to an operational data center after a few minutes; similar to what happens in a failover situation. There is no impact on PCN or Blast Dial meetings.
Previously scheduled meetings that have not started move to the operational data center. No other actions are required for the host or participants.
Users sign in to a WebEx site URL in the usual manner, but the system redirects the sign-in to the operational data center.
Administrators can sign in to the blocked data center as well as the operational data center.
Administrators receive a system-generated email which explains which data center is in the blocked state, and information explaining some of the possible causes.
To monitor CPU, memory, and network usage, we recommended that you use the performance tab of each CWMS virtual machine in vSphere client or vSphere Web client. The advantage to monitoring performance a of CWMS virtual machines by using vSphere client or vSphere Web client is that each virtual machine can be monitored separately and for a specified period of time. If an issue that affects the system negatively exists, it is easier to precisely troubleshoot.
To monitor CPU usage refer to http://pubs.vmware.com/vsphere-51/index.jsp?topic=%2Fcom.vmware.vsphere.monitoring.doc%2FGUID-FC93B6FD-DCA7-4513-A45E-660ECAC54817.html. Variations and spikes in CPU usage is expected; however, during general system use all levels should be less than 90 percent.
To monitor Memory usage refer to http://pubs.vmware.com/vsphere-51/index.jsp#com.vmware.vsphere.monitoring.doc/GUID-C442423F-18CD-4F01-914E-286ED6C72BC6.html. During normal operation Memory usage should be stable. Some variations are expected, but an increasing trend over a long period of time might indicate a pending issue that will soon affect system performance.
To monitor Network usage refer to http://pubs.vmware.com/vsphere-51/index.jsp#com.vmware.vsphere.monitoring.doc/GUID-41B7E742-B387-4638-A150-CB58E2ADD89F.html. Network usage can vary widely in reference to a CWMS virtual machine, and spikes in network usage (for example during a backup) are expected.
Step 1 | Sign in to Site Administration.
In a Multidata Center system, the DNS determines which data center Dashboard appears. Use this Dashboard to manage all the data centers in this system. | ||||||||||||||||
Step 2 | Select the alarm icon. | ||||||||||||||||
Step 3 | To modify, activate, or deactivate alarm thresholds, select Edit.
The Edit Alarms page appears. Select Percentage % to view the alarm threshold as a percentage or Number # to view the alarm threshold as a number. The default setting is Percentage %. | ||||||||||||||||
Step 4 | Select the check
boxes for the alarms that you want enabled and select the interval for each
enabled alarm.
An email is sent to administrators when an alarm exceeds a threshold. The interval is used to suppress multiple alarms within the specified time to avoid sending too many emails about the same issue. | ||||||||||||||||
Step 5 | Select
Save.
Your alarm settings are saved and the Alarms page is updated with your changes. |
See Viewing the Meetings List to view more information about a meeting.
See Finding a Meeting for more information about using the Meeting Search tab.
Step 1 | Sign in to Site Administration.
In a Multidata Center system, the DNS determines which data center Dashboard appears. Use this Dashboard to manage all the data centers in this system. | ||||||||||||||||||||||||||||||||||
Step 2 | Above the
Meeting Trend graph set a trend period by selecting the
From and To date and
time.
By default, the Meetings list displays the meetings for the current 24-hour period. See Viewing Meeting Trends for more information. By default the Meetings list displays meetings in the order of their scheduled start time.Meetings are displayed in order of status: In Progress, Ended, Not Started. Information displayed in the Meetings list includes:
| ||||||||||||||||||||||||||||||||||
Step 3 | (Optional) Select a column heading to sort the meetings. | ||||||||||||||||||||||||||||||||||
Step 4 | Use the pagination function to view the next or previous page. | ||||||||||||||||||||||||||||||||||
Step 5 | Select a
meeting
topic in the Meetings list to display more meeting information.
The list expands to show meeting details, such as the names of the participants, the start and end time, and the meeting status. | ||||||||||||||||||||||||||||||||||
Step 6 | (Optional) To refine your search, select the Meeting Search tab. Additional search fields appear. |
See Viewing a Meeting Analysis Report for more detailed meeting information.
See Downloading Cisco WebEx Meeting Logs to download a compressed file with several meeting logs. Use these logs to troubleshoot issues that participants experienced during a meeting.
See Finding a Meeting to refine your search results or find a specific meetings.
Step 1 | Sign in to the Administration site. |
Step 2 | In the Meeting Trend section, select the Meeting Search tab. |
Step 3 | Enter your
search criteria.
Search for meetings by using some or all of the following fields:
|
Step 4 | Select Search. The Search Results lists the meetings that match the search criteria. |
Step 5 | To start another search, select Clear. The system clears the search fields, but the results from the previous search remain in the Search Results. |
Step 6 | Select a
meeting
topic in the Meetings list to display more meeting information.
The list expands to show meeting details, such as the names of the participants, the start and end time, and the meeting status. |
To view additional meeting information, see Viewing a Meeting Analysis Report.
To download a zipped file with meeting logs, see Downloading Cisco WebEx Meeting Logs.
Additional information about a Cisco WebEx meeting and its participants is available on the Meetings Analysis Report page.
One or more meetings are displayed in the Meetings list on the Meeting Trend tab. See Viewing the Meetings List for details.
Step 1 | Select a meeting topic displayed in the Meetings list on the Meeting Trend tab. | ||
Step 2 | In the Meetings list, select Analyze Meeting Detail. While the system is processing the information, the date and time the system started generating the information is displayed with a status of Pending. When the system is finished generating the information, the date and time become an active link and the Pending status changes to a Download log active link. | ||
Step 3 | Select the
date and
time link to view the
Meeting
Analysis Report page.
The following information displays:
| ||
Step 4 | Select the Meeting Messages tab to display the Function, Time, and Messages generated during a meeting. | ||
Step 5 | Select the
Participants tab to display the following
information for each meeting participant:
|
See Downloading Cisco WebEx Meeting Logs to download a compressed file with several meeting logs.
While a Cisco WebEx meeting is in-progress or when a meeting has ended, you can download system-generated meeting logs that provide information for troubleshooting an issue users experienced during a meeting.
Step 1 | Sign in to the Administration site. |
Step 2 | Select the Meeting Trend tab, then select a From and To range to display a graph of meetings that occurred during the selected time frame. |
Step 3 | Click a particular location on the Meeting Trend graph to list the meetings that occurred within 5 minutes of the selected time in the Meetings list below the graph. |
Step 4 | Select a meeting topic in the Meetings list. Information about the selected meeting display below the meeting topic. |
Step 5 | Select Download logs. |
See About Meeting Logs for more information about the downloaded meeting logs.
This log contains information about the online portion of a meeting.
Conference ID
Meeting ID
Scheduled Start Time
Start Time
End Time
Host Email Address
Site URL
Meeting Type—Meeting client
Meeting Name—The meeting topic.
Primary Call-in Number
Secondary Call-in Number
Delete Meeting When Ended—Indicates whether this meeting is deleted from the Meetings details page when the meeting ends.
Meeting Status
Application Sharing—indicates whether the application sharing feature was used during a meeting.
Regular Telephony—Indicates whether participants called the meeting using telephones.
Hybrid Telephony
Eureka Video
Eureka VoIP
MMP VoIP
Hybrid VoIP
MMP Video
NBR2
Mobile
Audio Broadcast
Audio Broadcast for Mobile
This log provides information about audio streaming, audio switching, and SVC stream adaptation to the meeting client as it relates to MMP.
This log contains information about a teleconference meeting.
This log contains information about the web join events.
Meeting Name—Displays the meeting topic.
Conference ID—Data conference instance ID.
Site ID—The name of the Cisco WebEx site.
Note | The host that starts the meeting is not included in this total. |
Total Join—The total number of people who joined the meeting.
Start Time—Starting date and time of the meeting.
End Time—Ending date and time of the meeting.
Duration—Amount of time, in minutes, the meeting lasted.
End Reason—Reason the meeting ended.
When you turn on Maintenance Mode, all in-progress meetings end and the Meet Now function becomes unavailable. Before you perform system maintenance for a Single Data Center system, schedule a maintenance window and notify users in advance. Inform users that during a maintenance window, meetings currently in progress are terminated and that they cannot schedule meetings that overlap the maintenance window. If you are running a Multi-data Center system and only one system is put into Maintenance Mode, meetings transparently failover to the active system and there is no need to notify users.
For example, an administrator wants to bring a Single Data Center system down for one hour for maintenance. The administrator can try to schedule a time when no meetings appear to be scheduled. If meetings are scheduled, the administrator should notify the meeting hosts about the maintenance window. Hosts can then reschedule their meetings for another time, outside of the maintenance window. If a host tries to hold a scheduled meeting anyway, it will be terminated.
If the planned tasks require an extended period of time to complete, such as uploading a new Certificate Authority (CA) certificate, schedule a longer maintenance window. For example, when you schedule your maintenance window, specify a start time of 30 minutes before you plan to turn on Maintenance Mode. This allows a grace period for all meetings to end gracefully. Also we recommend that you add an hour to any maintenance window. The extra time allows the system to become functional after the reboot that might occur. You might also want to start one or more instant meetings to test the modified settings, before the users attempt to schedule or host meetings.
While some system maintenance tasks do not require that you turn on Maintenance Mode, the tasks that do require extra time to complete a restart or a reboot, after you turn off Maintenance Mode. A system restart takes only a few minutes (approximately 3-5 minutes), but a reboot takes approximately 30 minutes. See Turning Maintenance Mode On or Off for more details.
Step 1 | Sign in to Site Administration.
In a Multidata Center system, the DNS determines which data center Dashboard appears. Use this Dashboard to manage all the data centers in this system. |
Step 2 | Select Schedule Maintenance. The Schedule Maintenance Window displays. |
Step 3 | Use the calendar tool and the time drop-down menu to select the date and start time for the maintenance window. |
Step 4 | Enter the duration of the maintenance window by specifying the number of hours and minutes. |
Step 5 | Select Schedule.
When the maintenance window begins, users receive an error message if they attempt to schedule a meeting that falls within the scheduled maintenance window. Scheduling a maintenance window does not automatically put the system into Maintenance Mode; that must be done by an administrator. The scheduled maintenance window date, start time, and duration displays in the Maintenance pane. |
See Emailing Users for details about notifying users of system maintenance events.
After you schedule a maintenance window, you can reschedule the date and time or delete it.
Step 1 | Sign in to Site Administration.
In a Multidata Center system, the DNS determines which data center Dashboard appears. Use this Dashboard to manage all the data centers in this system. |
Step 2 | Select Dashboard. |
Step 3 | Select the displayed system maintenance date and time. |
Step 4 | On the
Schedule
Maintenance Window, you can:
If you finish your system maintenance early, you can either reduce the duration time or select Delete on the Schedule Maintenance Window. |
Turn on Maintenance Mode before you modify system properties. See About Maintenance Mode for information about which system properties require Maintenance Mode to be turned on.
Many configuration changes require that you put your system into Maintenance Mode. Maintenance Mode shuts down all conference functionality on a data center, so you should alert users by scheduling the maintenance windows (see Scheduling a Maintenance Window).
For more information, see Turning Maintenance Mode On or Off.
Putting a data center in Maintenance Mode does the following:
Disconnects users and closes all meetings. If you put a data center that is part of a Multi-data Center (MDC) system into Maintenance Mode, meetings in progress fail over to the active data center.
Prevents users from signing in from web pages, the Outlook plug-in, and mobile applications. Emails are automatically sent when the system is taken out of Maintenance Mode.
Stops access to meeting recordings.
Prevents users from scheduling or hosting meetings.
The system continues to send automatic notification emails to users and administrators.
Use the following table to help determine which tasks require you to turn on Maintenance Mode and the action your system performs after you turn off Maintenance Mode, so you can plan the downtime. When Maintenance Mode is required, the system provides reminder messages if you attempt to perform a task without turning on Maintenance Mode.
Task |
Reference |
Maintenance Mode Required |
Reboot or Restart |
---|---|---|---|
Adding or removing High Availability |
Y |
Reboot |
|
Adding or removing public access |
Adding Public Access to Your System by using IRP or Removing Public Access |
Y |
Restart |
Change the system default language |
Y |
Restart |
|
Changing your host or admin account URLs |
Y |
Restart |
|
Changing your mail server |
N |
N/A |
|
Changing your virtual IP address |
Y |
Reboot |
|
Configuring and changing branding settings |
N |
N/A |
|
Configuring and changing many of the audio settings |
Y |
Restart |
|
Configuring and changing the Call-In Access Numbers, Display Name, and Caller ID audio settings. |
N |
N/A |
|
Configuring and changing quality of service settings |
N |
N/A |
|
Configuring and changing SNMP settings |
Y |
Restart |
|
Configuring certificates |
Y |
Restart or Reboot |
|
Configuring disaster recovery settings |
Y |
Restart |
|
Configuring FIPS-compatible encryption |
Y |
Restart |
|
Configuring storage servers |
Y |
Restart |
|
Configuring virtual machine security |
Y |
Reboot |
|
Expanding system size |
Y |
Restart |
|
Performing updates or upgrades |
Y |
Restart |
|
Updating shared keys |
Y |
Restart |
|
Using the System Resource test |
Y |
Restart |
Each of your virtual machines has a console window that indicates when it is in Maintenance Mode. You can open the console windows in the vCenter inventory bar (for navigation). The console windows provide the URL of the system, type of system (primary, high availability, or public access), type of deployment (50 user, 250 user, 800 user, or 2000 user system), and the current system status including the time and date of the status change. The time displayed is configured in your Company Info settings. See Configuring Company Information for more information.
After you finish modifying your system configuration you can turn off Maintenance Mode. The system monitors the modifications and automatically makes the determination as to whether a restart or a reboot is required. The system displays a message to indicate the requirement:
The changes that you made require a system restart that takes only a few minutes.
The changes that you made require a system reboot that takes approximately 30 minutes, depending on the size of your system. During this time, conference functionality is unavailable.
When Maintenance Mode is off, the Dashboard page refreshes. Your system is ready for users to successfully start meetings when all of the virtual machines, listed on the System Properties page, display a status of Good (green). See Turning Maintenance Mode On or Off for more information.
If Maintenance Mode is off but the scheduled maintenance window is still in effect, users will be able to host and attend previously scheduled meetings, but will not be able to schedule new meetings until after the maintenance window ends.
Turning on Maintenance Mode for all active data centers shuts down conference functionality and prevents users from signing in to the WebEx site, scheduling or joining meetings, and playing meeting recordings. Some actions do not require that all data centers in a Multi-data Center (MDC) environment be put into Maintenance Mode. If you put all of data centers are put into Maintenance Mode, meetings in progress will end. When you turn off Maintenance Mode, the system determines whether a restart (takes approximately 3 - 5 minutes), or a reboot (takes approximately 30 minutes), is required and displays the appropriate message. See About Maintenance Mode for information about which system tasks require Maintenance Mode to be turned on.
Schedule a maintenance window and notify users about the scheduled system maintenance time. See Scheduling a Maintenance Window for details.
Step 1 | Sign in to Site Administration.
In a Multidata Center system, the DNS determines which data center Dashboard appears. Use this Dashboard to manage all the data centers in this system. |
Step 2 | From the Dashboard, select Manage Maintenance Mode. The Manage Maintenance Mode dialog displays. |
Step 3 | Select the data center to put into Maintenance Mode, or deselect the data center to be taken out of Maintenance Mode. |
Step 4 | Select Save. |
Step 5 | (Optional) Back up your virtual machines. |
Step 6 | (Optional) To determine if
the system is fully operational, select
(in the System section).
Conferencing functions can resume when the Status for all of the listed virtual machines is Good (green). |
You can use the HostID and the ConfID values for a meeting to locate the path to the recording for that meeting.
Familiarize yourself with the Network File System (NFS) directory structure.
Step 1 | Obtain the full name of the meeting host, the date and time of the meeting, and the meeting number. |
Step 2 | In CWMS Site Administration, go to Export. The system sends you an email with the and click users.csv file attached. |
Step 3 | In CWMS Site Administration, go to The system sends you an email with the , and then select a time period that includes the date and time when the meeting took place.CustomReport.zip file attached. |
Step 4 | Extract MeetingInformation.csv from the CustomReport.zip file. |
Step 5 | Open the users.csv file and use the name of the host to find the User ID for the host (first column of the file).
The User ID is the same as the HostID used in the directory structure. |
Step 6 | Open the MeetingInformation.csv file, and sort the data by date. |
Step 7 | Search for the Meeting Number and ensure that the details you gathered in Step 1 match. |
Step 8 | Find the Meeting ID value.
The Meeting ID is the same as the ConfID used in the directory structure. |
Step 9 | Use the information that you gathered to construct the path for the recording: NFSstorageIPaddressorFQDNpath/1/HostID%1000/HostID/ConfID%1000/ConfID.
Example: Where UserID=2711 and MeetingID=49782 HostID%1000 of 2711 = 711 HostID = 2711 ConfID%1000 of 49782 = 782 ConfID = 49782 Full path = NFSstorageIPaddressorFQDNpath/1/711/2711/782/49782 |
The Network File System (NFS) storage structure is organized into five directories (folders):
1—This directory contains all consolidated recordings and the following sub-directory structure:
HostID%1000—If the host ID is larger than three digits, this sub-directory name is based on last three digits of the host ID.
HostID—This sub-directory name matches the full host ID and is unique to each user.
ConfID%1000—If the conference ID is larger than three digits, this sub-directory name is based on last three digits of the conference ID.
ConfID—This sub-directory name matches the full conference ID and is unique to each conference. This sub-directory includes the following sub-directories:
RecordingData—This directory contains all of the consolidated recording files required for streaming the recording. Files present are wbxcbr.dat , wbxcbr.idx , wbxcbr.conf , Wbxcbr_tel.wav, wbxmcsr.dat , wbxmcsr.idx , and public.wbxcbr .
RecordingPac—The system creates this directory only after a host downloads the recording file from the WebEx Site. This directory contains an ARF recording file that people can play locally on their PC by using NBR Player.
Condition |
First Sub-directory Name |
---|---|
The host ID or full conference ID is 6534.1 |
534 |
The host ID or full conference ID is 23045.2 |
45 |
The host ID or full conference ID is 35000.3 |
0 |
The host ID or full conference ID is 42.4 |
42 |
Calendar year named directory —For the year 2017 the directory name is 2017. The system creates a new folder for each year. If you have had the CWMS solution for a few years, you can see other directories such as 2016, 2015, and 2014 directories. The system uses this directory to temporarily store meeting recording files during meetings. After a meeting ends, the system consolidates the associated files from this directory and moves them into the directory named 1. This directory contains the following sub-directory structure:
Month (by number) named directory—The system creates a directory for every month of that year (1 to 12).
Conf ID directory—This directory contains the following sub-directories:
Action—This directory contains the .dct recording files for the associated meeting (Conf ID).
Data—This directory contains the .dat and .idx recording files for the associated meeting (Conf ID).
Avatars—The system stores all images for avatars inside this folder.
nfskeepalive—This folder contains files that contain information about the regular checks of component access to NFS storage. There are two types of files in this directory and both are for system use only:
Files with number names –These files are empty.
Files with .nkl extension—Files with names beginning with wbxcb or wbxmcs and having .nkl extensions contain 0.
Snapshot_folder—These directories store the daily backups of the system. The system can create more than one Snapshot_folder. The system takes a backup before running a MINOR update, and these backup files are not automatically deleted from the NFS storage. For every MINOR update run on the system, the system creates a Snapshot_folder with backups taken just before the update was run.