IIS 7.5

Article:HOWTO62380

Created: 2011-12-13

Updated: 2011-12-20

Article URL http://www.symantec.com/docs/HOWTO62380

Article Type
How To

Product(s)

Show all

Subject

Show all

Languages

Show all

IIS 7.5

The core pieces of IIS that you should consider are the metadata that you can back up using the appcmd command. The appcmd command is located in the C:\Windows\System32\inetsrv directory directory.

See Preparing to back up.

To perform a 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 list all backups execute the %systemroot%\system32\inetsrv\APPCMD list backups command.

To restore a backup run the following command: %systemroot%\system32\inetsrv\APPCMD restore backup "20110901T000430"

The following files are found in the directory that is located under %systemroot%\system32\inetsrv and are backed up by the APPCMD command:

administration.config
applicationHost.config
MBSchema.xml
MetaBase.xml
redirection.config

By default in IIS 7.5 the Application Host Helper Service performs backups of the Schema and Metabase. These backups are located in the History folder under the inetsrv directory. You can also run the appcmd list backups command to see all the backups.

Symantec recommends that you 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. Ensure all these Web sites exist, at 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.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. Follow the instructions in the Symantec Knowledge Base, in article HOWTO49691, starting at page 16.

Warning:

Run only the core Workflow installer process. Do not run the Post Installation Wizard for ServiceDesk.

You can use the following script to generate the preceding list of Web sites on your local IIS server.

To generate the information, create a file that is called enumvdirs.cmd. Open this link to Symantec Knowledge Base article TECH173381, and copy the contents of the attachment into your enumvdirs.cmd file.

After you have created the enumvdirs command file with the code found in the attachment, execute the file using the following syntax:

enumvdirs localhost > SD.VirtualDirs.txt

Executing this command creates a TXT file that is called SD.VirtualDirs.txt. 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.

Note:

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.

Warning:

Remember that 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.

Legacy ID

v64048382_v66564686

Article URL http://www.symantec.com/docs/HOWTO62380

IIS 7.5

IIS 7.5

Legacy ID

Please Sign In

Knowledge Base Search

Knowledge Base Search

MySymantec

MySymantec

Contacting Support

Contacting Support