About backing up and restoring Symantec Workflow (and ServiceDesk)

book

Article ID: 181101

calendar_today

Updated On:

Products

Workflow Solution ServiceDesk

Issue/Introduction

 

Resolution

Whether you run only Symantec Workflow or you run ServiceDesk Solution on Symantec Workflow, you may need to back up and restore data. For example, if the Process Manager database has been corrupted through application error or through hard drive failure, you must restore the database. Both backing up and restoring require thoughtful planning. 

A number of architectural components of a workflow cannot be backed up while the system is in use. This limitation is due to the nature of the product: ServiceDesk Solution, which is built on the Symantec Workflow platform, cannot be backed up and restored with 100% of the data correctly in place. The details regarding these limitations are explained in the appropriate sections of the text.

The following infrastructure diagram provides the context on which the recommended backup and restore methods are based.

Information about the recommended backup and restore methods are based primarily on ServiceDesk, Symantec Workflow, IIS 7.5, and the Process Manager database. This information does not account for failure of Symantec Management Platform, nor does it include details about specialized configurations or customizations.

Preparing to back up Workfow or ServiceDesk

Although the process of backing up ServiceDesk and custom Workflows is relatively easy, restoring can be complex because some data may be lost. Data loss is due to the inherent workflow architecture with the message bus. To minimize the effect of an outage, Symantec recommends that you use a clustered Microsoft SQL environment. If you use ServiceDesk, include in your backup plan the appropriate failover and fault-tolerant hardware for ServiceDesk.

To minimize data loss, carefully consider which data to back up within ServiceDesk or Symantec Workflow projects. To restore data successfully, it is essential to identify which components of Symantec Workflow you must back up:

  • Process Manager database. Symantec Workflow projects and ServiceDesk Solution use this database.
    For performance reasons Symantec recommends that you use a simple recovery model, as follows:
    • Description: The transaction log is not backed up.
    • Possibility of data loss: Changes since the most recent backup are unprotected. In the event of a disaster, you must re-do the changes that were made since the most recent backup.
      To minimize data loss, place the database on a RAID 10 or similarly configured drives.
    • Recovery point: You can recover data only to the end of a backup, so use a short backup interval to prevent loss of significant amounts of data. Symantec recommends that you consider using Symantec NetBackup or Symantec Backup Exec, depending on the specific needs of the environment, for your regular backups.
       
  • SymQ messaging bus. SymQ provides a messaging bus architecture that all Symantec Workflow projects leverage. ServiceDesk also uses this message bus:
    • The messaging bus lets you orchestrate data and move it through your environment.
    • A bus can point to files, memory, a database that is located on another server, or even to a NULL (empty) pointer.
    • The bus acts like a data highway, and like any highway traffic can build up when data travels between two points at one time.
    • To minimize data loss, shut down the Web services and Symantec Workflow Server service before you capture the core configuration.
    • You must capture the core configuration data of the message bus every time you perform a backup. To capture the configuration details of SymQ for Symantec Workflow, back up the following directory: C:\Program Files\Symantec\Workflow\Data
       
  • Symantec Workflow Server. This Windows service is the core engine of Symantec Workflow; consequently, ServiceDesk also uses it.
    • This service performs a heavy processing load. Therefore, you should shut it down before you perform a backup.
      Shutting down the service prevents it from processing data while you back up the database or the workflow messaging environment. The shutdown helps prevent data loss.
    • Because the process flows rely on the Workflow Server service, when you shut it down some data is left in SymQ. Some of this data may be lost during a restore because there is no
      way to ensure that it is flushed to the database.
    • To verify that you have shut down the service, check Symantec Workflow Explorer. When you run Symantec Workflow Explorer, you see the following processes under the Current Running Processes menu selection: LogicBase.ServerExtensions andw3wp. When the Symantec Workflow Server service is stopped, the running processes completely disappear from the window. The empty window indicates that processing has stopped.
       
  • IIS 7.5. When published, each Symantec Workflow project creates a virtual folder on the IIS server; therefore, the w3wp process of IIS serves each running workflow.
    Symantec recommends that you stop the default Web site before backing up to ensure that all user interaction is completely inactive during backup.
    • Back up the metadata that can be backed up using the APPCMD command, which is in the C:\Windows\System32\inetsrv directory.
      To perform the backup, run the following command from the C:\Windows\System32\inetsrv directory: %systemroot%\system32\inetsrv\APPCMD add backup
      The output, BACKUP object "20110901T000430", is added to the C:\Windows\System32\inetsrv\backup\20110901T000430 directory.
    • To restore a backup run the following command: %systemroot%\system32\inetsrv\APPCMD restore backup "20110901T000430"

    • To view backups, you can
      • Run the %systemroot%\system32\inetsrv\APPCMD list backups command. The following files are backed up by the APPCMD command are stored under %systemroot%\system32\inetsrv:
        • administration.config
        • applicationHost.config
        • MBSchema.xml
        • MetaBase.xml
        • redirection.config
      • The Application Host Helper Service backs up the Schema and Metabase by default. See the History folder, under the inetsrv directory, to view these backups.
         
  • If you have installed or created your own workflows, you see them when you run the enumvdirs localhost > SD.VirtualDirs.txt command. If you need to rebuild your environment, you must republish those workflows that you created yourself. 
     
  • Any customizations you have made within ServiceDesk are lost if you run through the ServiceDesk installation process again. To ensure that your customizations are retained, create a backup of the directory path of all listed flows that the script located. Use the backup to restore your customizations after the ServiceDesk installation process is finished.
     
  • Ensure that the required virtual Web sites exist.  You can use the following script to generate the Web sites on your local IIS server: enumvdirs localhost > SD.VirtualDirs.txt
    To create the script and generate the Web sites,
    1. Create a file named enumvdirs.cmd.
    2. Open this link to Symantec Knowledge Base article TECH173381, and copy the contents of the attachment into your enumvdirs.cmd file.
    3. After you have created the enumvdirs command file with the code found in the attachment, execute the file to create a TXT file named SD.VirtualDirs.txt. Use the following syntax:
      enumvdirs localhost > SD.VirtualDirs.txt
    4. If only ServiceDesk is installed on the computer that you use, this text file is 7,249 bytes in size. Study the output and ensure that at a minimum the information exists before you attempt to restore any data in the environment.

The required Web sites are as follows (this list is a minimum):

localhost/W3SVC/1/ROOT = "C:\inetpub\wwwroot"
localhost/W3SVC/1/ROOT/SymWebInclude = "C:\Program Files\Symantec\Workflow\Shared\scripts"
localhost/W3SVC/1/ROOT/SymWorkflowPages = "C:\Program Files\Symantec\Workflow\Workflow Pages"
localhost/W3SVC/1/ROOT/SD.ReopenIncident = "C:\Program Files\Symantec\Workflow\WorkflowDeploy\Release\SD.ReopenIncident"
localhost/W3SVC/1/ROOT/SD.KnowledgeBaseSearch = "C:\Program Files\Symantec\Workflow\WorkflowDeploy\Release\SD.KnowledgeBaseSearch"
localhost/W3SVC/1/ROOT/SD.EmailServices = "C:\Program Files\Symantec\Workflow\WorkflowDeploy\Release\SD.EmailServices"
localhost/W3SVC/1/ROOT/SD.DataServices = "C:\Program Files\Symantec\Workflow\WorkflowDeploy\Release\SD.DataServices"
localhost/W3SVC/1/ROOT/SD.CloseIncidents = "C:\Program Files\Symantec\Workflow\WorkflowDeploy\Release\SD.CloseIncidents"
localhost/W3SVC/1/ROOT/SD.AssetViewProject = "C:\Program Files\Symantec\Workflow\WorkflowDeploy\Release\SD.AssetViewProject"
localhost/W3SVC/1/ROOT/SD.AttachProcessToChange = "C:\Program Files\Symantec\Workflow\WorkflowDeploy\Release\SD.AttachProcessToChange"
localhost/W3SVC/1/ROOT/SD.LoginFailureForm = "C:\Program Files\Symantec\Workflow\WorkflowDeploy\Release\SD.LoginFailureForm"
localhost/W3SVC/1/ROOT/SD.RoutingRules = "C:\Program Files\Symantec\Workflow\WorkflowDeploy\Release\SD.RoutingRules"
localhost/W3SVC/1/ROOT/SD.BulletinBoardEntry = "C:\Program Files\Symantec\Workflow\WorkflowDeploy\Release\SD.BulletinBoardEntry"
localhost/W3SVC/1/ROOT/SD.IncidentEscalation = "C:\Program Files\Symantec\Workflow\WorkflowDeploy\Release\SD.IncidentEscalation"
localhost/W3SVC/1/ROOT/SD.ManageRecurringChanges = "C:\Program Files\Symantec\Workflow\WorkflowDeploy\Release\SD.ManageRecurringChanges"
localhost/W3SVC/1/ROOT/SD.IMRemoveFromHold = "C:\Program Files\Symantec\Workflow\WorkflowDeploy\Release\SD.IMRemoveFromHold"
localhost/W3SVC/1/ROOT/SD.CreateChatTask = "C:\Program Files\Symantec\Workflow\WorkflowDeploy\Release\SD.CreateChatTask"
localhost/W3SVC/1/ROOT/SD.NotifyGroupsOnArticleCreation = "C:\Program Files\Symantec\Workflow\WorkflowDeploy\Release\SD.NotifyGroupsOnArticleCreation"
localhost/W3SVC/1/ROOT/SD.ProblemManagement = "C:\Program Files\Symantec\Workflow\WorkflowDeploy\Release\SD.ProblemManagement"
localhost/W3SVC/1/ROOT/SD.IncidentManagement = "C:\Program Files\Symantec\Workflow\WorkflowDeploy\Release\SD.IncidentManagement"
localhost/W3SVC/1/ROOT/SD.ChangeManagement = "C:\Program Files\Symantec\Workflow\WorkflowDeploy\Release\SD.ChangeManagement"
localhost/W3SVC/1/ROOT/SD.KBSubmission = "C:\Program Files\Symantec\Workflow\WorkflowDeploy\Release\SD.KBSubmission"
localhost/W3SVC/1/ROOT/SD.CustomerServiceSurvey = "C:\Program Files\Symantec\Workflow\WorkflowDeploy\Release\SD.CustomerServiceSurvey"
localhost/W3SVC/1/ROOT/SD.Feeder.ProblemCreation = "C:\Program Files\Symantec\Workflow\WorkflowDeploy\Release\SD.Feeder.ProblemCreation"
localhost/W3SVC/1/ROOT/SD.Feeder.KnowledgeBase = "C:\Program Files\Symantec\Workflow\WorkflowDeploy\Release\SD.Feeder.KnowledgeBase"
localhost/W3SVC/1/ROOT/SD.Feeder.ChangeManagement = "C:\Program Files\Symantec\Workflow\WorkflowDeploy\Release\SD.Feeder.ChangeManagement"
localhost/W3SVC/1/ROOT/SD.Feeder.CloneChange = "C:\Program Files\Symantec\Workflow\WorkflowDeploy\Release\SD.Feeder.CloneChange"
localhost/W3SVC/1/ROOT/SD.ReoccurringChangeMonitor = "C:\Program Files\Symantec\Workflow\WorkflowDeploy\Release\SD.ReoccurringChangeMonitor"
localhost/W3SVC/1/ROOT/SD.Remediation = "C:\Program Files\Symantec\Workflow\WorkflowDeploy\Release\SD.Remediation"
localhost/W3SVC/1/ROOT/SD.FollowTheSun = "C:\Program Files\Symantec\Workflow\WorkflowDeploy\Release\SD.FollowTheSun"
localhost/W3SVC/1/ROOT/SD.Feeder.WindowsEventMonitor = "C:\Program Files\Symantec\Workflow\WorkflowDeploy\Release\SD.Feeder.WindowsEventMonitor"
localhost/W3SVC/1/ROOT/SD.Feeder.TechnicianIncidentForms = "C:\Program Files\Symantec\Workflow\WorkflowDeploy\Release\SD.Feeder.TechnicianIncidentForms"
localhost/W3SVC/1/ROOT/SD.Feeder.GeneralIncidentSubmitForm = "C:\Program Files\Symantec\Workflow\WorkflowDeploy\Release\SD.Feeder.GeneralIncidentSubmitForm"
localhost/W3SVC/1/ROOT/SD.Email.Monitor = "C:\Program Files\Symantec\Workflow\WorkflowDeploy\Release\SD.Email.Monitor"
localhost/W3SVC/1/ROOT/SD.Email.InboundManagement = "C:\Program Files\Symantec\Workflow\WorkflowDeploy\Release\SD.Email.InboundManagement"
localhost/W3SVC/1/ROOT/SD.Feeder.CreateIncidentForAssetInNS = "C:\Program Files\Symantec\Workflow\WorkflowDeploy\Release\SD.Feeder.CreateIncidentForAssetInNS"
localhost/W3SVC/1/ROOT/UpgradePIWSetup = "C:\Program Files\Symantec\Workflow\WorkflowDeploy\Release\UpgradePIWSetup"
localhost/W3SVC/1/ROOT/SD.CreateSampleData = "C:\Program Files\Symantec\Workflow\WorkflowDeploy\Release\SD.CreateSampleData"
localhost/W3SVC/1/ROOT/SD.MonitorMigratedIncidents = "C:\Program Files\Symantec\Workflow\WorkflowDeploy\Release\SD.MonitorMigratedIncidents"
localhost/W3SVC/1/ROOT/SD.IncidentMigrator = "C:\Program Files\Symantec\Workflow\WorkflowDeploy\Release\SD.IncidentMigrator"
localhost/W3SVC/1/ROOT/SD.Feeder.CABVoting = "C:\Program Files\Symantec\Workflow\WorkflowDeploy\Release\SD.Feeder.CABVoting"
localhost/W3SVC/1/ROOT/SD.IncidentMigrationWizard = "C:\Program Files\Symantec\Workflow\WorkflowDeploy\Release\SD.IncidentMigrationWizard"
localhost/W3SVC/1/ROOT/SD.CategoryMigrationWizard = "C:\Program Files\Symantec\Workflow\WorkflowDeploy\Release\SD.CategoryMigrationWizard"
localhost/W3SVC/1/ROOT/SD.KBMigrationProcess = "C:\Program Files\Symantec\Workflow\WorkflowDeploy\Release\SD.KBMigrationProcess"
localhost/W3SVC/1/ROOT/SD.KBMigrationWizard = "C:\Program Files\Symantec\Workflow\WorkflowDeploy\Release\SD.KBMigrationWizard"
localhost/W3SVC/1/ROOT/SD.PlugIn.DiscussionsThreadNotification = "C:\Program Files\Symantec\Workflow\WorkflowDeploy\Release\SD.PlugIn.DiscussionsThreadNotification"
localhost/W3SVC/1/ROOT/SD.ChatInvitationEventListener = "C:\Program Files\Symantec\Workflow\WorkflowDeploy\Release\SD.ChatInvitationEventListener"
localhost/W3SVC/1/ROOT/SD.AccountEventListener = "C:\Program Files\Symantec\Workflow\WorkflowDeploy\Release\SD.AccountEventListener"
localhost/W3SVC/1/ROOT/SD.DiscussionEventListener = "C:\Program Files\Symantec\Workflow\WorkflowDeploy\Release\SD.DiscussionEventListener"
localhost/W3SVC/1/ROOT/SD.CalendarEventListener = "C:\Program Files\Symantec\Workflow\WorkflowDeploy\Release\SD.CalendarEventListener"
localhost/W3SVC/1/ROOT/SD.ArticlesEventListener = "C:\Program Files\Symantec\Workflow\WorkflowDeploy\Release\SD.ArticlesEventListener"
localhost/W3SVC/1/ROOT/SD.DocumentEventListener = "C:\Program Files\Symantec\Workflow\WorkflowDeploy\Release\SD.DocumentEventListener"
localhost/W3SVC/1/ROOT/SD.DocumentEventListener = "C:\Program Files\Symantec\Workflow\WorkflowDeploy\Release\SD.DocumentEventListener"
localhost/W3SVC/1/ROOT/SD.CreateRoutingRules = "C:\Program Files\Symantec\Workflow\WorkflowDeploy\Release\SD.CreateRoutingRules"
localhost/W3SVC/1/ROOT/SD.RequestAccessToNetworkShare = "C:\Program Files\Symantec\Workflow\WorkflowDeploy\Release\SD.RequestAccessToNetworkShare"
localhost/W3SVC/1/ROOT/SD.ResetPassword = "C:\Program Files\Symantec\Workflow\WorkflowDeploy\Release\SD.ResetPassword"
localhost/W3SVC/1/ROOT/ProcessManager = "C:\Program Files\Symantec\Workflow\ProcessManager"
 

If any of the preceding sites do not appear in the backed-up database, then you must install the files again, but run only the core Workflow installer process. Do not run the Post
Installation Wizard for ServiceDesk! 
Follow the instructions in the Symantec Knowledge Base, in article HOWTO49691, starting at page 16.

Backing up Workflow or ServiceDesk

The recommended method for backing up your ServiceDesk environment and Symantec Workflow projects is as follows. The steps to accomplish each task follow this list:

  1. Shut down the Symantec Workflow Server service.
  2. Stop the Default Web site. When you stop this site, you ensure that all user interaction on the site is completely inactive while the environment is backed up.
    Following is a list of the virtual Web sites that must exist when you restore a database.
  3. Create the backup.
  4. Restart the Default Web site.
  5. Restart the Symantec Workflow Server service.

To shut down the Symantec Workflow Server service

  1. On the server, start the Microsoft Management Console.
  2. Click Services (Local).
  3. Navigate to Symantec Workflow Server service and click it.
  4. Under Application Experience, click Stop the service.

To stop the Default Web site

  1. On the server, start Internet Information Services (IIS) Manager.
  2. In the left pane, under the server name, under Sites, click Default Web Site.
  3. In the Manage Web Site dialog box, click Stop.

To back up ServiceDesk or Workflow

  1. On the server, in the Microsoft Management Console, open a command prompt and run the %systemroot%\system32\inetsrv APPCMD add backup command. You run this command to ensure that you have a current backup of the metabase, as follows: C:\Windows\system32\inetsrv > APPCMD add backup
  2. Add the %systemroot%\system32\inetsrv to your backup directory path. (Refer to your vendor-specific backup documentation if you need details about how to perform this step or subsequent backup tasks.)
  3. Back up the directory path of SymQ, which is C:\Program Files\Symantec\Workflow\Data.
  4. Back up the location of your ServiceDesk workflows. These workflows are typically located at C:\Program Files\Symantec\Workflow\WorkflowDeploy.
  5. Locate and back up any additional workflows that you have created.
  6. In Microsoft SQL Server Management Studio, look at the properties of the database named Process Manager to locate the database files to back up.
  7. Make a backup of the Process Manager database.

To restart the Default Web Site

  1. On the server, start Internet Information Services (IIS) Manager.
  2. In the left pane, under the server name, under Sites, click Default Web Site.
  3. In the Manage Web Site dialog box, click Start.

To restart the Symantec Workflow Server service

  1. On the server, start the Microsoft Management Console.
  2. Open Services (Local).
  3. Navigate to the Symantec Workflow Server service, and under Application Experience click Restart the service.

Restoring the Workflow Process Manager database after a failure

The recommended method for restoring the database is as follows. The steps to accomplish each task follow this list:

  1. Shut down the Symantec Workflow Server service. Follow the procedure shown above.
  2. Stop the Default Web site. Follow the procedure shown above.
  3. Create backups.
  4. Restart the Default Web site.
  5. Restart the Symantec Workflow Server service.

To shut down the Symantec Workflow Server service

  1. On the server, start the Microsoft Management Console.
  2. Click Services (Local).
  3. Navigate to Symantec Workflow Server service and click it.
  4. Under Application Experience, click Stop the service.

To stop the Default Web site

  1. On the server, start Internet Information Services (IIS) Manager.
  2. In the left pane, under the server name, under Sites, click Default Web Site.
  3. In the Manage Web Site dialog box, click Stop.

To back up ServiceDesk or Workflow

  1. On the server, in the Microsoft Management Console, open a command prompt and run the %systemroot%\system32\inetsrv APPCMD add backup command. You run this command to ensure that you have a current backup of the metabase, as follows: C:\Windows\system32\inetsrv > APPCMD add backup
  2. Add the %systemroot%\system32\inetsrv to your backup directory path. (Refer to your vendor-specific backup documentation if you need details about how to perform this step or subsequent backup tasks.)
  3. Back up the directory path of SymQ, which is C:\Program Files\Symantec\Workflow\Data.
  4. Back up the location of your ServiceDesk workflows. These workflows are typically located at C:\Program Files\Symantec\Workflow\WorkflowDeploy.
  5. Locate and back up any additional workflows that you have created.
  6. Take one of the following actions, depending on the nature of the failure:
    1. If a hard drive failed, install Microsoft SQL Server 2008 R2. Refer to the Microsoft Web site at http://msdn.microsoft.com/en-us/library/ms143219.aspx. Note that if you use a different version of Microsoft SQL, you should locate the correct installation documentation.
    2. If a database was corrupted, stop the Microsoft SQL Server Instance by performing the following steps:
      • Start Microsoft SQL Server Management Studio.
      • Right-click the SQL Instance that is running on your Microsoft SQL Server, and click Stop.
  7. Restore the Process Manager MDF files and LDF files. These files are located in the Microsoft SQL Server Management Studio.
  8. Start Microsoft SQL Server Management Studio, right-click the SQL Instance that is running on your Microsoft SQL Server, and click Start.
    Ensure that the database can be accessed and is attached.
  9. Restore theSymQC:\Program Files\Symantec\Workflow\Data directory path.

To restart the Default Web Site

  1. On the server, start Internet Information Services (IIS) Manager.
  2. In the left pane, under the server name, under Sites, click Default Web Site.
  3. In the Manage Web Site dialog box, click Restart.

To restart the Symantec Workflow Server service

  1. On the server, start the Microsoft Management Console.
  2. Open Services (Local).
  3. Navigate to the Symantec Workflow Server service, and under Application Experience click Restart the service.

Restoring the ServiceDesk server after a failure

You may need to restore a server after a ServiceDesk IIS failure or a Workflow Server failure. If the data disks or the entire operating system of your ServiceDesk server fails, you must run a base installation. Restoring a ServiceDesk or Workflow Server means that you get it up and running again.

Restoring your server involves the following main steps:

  1. Back up the current Process Manager database. You need this backup later in your restore process.
  2. Detach the Process Manager database from the server.
  3. Reinstall the ServiceDesk server.
  4. Restart the Default Web site.
  5. Restart the Symantec Workflow Server service.

The following procedures are based on the assumption that the operating system functions and that IIS 7.5 Web Services have been installed and restarted.

To back up the current Process Manager database

  1. Open Microsoft SQL Server Management Studio.
  2. Navigate to the Process Manager database files in the Microsoft SQL Server Management Studio as you did when you backed them up.
  3. In Microsoft SQL Server Management Studio, look at the properties of the database named Process Manager to locate the database files to back up.
  4. Make a backup of the Process Manager database.

To detach the Process Manager database

  1. Start the Microsoft SQL Server Management Studio.
  2. Right-click the Process Manager database and click Tasks > Detach.
  3. Store the LDF files and MDF files in an easily accessible location on your server hard drive.

To reinstall the ServiceDesk server

  1. Perform a new installation of ServiceDesk.
    Refer to the Symantec Knowledge Base article HOWTO49691 for ServiceDesk installation information.
  2. Shut down the Symantec Workflow Server service. On the ServiceDesk server start the Microsoft Management Console and open Services (Local).
  3. Under Services (Local), navigate to the Symantec Workflow Server Service and click Stop the service.
  4. Stop the WWW Services. On the ServiceDesk server start the Microsoft Management Console and open Services (Local).
  5. Under Services(Local), navigate to the WorldWideWebPublishingService and click Stop the service.
  6. Start the Microsoft SQL Server Management Studio to delete the newly created Process Manager database on the SQL Server.
  7. Under Databases right-click Process Manager and click Delete.
  8. Copy the original Process Manager database back onto the SQL Server.
    To copy the database copy the LDF files andMDFfiles to the original location. The files are accessible through the Microsoft SQL Server Management Studio.
  9. Start the Microsoft SQL Server Management Studio to attach the original Process Manager database to the SQL Server.
  10. Right-click the Database folder and click Attach.
  11. Click Add and locate the Process Manager MDF and LDF files. Then click OK to attach the files again.
  12. Restore the %systemroot%\system32\inetsrv directory.
    Refer to vendor-specific information for details about how to perform this step.
  13. Restore the SymQ C:\Program Files\Symantec\Workflow\Data directory.
  14. Restore your ServiceDesk workflows from your backup media to the C:\Program Files\Symantec\Workflow\WorkflowDeploy directory.
    Expect to overwrite some content. The purpose of this step is to restore the original ServiceDesk changes that you made to your system as they were before the failure.

To restart the World Wide Web Publishing Service on the ServiceDesk server

  1. On the ServiceDesk server, start the Microsoft Management Console.
  2. Open Services (Local).
  3. Navigate to the World WideWebPublishing Service and under Applicaton Experience click Restart the service.

To restart the Symantec Workflow Server service

  1. On the ServiceDesk server, start the Symantec Workflow Server service.
  2. Open Services (Local).
  3. Navigate to the Symantec Workflow Server service, and under Applicaton Experience click Restart the service.

For additional information about Symantec backup and backup products, see https://www-secure.symantec.com/business/index.jsp.

 

Attachments