StifleR
2.6
2.6
  • Start Here - StifleR 2.6
  • StifleR 2.6.x.x
    • StifleR - Release Notes
    • What's New
    • QuickStart Guide
      • Installation
        • Manual Server Installation
        • StifleR Client Installation
        • StifleR Network Locations
        • Example StifleR Rules Definition
    • Planning & Deployment Guide
      • TL;DR version
      • StifleR Overview
        • The StifleR Solution
      • Features Overview
        • Other Features
      • Technical Overview
        • StifleR Standard Features
        • StifleR Enterprise Features
      • Planning Your StifleR Implementation
        • Firewall Ports
        • Supported Clients
        • Networks in StifleR
        • Permissions
      • Installation
        • StifleR Server Installation
        • Dashboards, Client and Beacon Server Installation
        • Post Installation Checks
        • Testing Quick Start Guide
      • Troubleshooting
        • BranchCache across Subnets
      • StifleR Generic Concepts
        • Red Leader
        • Enterprise Environment - Blue Leader
      • Bandwidth Management
        • Bandwidth Tuning Monitoring and Control
      • StifleR WMI Provider
      • StifleR Feature Details
        • StifleR Enterprise Edition Features
      • Further Reading
    • StifleR Operations
      • Maintenance tasks
      • Backup and Recovery
        • Moving the StifleR Server Databases to a New Drive on the Same Server
    • StifleRulez.xml Configuration Guide
      • The Match – TypeData
        • When the Job Title Isn’t Suitable
        • ConfigMgr Specific Rules
      • The Setting - DownloadTypes
        • Delivery Optimization Jobs
      • Sample StifleRulez.xml
    • Securing StifleR Operations with SSL
      • Pre-Requisites
      • Securing the StifleR SignalR Endpoint
        • Binding certificates to SSL Ports for SignalR/StifleR
      • Running SignalR with SSL
      • IIS Configuration
      • Appendix A: Certificates
        • Using IIS to create a self-signed Certificate
        • Using a full IIS Certificate
      • Appendix B:Finding the CertHash
Powered by GitBook
On this page
  • Summary
  • Procedure
  • Verification
  • Backout
Export as PDF
  1. StifleR 2.6.x.x
  2. StifleR Operations
  3. Backup and Recovery

Moving the StifleR Server Databases to a New Drive on the Same Server

The information on this page only applied to StifleR Server 2.6.

Summary

The 2Pint StifleR Server, by default, stores its databases in the %ProgramData% folder which is typically located on the C: drive. In some cases, an admin might want to move the databases to another drive. The steps below describes the process of migrating the StifleR databases to another folder on the same server.

Procedure

  1. On the server hosting the StifleR server, create a new folder where you would like to store the databases. In this example, the folder will be D:\StifleRDBs.

  2. Stop the "2Pint Software StifleR Server" service.

  3. Copy the folder structure from C:\ProgramData\2Pint Software\StifleR\Server\Databases to the folder created in step 1, Ex: D:\StifleRDBs.

  4. To modify the configuration, you will need to edit the StifleR.Service.exe.config file. It is recommended to make a backup copy of the file before proceeding. The file is located in the installation directory in which StifleR was installed.

  5. Open a text editor as administrator and edit the StifleR.Service.exe.config file.

  6. In the .config file, under the <AppSettings> line, add the following:

    <add key="ClientDatabasePath" value="D:\StifleRDBs\Clients" />
    <add key="HistoryDatabasePath" value="D:\StifleRDBs\History" />
    <add key="JobsDatabasePath" value="D:\StifleRDBs\Jobs" />
    <add key="LocationDatabasePath" value="D:\StifleRDBs\Locations" />
    <add key="SRUMDatabasePath" value="D:\StifleRDBs\SRUM" />
  7. Save the .config file and start the "2Pint Software StifleR Server" service.

  8. Check the Event Viewer - Applications and Services Logs - StifleR and check for errors.

Verification

  1. Open the StifleR Dashboard and verify that you can logon and verify that the data is available as expected, specifically your Networks.

  2. If all looks well, feel free to delete the Databases folder under: C:\ProgramData\2Pint Software\StifleR\Server. If not, see the next section to Backout of the change.

Backout

  1. If an error occurred and you need to restore the previous configuration. Stop the 2Pint Software StifleR Server service.

  2. Restore the backup copy of the StifleR.Service.exe.config and start the 2Pint Software StifleR Server service.

PreviousBackup and RecoveryNextStifleRulez.xml Configuration Guide

Last updated 1 year ago