Services - Advanced

Table of Contents

Controlling Services on Windows

Stopping a Service

All services should be in the running state to successfully backup and restore data. Therefore, it is recommended not to stop a service unless absolutely necessary.

Before you begin, verify from the Job Controller that no jobs (like backup, restore, etc.) are in progress. If a job is in the running or waiting state, use the Job Controller to suspend or kill the job before stopping the services. Alternately, you can wait for the job to complete.

Note: Stopping either the CommServe services or the Base services stops all operations on the computer.

Use the following steps to stop a running service:

  1. Click Start and point to All Programs.
  2. Click NetApp, Inc. > Process Manager.
  3. Under the Services tab, right-click a running service and then click Stop.

    A message appears that asks if you want to stop the services.

  4. Click Yes.

Starting a Service

By default, all of the services are running. If a service is stopped manually, start the service using the following steps.

Note: If a service stops unexpectedly, the system automatically attempts to restart the service every two minutes until it starts successfully.

  1. Click Start and point to All Programs.
  2. Click NetApp, Inc. > Process Manager.
  3. Under the Services tab, right-click a stopped service and then click Start.

Restarting a Service

When services are running, manually restart a service using the following steps.

When you restart a service, the dependent services are also restarted. For more information on dependent services, see Service Dependencies.

  1. Click Start and point to All Programs.
  2. Click NetApp, Inc. > Process Manager.
  3. Under the Services tab, right-click a running service and then click Restart.

Controlling Services on UNIX

Services can be stopped or started from a Unix system. The following commands can be used to control services on Unix clients:

Operation Command Description
Starting Services

snapprotect -all start

Use this command to start all the services.

 

snapprotect -instance <inst_name> start

Use this command to start the services for a specific instance.*
 

snapprotect [-force] start

Use this command to forcefully start the services.

This may be needed in certain circumstances such as when services cannot be started due to a partially installed update. In such cases, you can perform one of the following:

  • Use the [-force] option to start the services and then use Automatic Update to install the Service Pack or the Update from the CommServe.
  • Alternatively, install the latest Service Pack. Services will be automatically started after the installation of Service Pack.
Stopping Services

snapprotect -all stop

Use this command to stop all the services.

 

snapprotect -instance <inst_name> stop

Use this command to stop the services for a specific instance.*
Restarting Services

snapprotect -all restart

Use this command to restart all the services.

 

snapprotect -instance <inst_name> restart

Use this command to restart the services for a specific instance.*
Viewing Services

snapprotect -all list

Use this command to view a list all running services.

 

snapprotect -instance <inst_name> list

Use this command to view a list running services for a specific instance.*
Viewing Service Status

snapprotect -all status

Use this command to view information about the client installation.

 

snapprotect -instance <inst_name> status

Use this command to view information about the client installation for a specific instance.
Viewing the CommServe Name

snapprotect -csname

Use this command to display the name of the CommServe associated with the client.

If you have multiple instances, this command displays name of the CommServe associated with each instance.

Getting Help

snapprotect help

Use this command to display help.

* Instance refers to two independent installations of the software on the same machine. Each instance has an independent set of binaries, use different network ports, and may connect to a different CommServe. (Instances do not refer to virtual machines.)

Scheduling Restarts Using Crontab

If services go down during a process (e.g. install, backup, etc.), the snapprotect start command will not restart services unless the command is included in the crontab file.

You can also schedule service restarts using a Crontab file.

Use the following steps to create the Crontab file:

  1. Log on to a client computer as root.
  2. At the command prompt, type the command to edit the crontab file:

    crontab -e

  3. At the command prompt, type the command to display the crontab file:

    crontab -l

  4. Use the following command to schedule a restart - the following example will start the service at 7:00 am on the first day of each month.

    071**/<software installation path>/Base/snapprotect start

    Where 071** indicates the following:

    0 = Minute (0-59)

    7 = Hour (0-23)

    1 = Day of Month (1-31)

    * = Month (1-12 or Jan-Dec)

    * = Day of Week (0-6 or Sun-Sat)

  5. Type :wq to save the changes made.
  6. Alternatively, you can also open the crontab file from the client computer, set the restart time and then save the file.

Controlling Services on Macintosh

You can stop, start, and restart the SnapProtect services from a Macintosh computer using Process Manager.

Stop Services

Use the following steps to stop the SnapProtect services:

  1. Log on to the computer with an administrator account.
  2. Navigate to the /Applications directory and launch Process Manager.
  3. Click the Services tab.
  4. Click to stop services.
  5. A message appears asking if you want to stop services. Click Yes.
  6. Type the user name and password for the administrator account in the Name and Password boxes, and click OK.

    The instances drop-down list is displayed when multiple instances are running on the client.

Start Services

By default, all the services will be in the running state. However, if the services have been stopped manually, use the following steps to start services:

  1. Log on to the computer with an administrator account.
  2. Navigate to the /Applications directory and launch Process Manager.
  3. Click the Services tab.
  4. Click to start services.
  5. Type the user name and password for the administrator account in the Name and Password boxes, and click OK.

    The instances drop-down list is displayed when multiple instances are running on the client.

Restart Services

Use the following steps to manually restart the services:

  1. Log on to the computer with an administrator account.
  2. Navigate to the /Applications directory and launch Process Manager.
  3. Click the Services tab.
  4. Click to restart services.
  5. A message appears asking if you want to restart services. Click Yes.
  6. Type the user name and password for the administrator account in the Name and Password boxes, and click OK.

    The instances drop-down list is displayed when multiple instances are running on the client.

Service Dependencies

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

Action Has the following effect:
Stop all services Stops all services on that system.
Start all services Starts all services on that system.
Stop the Base services Stops all services on that system because all services depend on the Base services.
Start the Base services Starts only the Base services.

Restarting the other services can be done individually or by restarting all services simultaneously.

Stop the CommServe services Stops only the CommServe services.
Start the CommServe services Starts the Base and CommServe services.
Stop the MediaAgent services Stops only the MediaAgent service.
Start the MediaAgent services Starts the Base and the MediaAgent services.
Stop Data Archiver services Stops the CVMHSM service.
Start Data Archiver services Starts the CVMHSM service.
Stop CDR services Stops the CVRepSvc service.
Start CDR services Starts the CVRepSvc service.
Stop VSS Provider Service Stops the GxVSSProv service.
Start VSS Provider Service Starts the GxVSSProv service.

Managing Processes

Each operation in the CommCell Console may have sub-processes associated with the operation. You can view these processes from Process Manager. The Process Manager also displays the Process Identifier (PID) which is a number that uniquely identifies a process while it runs. You can view information about each process like CPU usage, memory usage, start date and time, thread count, etc. You can also perform the following operations.

Creating a Process Dump

You can create a dump file to view the process details.

Use the following steps to create a process dump:

  1. Click Start and point to All Programs.
  2. Click NetApp, Inc. > Process Manager.
  3. Click the Processes tab.
  4. Right-click a process and click Dump.

    An information box appears displaying the path of the created dump file: software_installation_directory/Log Files.

  5. Click OK.

Viewing Process Logs

A log file contains time-stamped events useful to understand the activity of the process and to diagnose problems, if any. For example, on starting a backup operation, an entry is made in the log file. The log file continues to record the events for this operation until the backup is completed or terminated. If the backup operation is abruptly terminated, the log file records this event and may provide troubleshooting information.

Use the following steps to view process logs:

  1. Click Start and point to All Programs.
  2. Click NetApp, Inc. > Process Manager.
  3. Click the Processes tab.
  4. Right-click a process and click View Logs.

    The process logs are displayed in software_installation_directory/Log Files.

Alternatively, view the process logs by using the Filter by option at the bottom of the Process Manager. Search for a process either by Process Name or PID and then click View Logs.

Killing a Process

Use the following steps to terminate a process:

  1. Click Start and point to All Programs.
  2. Click NetApp, Inc. > Process Manager.
  3. Click the Processes tab.
  4. Right-click a process and click Kill.
  5. Click Yes in the warning message box.

    An information box appears displaying that the selected process was killed successfully.

  6. Click OK.

Changing the Priority of Communications Service (Cvd)

By default, the priority of the process started by NetApp Communications Service (CVd) is "normal." You can change the priority of this process using the following steps:

  1. From the CommCell Browser, navigate to the Client Computers node.
  2. Right-click the <Client>, and then click Properties.
  3. On the Client Computer Properties dialog box, click Advanced.
  4. Click the Additional Settings tab and then click Add.
  1. In the Name box of the Add Additional Settings dialog box, type PROCESS_PRIORITY. The Category and Type details will be automatically populated.

    Alternatively, you can click Lookup and search for the additional setting using the Find box.

  2. In the Value box, type either 0 for Normal priority, 1 for Below Normal priority, or 2 for High priority.
  3. Click OK to save the additional setting.
  4. Click OK.

Managing Logging

You can customize some of the parameters for log files, such as the type of log entries included in the files and the size of log files, by adjusting settings on the Logging tab. This is useful if you want to set logging rules for all computers in the CommCell.

Setting the Debug Level

You can limit the type of log entries that appear in the log file in this column. Events that appear in the log file are categorized from 1 to 5, where 1 is the most important, and 5 is the least important.

To set the debug level:

  1. Click Start and point to All Programs.
  2. Click NetApp, Inc. > Process Manager.
  3. Click the Logging tab.
  4. Select the module for which you want to set the debug level.
  5. Under DbgLevel, double-click the cell next to the module name.
  6. Type a number from 1 to 5, and then press Enter.

Setting the Maximum Log File Size

When a log file reaches its maximum size, the file is rolled over to an additional file, <filename>_1.log. You can use this setting to change the maximum size for a log file. Note that file sizes are measured in megabytes (MB).

To set the maximum size for a log file:

  1. Click Start and point to All Programs.
  2. Click NetApp, Inc. > Process Manager.
  3. Click the Logging tab.
  4. Select the module for which you want to set the maximum log file size.
  5. Under LogFileSize (MB), double click the cell next to the module name.
  6. Type a number from 10 to 50, and then press Enter.

Setting the Maximum Number of Log Files

When a log file reaches its maximum size, additional log files are created. You can use this setting to specify the maximum number of additional log files.

To set the maximum number of additional log files:

  1. Click Start and point to All Programs.
  2. Click NetApp, Inc. > Process Manager.
  3. Click the Logging tab.
  4. Select the module for which you want to set the maximum number of additional log files.
  5. Under LogFileMaxVer, double-click the cell next to the module name.
  6. Type a number from 1 to 5, and then press Enter.

Setting the Debug Wait Time

Note: This setting is for developers only. Developers can use this setting to create a delay before the module opens. The delay is commonly used to attach a debugging application to the module. Therefore, this setting is most useful for developers who want to find errors in code. Wait time is measured in seconds.

To set the wait time for a module:

  1. Click Start and point to All Programs.
  2. Click NetApp, Inc. > Process Manager.
  3. Click the Logging tab.
  4. Select the module for which you want to set the wait time.
  5. Under DbgWaitTime, double-click the cell next to the module name.
  6. Type a number, and then press Enter.

Managing Troubleshooting

You can enable Windows error reporting from the Troubleshooting tab. Selecting this option enables error reporting for all Windows clients in the CommCell. The memory dump files are stored in the software_installation_directory\Log Files folder. Up to three files are stored. These memory dump files are read-only text files.

Enabling Windows Error Reporting

Use the following steps to enable Windows error reporting:

  1. Click Start and point to All Programs.
  2. Click NetApp, Inc. > Process Manager.
  3. Click the Troubleshooting tab.
  4. Select the Enable Windows Reporting check box.

Binding Services to a Specific Network Interface Card

By default, the system binds the services to all the available NICs. However, you can bind all services (e.g., Client Event Manager, Communications Service, etc.) to a specific NIC. In a dual or multi-NIC setup where you do not want CommVault® services exposed on the public interface, the following steps allows you to bind all services to the specified interface name or IP address.

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.

Use the following steps to bind the services to a specific NIC in a non-clustered environment:

  1. From the CommCell Browser, navigate to the Client Computers node.
  2. Right-click the <Client>, and then click Properties.
  3. On the Client Computer Properties dialog box, click Advanced.
  4. Click the Additional Settings tab and then click Add.
  1. In the Name field of the Add Additional Settings dialog box, type sBindToInterface. The Category and Type details will be automatically populated.

    Alternatively, you can click Lookup and search for the additional setting using the Find box.

  2. In the Value box, type IP address or host name of the interface to which all services should bind.
  3. Click OK to the additional setting configuration.
  4. Click OK.
  5. Stop and start the services.

Running Services Using a Windows User

CommCell administrators can provide users with the minimal permissions they require to perform their tasks. These permissions can vary, depending on the task each user needs to perform. For example, an administrator can either provide full control to a user or restrict the CommCell objects that a user can view. An administrator can also create/setup permissions for a user to run services and operations.

Viewing or Modifying User Rights Assignment on a Workgroup or Member Server

A CommCell administrator can view or modify user rights assignment on a workgroup or member server. By adding a user/user group to a selected policy, you can allow that user certain rights and permissions associated with that policy. Similarly, to restrict, you can remove a user/user group from a policy. For example, administrator can allow only Backup Operators group to change the system time.

Follow the steps to view or modify user rights assignments on a Workgroup or Member Server:

  1. Click Start > Settings > Control Panel > Administrative Tools.

  2. From Administrative Tools, select the local security policy and add the Service user to all the required rights (logon as service, backup, restore).

Viewing or Modifying User Rights Assignment on a Domain Controller

A CommCell administrator can view or modify user rights assignment on a domain controller. By adding a user/user group to a selected policy, you can allow that user certain rights and permissions associated with that policy. Similarly, to restrict, you can remove a user/user group from a policy. For example, administrator can allow only Backup Operators group to change the system time.

Follow the steps below to view or modify user rights assignments on a domain controller:

  1. Click Start > Settings > Control Panel > Administrative Tools.

  2. From Administrative Tools\Domain Controller Security Policy, expand the tree to Security Settings, Local Policies, and User Rights Assignment. Add the user to all the required rights (logon as service, backup, restore).

Setting Up User Permissions and Rights on a Windows Workgroup or Member Server

By default, services run as a local system account. However, an administrator can create a user to run services and operations only for the Windows File System iDataAgent and SQL Server iDataAgent. This is useful if you are troubleshooting service failures or if you need to change the security account under which a service runs. The created user can run services to back up and restore files and folders regardless of ownership, permissions, encryption, or auditing settings.

To run services, a user can be assigned to built-in groups like Backup Operators, Administrator and Local Administrator. These groups have the necessary permissions and user rights defined to perform a specific task. Only a member of the Administrator group can assign users as Backup Operators.

To add a user to the Backup Operators Group, perform the following steps on an individual server:

  1. Navigate to Start | Settings | Control Panel | Administrative Tools.
  2. Double-click Computer Management.
  3. Navigate to Local User and Groups | Users.
  4. Right-click the user who will be performing backups and click Member of.
  5. Add the Backup Operators group to the User.
  6. Click OK.
  7. Log off and log in as the domain controller Administrator for the policies to take effect.

Setting Up Folder Permissions

A CommCell administrator can provide a user with full control to the installation directory. The default location of the installation directory is C:\Program Files\company_name.

Use the following steps to set up folder permissions:

  1. Go to the C:\Program Files\company_name folder.
  2. Right-click the folder and select Properties.

    The properties dialog box appears.

  3. Select the Security tab and click Edit.

    The Permissions dialog box appears.

  4. Select a group or a user and select the Allow check box next to Full control.
  5. Click OK.

Command Line Operations

Restarting Client Services

Use the following steps to restart the SnapProtect services of a client computer.

  1. Download the restart_client.xml file and save it on the CommServe computer.
  2. From the command prompt, go to software_installation_directory/Base and run the following command:

    qlogin -u <user name>

  3. Execute the following command to restart the services of a client:

    qoperation execute -af restart_client.xml -clientName xxxxx

    where clientName is the name of the client where you want to restart services.