Network recovery – Echelon LNS User Manual

Page 271

Advertising
background image

LNS Programmer's Guide

257

(.BMP extension), and source files (.NC, .C and .H extensions). It is also a good idea to

reinstall plug-in software that applies to device types that are used within this network
with your data. Echelon recommends that you backup all these files before performing

the move. NOTE: Figure 6.2 in Chapter 6 of this document depicts where the external
interface files on a PC are stored.

Once you have moved the database to the new PC, you can restore access to the network

database on another LNS Server PC by following these steps:

1. Restore the database files into a suitable location on the LNS Server PC’s

hard drive, e.g. in a folder called “C:\MyNetwork”.

2. Restore all the required support files to their respective locations. You

will need to add any resource file sets that have been moved to the

resource file catalog. Any other files referenced in the network database

must be placed in the same absolute path location on the new PC.
Alternatively, you can update the path property (e.g. BitmapFilePath

or IconFilePath property) referencing the file.

3. Call

the

Networks collection’s Add() method. You will provide a name

for the imported database as the networkName element, and a reference
to its location as the databasePath element. Set the createDatabase

element to False. This adds a reference to the imported database to the

global database, without destroying any of its content.

Dim MyNetwork As LcaNetwork

Set MyNetwork = MyNetworks.Add(“Zorro Ltd”, _

“C:\MyNetwork”, False)

Network Recovery

The LNS Object Server includes a set of services that allow it to rebuild a network
database by scanning an installed network. This process, known as network recovery,

can be used to:

• Migrate from a LonManager API-based tool to a LNS-based tool.
• Migrate from an NSS-10 managed network to an LNS Object Server

managed network.

• Migrate from an NSS-based tool to an LNS-based tool.
• Recover a network database when no backup is available.

Recovery must be initiated by a Local client application. Even though you can use the

network recovery feature to rebuild an entire network database, you should not consider
it to be a replacement for consistently backing up your LNS databases, as described in

the Backing Up Network Databases section on page 251. Database backup has these

advantages:

• Copying a database directory to restore from a backup is much faster

than performing a network recovery. To recover a network database, the
LNS Object Server must scan the network to discover all the devices,

upload the piece of the overall network configuration that it stored in

each device, and then deduce the overall configuration of the network
from these pieces. This data collection and reconstruction process grows

roughly linearly with the complexity of the network, where complexity is

Advertising