Creating a Manual Solution

To prevent data loss, create a database solution, and implement it in the event of a disaster.

While a Maintenance Plan will allow you to automate the backup of your databases and transaction logs, you can also create and restore individual backups using the SQL Server Management Studio.

Creating a Database Backup

The most important part of an effective disaster recovery technique is having a current and valid backup. Create a backup for the SQL Server instance associated with Ivanti Endpoint Security to assure minimal system data is lost if a disaster occurs.

Backups are created within SQL Server Management Studio.

  1. Open the Microsoft SQL Server Management Studio.
  2. Log into your database server.
  3. In the directory tree, expand to Databases (Server Name > SQL Instance > Databases).
  4. Right-click the PLUS database.
  5. Select Tasks > Backup.
    The Back Up Database window opens.
  6. Ensure that the Source values are set as follows:
    • Database: PLUS
    • Recovery model: Full

      If the Recovery model is not set to Full, refer to Preparing Your Database.

    • Backup Type: Full
    • Backup Component: Database
  7. Define the Backup set identification fields.
    The following table describes each field.

    8. Field

    Description

    Name

    The name of the backup set.

    Description

    The description of the backup set.
  8. Define the backup set expiration date.
    Use one of the following methods.

    9. Method

    Steps

    To define an expiration date based on a set number of days:
    1. Select the After option.
    2. Type the desired number in the After field.

    To define an expiration date based on a set date:
    1. Select the On option.

    2. Select the desired date from the On list.
  9. Define your backup Destination settings.
    1. Select either the Disk or Tape option.
    2. Define the destination Folder.

      For performance reasons, it is recommended that you create your database backup in a directory that is not on the same physical drive as your database.

  10. Select Options within the Select a page pane.
    The Options page displays.
  11. Select whether to Backup up to the existing media set or Back up to a new media set, and erase all existing backup sets as is appropriate for your organization.
  12. Select the Verify backup when finished option to ensure a valid backup.
  13. Click OK.
  14. Repeat steps 5 through 13 for the following databases:

    15. Database Name

    Product

    STAT_Guardian

    Ivanti Endpoint Security

    UPCCommon

    Ivanti Endpoint Security

    UPCExtended

    Ivanti Endpoint Security

    PLUS_Reports

    Ivanti Enterprise Reporting Client

    ERS

    Ivanti Enterprise Reporting

    ERS_Staging

    Ivanti Enterprise Reporting

    ReportServer(1)

    Microsoft SQL Server Reporting Services

    ReportServerTempDB(1)

    Microsoft SQL Server Reporting Services

    SafeGuard(2)

    powered by Sophos®
    1. Subscription features available in Microsoft SQL Server Reporting Services can be implemented in Ivanti Enterprise Reporting. By default, the database names are ReportServer and ReportServerTempDB.
    2. Data protection capabilities in is enhanced with a full disk encryption add-on from Sophos. The installation of results in a Safeguard database.

After Completing This Task:

You must also backup the Ivanti Endpoint Security content directory.

The default location of the content directory is <Installation Directory>\HEAT\EMSS\Content. However, if this directory was modified during installation, you can verify its location by viewing the \HKEY_LOCAL_MACHINE\SOFTWARE\Patchlink.com\Update\ISAPI\Storage registry key.

Restoring a Database Backup

Another important part of an effective Disaster Recovery Solution is having a process defined in which to restore your database backup.

Prerequisites:

  • Prior to restoring the database backup you must install the Ivanti Endpoint Security server using the same serial number that was used previously.

Important: After installing the Ivanti Endpoint Security server do not open the user interface until after you have restored the databases.

  1. Open the Services Management Console.
  2. Right-click the World Wide Web Publishing service.
  3. Select Stop to stop the World Wide Web Publishing (IIS) service.
  4. Repeat steps 2 and 3 for the following services:
    • EDS Server
    • EDS InstallerService
    • Replication Service
    • STATEngine
  5. Restore the backup you made of the content directory, over the new content directory (<Installation Directory>\HEAT\EMSS\Content by default). However, if this directory was modified during installation, you can verify its location by viewing the \HKEY_LOCAL_MACHINE\SOFTWARE\Patchlink.com\Update\ISAPI\Storage registry key.
  6. Open the Microsoft SQL Server Management Studio (Start > Programs > Microsoft SQL Server 2008 > SQL Server Management Studio).
  7. Using an user account that has sysadmin rights, log into your database server.
  8. In the directory tree, expand Server Name\SQL Instance > Databases.
  9. Right-click the Databases folder.
  10. Select Restore Database.
    The Restore Database window opens.
  11. In the To database field, type or select the PLUS database.
  12. Select From device and click the Ellipses button (...).
    The Specify Backup dialog opens.
  13. Click Add.
    The Locate Backup File dialog opens.
  14. Locate and select your backup (.bak) file.
  15. Click OK.
  16. Click OK to return to the Restore Database window.
  17. Select the check-box associated with your backup within the Select the backup sets to restore table.
  18. Click Options within the Select a page pane.
    The Options page displays.
  19. Ensure the Overwrite the existing database option is selected.
  20. Verify, and correct if necessary, the directory path within the Restore the database files as table.
  21. Ensure the Leave the database ready to use option is selected.
  22. Click OK to begin the database restoration.
  23. After the restore is complete run the following SQL command against the database:
    exec sp_changedbowner 'sa'
  24. Repeat steps 9 through 23, restoring each of the following databases:

    25. Database Name

    Product

    STAT_Guardian

    Ivanti Endpoint Security

    UPCCommon

    Ivanti Endpoint Security

    UPCExtended

    Ivanti Endpoint Security

    PLUS_Reports

    Ivanti Enterprise Reporting Client

    ERS

    Ivanti Enterprise Reporting

    ERS_Staging

    Ivanti Enterprise Reporting

    ReportServer(1)

    Microsoft SQL Server Reporting Services

    ReportServerTempDB(1)

    Microsoft SQL Server Reporting Services

    SafeGuard(2)

    powered by Sophos®
    1. Subscription features available in Microsoft SQL Server Reporting Services can be implemented in Ivanti Enterprise Reporting. By default, the database names are ReportServer and ReportServerTempDB.
    2. Data protection capabilities in is enhanced with a full disk encryption add-on from Sophos. The installation of results in a Safeguard database.
  25. Against the master database run the following SQL command.
    Copy
    exec sp_dboption N'STAT_Guardian', N'DB CHAINING', N'true' exec sp_dboption N'UPCCommon', N'DB CHAINING', N'true' exec sp_dboption N'UPCExtended', N'DB CHAINING', N'true' exec sp_dboption N'PLUS', N'DB CHAINING', N'true'
    exec sp_dboption N'PLUS_Reports', N'DB CHAINING', N'true'
     
    exec sp_dboption N'ERS', N'DB CHAINING', N'true'
    exec sp_dboption N'ERS_Staging', N'DB CHAINING', N'true' exec sp_dboption N'ReportServer', N'DB CHAINING', N'true'
    exec sp_dboption N'ReportServerTempDB', N'DB CHAINING', N'true' exec sp_dboption N'SafeGuard', N'DB CHAINING', N'true'
  26. If you changed the computer name, Service account name, or Client account name, then you must perform the following steps.
    1. Delete the previous Service account and Client account users from each database.
    2. Add the new Service and Client account users to the following roles for each database.
      • PLUS - EMSS Server and aspnet_ChangeNotification_ReceiveNotificationsOnlyAcccess
      • PLUS_Reports - EMSS Server
      • STAT_Guardian - Guardian_Admin
      • UPCCommon - EMSS Server and aspnet_ChangeNotification_ReceiveNotificationsOnlyAcccess
      • UPCExtended - EMSS Server and aspnet_ChangeNotification_ReceiveNotificationsOnlyAcccess
      • ERS - EMSS Server
      • ERS_Staging - EMSS Server
  27. If you re-installed the Ivanti Endpoint Security server with a different user name than was used when originally installed, run the following SQL command:
    UPDATE AccountContacts SET UserName = 'NewUserName' WHERE UserName = 'OldUserName'
  28. If you re-installed the Ivanti Endpoint Security server with the content directory in a different location than the original installation, run the following SQL command:
    UPDATE SystemConfig SET SystemConfig_Value = 'NewStorageSystemPath' WHERE SystemConfig_Name = 'Storage'
  29. If you re-installed the Ivanti Endpoint Security server with a different installation directory than the original installation, run the following SQL command:
    UPDATE SystemConfig SET SystemConfig_Value = 'NewWebInstallPath' WHERE SystemConfig_Name = 'InstallPath'
  30. Restart the World Wide Web Publishing Service, EDS LanPortal, EDS MessageBroker, EDS Server, Replication Service, and STATEngine services.
  31. Install the Ivanti Endpoint Security Agent from the Download Agent Installers page.