Submit a ticketCall us

Webinar: Web Help Desk for HR, Facilities and Accounting Departments
This webinar will focus on use cases for HR, Facilities and Accounting.

Having a unified ticketing and asset management system for all the departments in your company can provide end-users with a seamless experience and make things easier for your IT team. Yet, with different business tasks and objectives, many departments don’t fully understand the capabilities of Web Help Desk and how the software can be customized for effective use in their departments.
Register Now.

Home > Success Center > Storage Manager (STM) > XML Configuration Preservation locations for Storage Manager Proxy agents

XML Configuration Preservation locations for Storage Manager Proxy agents

Table of contents
No headers
Created by Interspire Import, last modified by MindTouch on Jun 23, 2016

Views: 14 Votes: 0 Revisions: 8

XML Configuration Preservation will begin when the customer upgrades a version of Storage Manager that is higher than version 5.7.0. The installation scripts will perform the task of backing up previous agent XML configuration files on the Storage Manager Server. Any upgrades after Storage Manager Release 5.7.0, will also provide the same functionality and include backups of the Storage Manager Proxy agents XML configuration files. This will occur if the Proxy Agent upgrade is done via the installation scripts or an agent module push via the Storage Manager Server website.

Depending on whether the previous agent’s XML configuration files are backed up using the install scripts or agent module push, the location of the backup files will be in different locations depending on the method used.

When upgrading STM proxy agents using the installation scripts, the agent configuration XML files will be backed up to the following location on the local file system:

%{STM_INSTALLATION_DIRECTORY}/history/config-YYYYMMDD/agent/[administrative|systemic]/${moduleDir}/${moduleName}.xml

  • ${STM_INSTALLATION_DIRECTORY} is where the STM product is installed (e.g., "C:\Program Files\SolarWinds\Storage Manager Server" or "/opt/Storage_Manager_Agent")
  • YYYYMMDD is the year, month, and date that the upgrade was applied by the installation script
  • [administrative|systemic] means that either one value or the other (e.g., "administrative" or "systemic") is used
  • ${moduleDir} is the name of the module directory that is backed up (e.g., "mod.adm.collect.Collector_1.0" or "mod.sys.app.mail.Mail_1.0")
  • ${moduleName} is the name of the module that is backed up (e.g., "mod.adm.collect.Collector" or "mod.sys.app.mail.Mail")

When upgrading STM proxy agents using the agent module push option on the Storage Manager Server website, the agent configuration XML files will be backed up to the following location on the local file system:

${STM_INSTALLATION_DIRECTORY}/agent/history/${moduleName}/YYYYMMDD/${moduleName}_YYYYMMDD-hhmmss.xml

  • ${STM_INSTALLATION_DIRECTORY} is where the STM product is installed (e.g., "C:\Program Files\SolarWinds\Storage Manager Server" or "/opt/Storage_Manager_Agent")
  • ${moduleName} is the name of the module that is backed up (e.g., "mod.adm.collect.Collector" or "mod.sys.app.mail.Mail")
  • YYYYMMDD is the year, month, and date that the configuration XML file backup was applied by the agent module upgrade code
  • hhmmss is the hour, minute, and second that the configuration XML file backup was applied by the agent module upgrade code
Last modified
03:49, 23 Jun 2016

Tags

Classifications

Public