StifleR
2.10
2.10
  • Start Here - StifleR 2.10
  • Introduction
    • StifleR Overview
      • The StifleR Solution
      • Managing Microsoft Data Transfer Services
    • Technical Overview
      • 2Pint BranchCache Administrator Guide
    • Features Overview
      • Control
      • Monitor
      • Automate
      • Other Features
      • StifleR Feature Details
    • Release Notes
  • Proof of Concept
    • Objectives and Prerequisites
    • Configure Microsoft Peer-to-Peer Components
    • Install and Configure StifleR
    • Testing and Validation
    • StifleR POC Quick Checklist
  • Planning
    • StifleR Server Considerations
    • StifleR Client Considerations
    • Firewall Ports
    • Permissions
    • Antivirus Exclusions
    • Network Topology
    • StifleR Generic Concepts
      • Client Leader Roles
        • Red Leader
        • Blue Leader
        • Green Leader
        • Examples of Leader Selection
      • Templates
      • Beacons
  • Installation
    • Overview
    • Server
      • StifleR Server Installation
      • StifleR Dashboard Installation
      • StifleR Beacon Installation
    • Client
      • StifleR Client Installation
      • Post Installation Checks
  • Configuration
    • Configuration Files
      • StifleR Server Configuration File
        • Using the AppSettings Override File
      • StifleR Client Configuration File
      • StifleR Dashboard Configuration File
    • Configuring BranchCache on Windows Server
    • Configuring Delivery Optimization
    • Configuring LEDBAT on CM DPs
    • Configuring a Beacon Server
    • Configuring StifleR SQL History
    • StifleR Network Locations
      • Automatic linking of Location, Network Groups and Networks
      • Network Topology Automation
      • Location Fields
        • Network Group Fields
          • Network Fields
    • 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
      • Prerequisites
      • Using a Web Server Certificate
        • Requesting a Web Server Certificate
      • Using a Self-Signed Certificate
      • Preparing the StifleR Dashboard Web Site for SSL
      • Configuring StifleR to Use SSL
      • Finding the Certificate Thumbprint
    • StifleR Client Access Control Options
  • Operations
    • Dashboard
      • Overview & Navigation
        • Home Page
        • Traffic & Downloads
          • Transfers & Downloads
            • How to use query hosts search?
          • Running Sequences
          • Weekly Downloads Activity
          • History
        • Devices
          • Clients
            • Client Details
              • How to use an extended search?
          • Servers
          • StifleR Server
            • Templates Detail
        • Cache Management
        • System Resource Usage
        • Network Topology
          • Maps
          • Countries
          • Locations
            • Bandwidth Allocations and Locations
          • Network Groups
          • Networks
        • Reporting & Diagrams
    • Client Management & Remote Tools
      • Remote PowerShell Session
      • Remote Performance Counter
      • Remote WMI Browsing
      • Remote Event Log Viewer
      • Remote Netmon Session
    • Monitoring
      • StifleR server health
      • StifleR client health
      • BranchCache Testing and Monitoring
    • Maintenance tasks
    • Bandwidth Management and Allocation
      • Bandwidth Tuning Monitoring and Control
    • Backup and Recovery
      • Moving the StifleR Server Databases to a New Drive on the Same Server
    • Troubleshooting
      • StifleR Client Command Line Options
      • BranchCache across Subnets
    • StifleR WMI Provider
Powered by GitBook
On this page
  • Summary
  • Procedure
  • Verification
  • Backout
  1. Operations
  2. 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.10.

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 and appSettings-override.xml files. 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 StifleR.Service.exe.config file, under the <appSettings file="./appSettings-override.xml"> line, add the following:

    <add key="NewLocationDatabasePath" value="D:\StifleRDBs\Location" />
    <add key="MainDatabasePath" value="D:\StifleRDBs\Main" />
    <add key="HistoryDatabasePath" value="D:\StifleRDBs\History" />
  7. Save the StifleR.Service.exe.config file then start the "2Pint Software StifleR Server" service.

  8. Check the Event Viewer - Applications and Services Logs - TwoPintSoftware - StrifleR.Service - Operational 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 RecoveryNextTroubleshooting

Last updated 1 year ago