LANsurveyor's Repository collects asset data from SNMP-enabled network equipment in addition to workstations and servers running the Responder client software and stores the data on a regular basis in a database. LANsurveyor uses either Microsoft SQL Server Express or Microsoft SQL Server (either locally or across the network).
This chapter covers pre-installation considerations as well as Repository setup.
Responder clients
Asset data stored in the Repository is gathered from systems running the optional Responder client software. In order to store data in the Repository, Responder clients must be version 5.4 or later. Refer to the Install Responder clients or Upgrade Responder client sections of this manual for more information.
Responder clients are assigned their primary database key based on the millisecond the LANsurveyor system installs the key.
SNMP-enabled Network Equipment
SNMP asset data can also be stored in the Repository including basic configuration information, printer statistics, and APC-specific UPS data.
Architecture Considerations
If you plan to use just one copy of LANsurveyor at your site, you can skip this section. You can also skip this section if you plan to implement multiple copies of LANsurveyor with independent Repository databases.
If your organization plans to implement more than one copy of LANsurveyor with a shared database, you need to consider which copy of LANsurveyor will be responsible for gathering data from which clients. The responsibility for gathering client data lies with the LANsurveyor applications and is based on the maps either opened or specified at each copy of LANsurveyor under AutoOpen options.
Computers included on maps opened by multiple copies of LANsurveyor will be subject to multiple Repository requests within the same data collection period. There will not be multiple primary records for the computers; rather, there will be duplicate entries for individual pieces of information, such as memory, CPU speed, etc. For example, if there are two copies of LANsurveyor, a central SQL Server Repository, and the Repository is set to gather information once a week from each system, each system included on the active or specified LANsurveyor diagrams of both LANsurveyor systems will have information gathered twice per week rather than once per week.
Sites with multiple copies of LANsurveyor may share maps between systems so each copy has access to a superset of network data. In order to prevent inadvertent duplication of Repository resources, each copy of LANsurveyor can specify which maps should be used for Repository tasks using the AutoOpen option.
Repository Installation
To install, configure and run the Repository, select Tools>Options and click on the Repository tab. Click the "Install Repository" button to begin the process.
You can either connect to an existing SQL Server or have LANsurveyor install a new SQL Server Express database.
If you choose to use an existing SQL Server installation, you must provide an administrator's login name and password (or a login with enough permissions to create a database and run the sp_addlogin stored procedure).
The most current installation instructions and links to supported SQL Server Express software are available on the SolarWinds website at http://www.solarwinds.com/lansurveyor/RepositoryInstructions.htm.
If you choose to install a new database, the next step in the wizard allows you to select your user name and password for this installation.
Once the Repository is successfully installed, the other options become available.
If you have maps created with prior versions of LANsurveyor or older Responder client software installed, you will need to upgrade your Responder client software and draw a new map to begin data capture.
Repository Options
LANsurveyor includes built-in database maintenance utilities to optimize and protect your Repository. You can set the frequency of backup and internal maintenance routines as well as specify an alert should LANsurveyor encounter a Repository error.
Click Change Repository Password to change the database login name and/or access password using this dialog box:
The Asset Data Collection section of the Repository tab allows you to specify Repository settings for this specific copy of LANsurveyor. LANsurveyor will attempt to collect asset data during the period you specify trying every "n" hours to connect if the a system is not available at the collection time.
This section also includes a Discard asset data older than grooming capability to help minimize the database resources used to maintain asset information.
If Always use Repository data when generating reports is selected, LANsurveyor will use Repository for all custom reports with Responder client data fields as well as the Software Inventory, Missing Software, and Hardware Inventory standard reports. LANsurveyor will never use the Repository for Backup Profiler, Software Meter, or Get Info reports as these are real-time in nature.
If LANsurveyor fails to gather asset data within the given number of days, selecting Alert on unresponsive nodes will cause an alert to be sent for each missing node.
After the Repository is created and a new LANsurveyor map is generated, Responder clients and SNMP systems are automatically tracked in the Repository. You can specify which SNMP and Responder nodes are included in the Repository using the Change Collection Status buttons.
