Skip to main content
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.

Dell NetWorker 19.9 Administration Guide

Server role considerations

This section describes considerations for Windows Server Roles in Windows BMR.

Protecting Windows server roles

Several server role components of Windows host store the data in a database. Examples of Windows server roles with databases include:

  • Active Directory Rights Management Services (ADRMS).
  • Windows System Resource Manager (WSRM).
  • Universal Description, Discovery, and Integrations (UDDI) Services.
  • Windows Server Update Services (WSUS).

When you install the Windows server role on a host, the installation process prompts you to store data on either an existing SQL Server installation or in a Windows Internal Database (WID).

NetWorker uses the VSS SQL Server writer to back up the role databases that are stored in WID but does not protect role databases, which the server role component stores in a SQL Server. Use NMM or a third-party SQL backup product to backup and recovery the roles databases.

Backup and recovery workflows for server roles that use WID

These are the backup and recovery workflows are as follows:

  • Perform a NetWorker Windows BMR backup, which includes all the SQL writer components for WID. If required, backup user data on the client.
  • Perform a NetWorker Windows BMR recovery operation, which recovers all the WID components.

After the NetWorker Windows BMR system restart, the WID service is available and Windows server roles have access to their databases.

Saving and recovering SQL Server components with Windows BMR and NMM:

  1. Perform a NetWorker Windows BMR backup. If required, backup user data on the SQL client.
  2. Use NMM or a third-party backup application to back up the SQL Server application.
  3. Perform a NetWorker Windows BMR recovery operation.

    After the recovery and restart operations complete, you cannot start the SQL Server service. Also, any server roles that store data in SQL databases outside WID will not work.

  4. For non-clustered SQL servers only, ensure that the SQL group is offline.
  5. Run the following setup.exe command from a command prompt with elevated privileges, to rebuild the SQL Server:

    C:\> setup /QUIET /ACTION=REBUILDDATABASE /INSTANCENAME=Instance_name /SQLSYSADMINACCOUNTS=domain_name\administrator

    NOTE:The SQL Server installation media contains the Setup tool.
  6. Bring the SQL server services online.
  7. Use NMM or a third-party backup application to recover the SQL system databases (primary, model, msdb).
  8. Use NMM or a third-party backup application to recover the role databases.
  9. Restart the services that require the role databases that you recovered.
    NOTE:The NetWorkerModule for Microsoft Applications Application Guide provides more information about using NMM to recover SQL databases.

Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\