Services

Topics | How To | FAQs | Related Topics

Overview

Service Dependencies

TCP Ports Used for Services

• Static Ports
• Dynamic Ports

Binding Services to Specific Network Interface Cards (NIC)

• CommServe Computers in Clustered Environments

Service Control

• Service Control for Windows
• Service Control on Windows Cluster
• Running Services Using a Windows User
• Service Control for Unix
• Service Control for NetWare
• Service Control for Content Indexing

GxAdmin Tool

Overview

Several services are required by the software to function. For example, all computer configurations minimally require the Base services to be running. CommServe services are installed exclusively on the CommServe computer, and MediaAgent services are installed exclusively on the MediaAgent computer. The following table describes the various CommCell components and the appropriate services that are required. Note that these services are automatically installed when the appropriate software is installed on the computer.

Service Dependencies

When a system has more than one CommCell component, the service dependencies are as follows:

TCP Ports Used for Services

Base Services provide the key communications and control link between components. These services are assigned registered network port numbers and are identified in the /Windows/System32/Drivers/etc/Services file as Static Ports and Dynamic Ports.

Static Ports

For types of static ports, see Network TCP Port Requirements.

Dynamic Ports

Cvd sessions also use free ports between 5000 and 32767 for communication during data protection and data recovery jobs. The system will dynamically assign a number of free ports to be used by each job to allow parallel data movement. The client, CommServe, and MediaAgent all send job related communications using that port number. Once the job is finished and no other job is pending, the dynamic ports are released.

For more information about ports used by the system, see Network TCP Port Requirements.

Binding Services to Specific Network Interface Cards (NIC)

By default the system binds the services to all the available NICs. You can however, bind the services to a specific NIC using the steps described below. Note that this operation is not recommended for clustered computers. (In a clustered environment, failover will not work if the services are bound to a specific NIC.)

1. Create the sBindToInterface registry key on the computer and provide the host name or IP address of the interface to which all services should bind.
2. Stop and start the services.

(Note that the system also allows you to define the interface pairs for data transfer between any two computers. See Data Interface Pairs for more details.)

CommServe Computers in Clustered Environments

For CommServe computers in clustered environments, you can bind known-port services (such as CVD, EvMgrC, EvMgrS, and QSDK) to specific IP address and/or host names. Use the following steps to bind services using this feature.

1. Create the IPsToBind.txt file in the <Install Directory>\Base folder.
2. Add the IP address or the interface name associated with the NIC cards(s) that must be used.

   There must be one entry per line, as shown in the following example:

   123.45.67.895

   interface1.company.com

3. Save the file and then stop and start the services.

Service Control

Service Control for Windows

The Service Control Manager can be used to stop and start services used by the system on Windows. Services on any Windows client computer within the CommCell can also be stopped and started remotely from another Windows client computer within the CommCell. The Service Control Manager window includes the following fields:
Computer	The host computer of the services.
Services	Allows you to select either All Services, Base Services, CommServe Services, or MediaAgent Services. The All Services option starts (or stops) all services on the local computer, regardless of the components you have installed.
Base Services	Either stopped or running.
CommServe Services	Either stopped or running.
MediaAgent Services	Either stopped or running.
Data Archiver Services	Either stopped or running.
CDR Services	Either stopped or running.
VSS Provider Service	Either stopped or running.
CommNet Service	Either stopped or running.
Start/Stop Data Classification Services With All Services	If selected, and all services on the local computer are started (or stopped), then all Data Classification Enabler services will start (or stop) as well.
Auto-Start Services when OS Starts	If selected, all services applicable to the local system will start automatically when the system is started. If cleared, the services must be started manually.
Retrieve Remote Clients	If selected, the Computer field is populated with the names of all the remote Windows client computers within the CommCell. From this field you can remotely stop or start services from any selected Windows client computer within the Computer field. This feature is not support for Clients installed with an IP address, and Clients on Windows 64-bit computers.

Service Control on Windows Cluster

A clustered environment that is not a Windows cluster (VERITAS, Polyserve, etc.) requires that each physical node bind only to that node's specific IP address. Each physical node needs an IPsToBind.txt file in the Base directory. This will force the services on each node to bind to the node's IP address and not the virtual machine IP address. This is not necessary in a Windows clustered environment.

Running Services Using a Windows User

You can create a User (and not the local system account) to run services and operations only for the Windows File System iDataAgents and SQL Server iDataAgent. By default, services run as a local system account. The created User will run services to back up and restore files and folders regardless of ownership, permissions, encryption, or auditing settings.

The User will use several built-in groups, including Backup Operator, Administrator, and Local Administrator. These groups have the necessary permissions and user rights defined. Only a member of the Administrator group can assign users as Backup Operators.

Warning: You may be required to edit the registry. However, before you do this, back it up and ensure that you understand how to restore it if a problem occurs. For information about how to do this, view Windows Help on the "Restoring the Registry" from Microsoft Help topic in Regedit.exe or the "Restoring a Registry Key" Help topic in Regedt32.exe.

See User Accounts and Passwords: Considerations When Using a Windows User to Run Operations for more information along with the following procedures:

• View or Modify User Rights Assignments on a Workgroup or Member Server
• View or Modify User Rights Assignments on a Domain Controller
• Set up User Permissions and Rights on a Windows Workgroup or Member Server
• Set up Folder Permissions

Service Control for Unix

The services can be stopped or started from a Unix system. However, only one instance of start/stop services at a time is allowed on the system. If you attempt more than one such instance, the appropriate error message is displayed. The following commands can be used to start and stop services:

Service Control for NetWare

Services used by the system can be stopped or started from the NetWare Server using the Load/Unload commands, or from a remote Novell Client PC using the NetWare Service Manager. The NetWare Service Manager window includes the following fields: NW Servers Allows you to select the name of the NetWare server for service control. Services Allows you to select either All Services, Base Services, or MediaAgent Services. The All Services option starts (or stops) all services on the local computer, regardless of the components you have installed. Refresh Services Allows you to refresh the selected services. NLM Status Displays the current status of the NetWare Loadable Module (NLM).

Service Control for Content Indexing

For information on controlling the services for Content Indexing, see Content Indexing Services.

GxAdmin Tool

GxAdmin is a real-time CommCell administration tool used to view, monitor, and administer the various services and processes of the CommCell components on local and remote Windows computers.

This tool is available at the <Install Directory>/base folder, on Windows computers. The tool contains the following tabs:

General

The general tab displays the CommCell deployment details such as Instance Name, CommServe Host Name, Client Name, and the Client Host Name. It also provides the configuration details of each CommCell component installed.

The following details are displayed:

• Software version
• Installation directory
• Total space and free space on the disk
• Job Results directory (for clients), Index Cache (for MediaAgents), and database details (for CommServe).

By default, details of the local client are displayed. You can also view the details of remote clients. See Use GxAdmin to View Remote Clients for instructions.

Services

The services tab displays the list of services along with the instance name and the status of the service, for each CommCell component. The individual services can be managed. See Use GxAdmin to Start/Stop Services for step-by-step instructions.

Processes

The processes tab displays the list of CommCell processes that are currently running. Process details such as start time, memory used, thread count, and handle count are displayed. The log details of the process can be stored in a dump file and used for troubleshooting purposes. See Use GxAdmin to Create Process Dump for step-by-step instructions.

Log Params

The Log Params tab displays the log parameter details such as the debug level, log file size, maximum log file version, and debug wait time, for each module. You can use the Log Params tab to configure log parameters. See Use GxAdmin to Set Log Parameters for instructions.

Back To Top