Sysload Maintenance and Housekeeping

Solved : Management Server: Move Management Server from one host to another

Fri, 09 Oct 2009 17:03:43 +0200

Maintenance on the production environment may require to move the Management Server product from one host to another.

SP Analyst consoles, SP Portal and some SP Monitor modules communicate with the agents via the Management Server. Several console objects and enterprise models can be stored on the Management Server (SP Analyst users, the Enterprise Event Model, different workspaces, SP Portal agent classes and groups, time profiles�). Hence particular attention shall be taken when moving it.

REMARKS
---

A Management Server is known in Sysload by its name, which is in general the name of the machine hosting the program. This name appears when displaying the Management Server window in SP Analyst console. Some console objects (charts and tables and workspaces, event models, entity models�) make a reference to that name when retrieving data from agent declared on a Management Server.

When moving the Management Server from one host to another, the name of the host, and therefore of the Management Server, changes.

It is possible though to keep the console object database and settings from one Management Server to another but a simple duplication won't be enough to have it ready to work again. A particular procedure is required to have the new name to be used by all existing objects having to send request to the agents. Two methods are available.

FIRST METHOD
---

The first possible way to use the former Management Server database, is to force the new Management Server to use the same name as the previous one.

Procedure:
- Install the program on the new server without starting the Communication Server and Management Server services.
- Copy the object database file, namely sld_objects_repository, located on the old server in the \sldmgts\daily_backup\ directory on the new server in the \sldmgts\storage\sldat\ directory.
- Edit the \sldmgts\sldmgts.ini configuration file on the new server and modify the Name parameter with the old Management Server name.
- Start the Management Server and Communication Server services, using the Windows services management panel

SECOND METHOD
---

The second method is not based on forcing the name of the Management Server. Therefore you will be working with the new Management Server name, meaning with the real Management Server host name. But updating the console objects will be mandatory.

Procedure:
- Install the program on the new server without starting the Communication Server and Management Server services.
- Copy the object database file, namely sld_objects_repository, located on the old server in the \sldmgts\daily_backup\ directory on the new server in the \sldmgts\storage\sldat\ directory.
- Start the Management Server and Communication Server services, using the Windows services management panel
- Open the Management Server window in SP Analyst console and connect to the new Management Server.
- Edit all of the Management Server objects making referece to agents (charts and tables in workspaces, event models, entity models�) and update the agents used within these objects, one by one.

Solved : Agent: Purge agent history top data

Fri, 09 Oct 2009 17:01:10 +0200

PROCEDURE ON WINDOWS, UNIX AND LINUX
---

The procedure is as follows:

- Run the SP Analyst console.

- Select the agents.

- Select the menu Agents > Define the > Collector analysis parameters.

- Select the first tab, 'Collector analysis parameters'.

- Choose section 'Historical Tops'.

- Choose the keyword 'Revolving historic'.

- Set a value in number of days (keep the last n days).

- Set the value '0' (zero) to keep data forever.

- Click OK. Collector will restart.

- Wait the next day.

- Check in the Collector log file that the purge has been done. The purge will then be done every day.

REMARKS
---

- The purge is done automatically at midnight every day (this is fixed in the source code).

- The purge deletes the data in the history file, but leaves empty records. One therefore do not gain disk space by running the automatic purge on the history of tops (the objective of the purge is to have a file withs constant size).

- A Sysload tool to manually purge history files exists (/tools/sld_purge'), but the effect of this purge depends on the version of the agent:
. Agent <= 5.00x: Same as for automatic purge, no disk space is gained. The only method to gain disk space is by deleting the history files '*-top.dat' and '*-top.idx'. Stop Collector and File Server before doing so.
. Agent >= 5.10: The purge can be used to gain disk space by purging old data. Proceed as for purging history files of acvity but on the '-top' files. See specific FAQ.

Solved : Token Server: Move Token Server from one host to another

Fri, 09 Oct 2009 16:54:39 +0200

Maintenance on the production environment may require to move the Token Server product from one host to another.

Token Server is a central component that is accessed by several Sysload programs and hence particular attention shall be taken when moving it.

REMARKS
---

Token Server is protected by the license file that was originally set in place during the initial setup of Token Server. Hence if the IP address of the new server is different to the one of the former one, then a new license file is necessary. Contact Orsyp in order to do so.

Agents, SP Analyst consoles and SP Portal are clients to Token Server. The configuration of those clients may require to be updated in order to contact Token Server on the new host.

A Token Server working as a gateway does not have a license file. Not all the information indicated hereafter then applies.

There may be firewalls between Token Server and its clients, and/or between the master Token Server and the Token Server gateways. In this case firewall security policies may require to be updated.

PROCEDURE WHEN THE IP ADDRESS REMAINS THE SAME
---

If the IP address of the former Token Server host is transfered to the new host, then the procedure is as indicated below.

Start Token Server:
- Install Token Server on the new host.
- Stop Token Server on the former host.
- Copy the file '/sldtkd/sldtkd.dat' from the former host to the new one.
- Start Token Server on the new host.
- Check the new Token Server is operational with the Token Server web interface:
. Open a web browser.
. Go to address 'http://:9557'.
. Click Token Status.
. Check that the agents that were given Tokens by the former Token Server are known by the new Token Server (subscribed agents).

Make Token Server clients point to the new Token Server host:
- If the clients were contacting the Token Server host by its IP address and as the IP address stays the same, then there is no action to take.
- If the clients were contacting the Token Server host by its hostname and if the hostname stays the same there there is no action to take.
- If the clients were contacting the Token Server host by its hostname and if the hostname changes, then change the DNS entry for the Token Server host and change the Tokens Server host hostname in the configuration files of the Token Server clients.

PROCEDURE WHEN THE IP ADDRESS CHANGES
---

If the IP address of the new host is different than the one of the former host, then the procedure is as indicated below.

Start Token Server:
- Obtain a new license file ('sldtkd.lic') from your sales representative.
- Install Token Server on the new host. Set it up with the license file newly received.
- Check the Token Server web interface:
. Open a web browser.
. Go to address 'http://:9557'.
. Click Token Status.
. Check that the stock of tokens in the section Token info (the column used count should be 0 (zero)).
- Stop Token Server on the former host.
- (From this point onward, agent Collector programs will continue running for the duration of the grace period. Do make clients point to the new Token Server ASAP.)

Make Token Server clients point to the new Token Server host:
- For the agents this may be done via the SP Analyst console:
. Right mouse button on an agent.
. Select the menu item Define the > Collector analysis parameters.
. Select the tab Collector analysis parameters.
. Select the section Token Server.
. Set host to the new host ID.
. Click Apply (eventually apply to many agents).
. (The agent Collector program will be restarted.)
- For SP Analyst console this is done by editing the configuration file of the console:
. Go the SP Analyst console machine(s).
. Edit the file '\console\sld.ini'.
. Set the parameter 'masterip' in the section 'SLDTK' to the host ID.
. Start the console to check it can obtain a token from the new host.
- For the SP Portal Sldppcoll program this is done by editing its configuration file:
. Go the the server hosting SP Portal.
. Edit the file '\sldppcoll\sldppcoll.ini'
. Set the parameter 'masterip' in the section 'SLDTK' to the host ID.

Solved : Agent: Rename the hostname written in Sysload history files

Fri, 09 Oct 2009 16:51:52 +0200

The hostname of the machine is written in the history files of Sysload agents (history of activities, history of alerts).

When renaming the machine, the name in the history files must be renamed.

The rename tool exists on Windows and Unix agents.

Hereafter '' refers to the Sysload installation directory.

PROCEDURE ON UNIX
---

The procedure is as follows:

- Open a command prompt.

- Make sure Collector and File Server are not running, run the following commands:
. '/coll/conf/sldrmd stop'
. '/coll/conf/sldfsd stop'

- When applicable, stop Oracle Collector:
. '/coll/conf/sldord stop'

- Check there are no remaining processes returned by the following commands:
. 'ps -ae | grep sldrm'
. 'ps -ae | grep sldfs'

- When applicable:
. 'ps -ae | grep sldor'

- Go to the '/tools' directory.

- Run the following command:
. '/tools/sld_rename -hst_file /_hst -new_node '
. Example:
. '/opt/sysload/tools/sld_rename -hst_file /opt/sysload/moon_hst -new_node sun'

- Start Collector:
. '/coll/conf/sldrmd start'

- When applicable, start Oracle Collector:
. '/coll/conf/sldord start'

- Check that it starts successfully by looking at Collector log file ('/coll/conf/sldrmd.log').

- Start File Server:
. 'sldfsd start'

PROCEDURE ON WINDOWS
---

The procedure is as follows:

- Make sure Collector and File Server are not running, stop the following services with the Windows Services panel:
. Sysload Collector
. Sysload File Server

- When applicable, stop Oracle Collector service:
. Sysload Oracle Collector

- Check there are no remaining processes with Windows Task Manager:
. Sldrm*
. Sldfs*
. Sldor*

- Open a command prompt.

- Go to the directory.

- Go to the 'tools' directory.

- Run the following command to process the history files of activities:
. Sld_rename.exe -hst_file \History\Activity -new_node
. Example:
. Sld_rename -hst_file "C:\Program Files\Sysload\History\Activity" -new_node sun

- Run the following command to process the history files of alerts
. Sld_rename.exe -hst_file \History\Alert -new_node
. Example:
. Sld_rename -hst_file "C:\Program Files\Sysload\History\Alert" -new_node sun

- Start Collector by starting the following service:
. Sysload Collector

- When applicable, start Oracle Collector:
. Sldord start

- Check that Collector starts successfully by looking at Collector log file ('\sldrmd\sldrmd.log').

- When applicable, check that Oracle Collector starts successfully by looking at Collector log file ('\sldord\sldord.log').

- Start File Server by starting the following service:
. Sysload File Server

REMARKS
---

The history files of Tops do not make any reference to the hostname, no need to run the 'sld_rename' on them.

When refering to the history files, do not write the file exentions (.dat, .idx).

On Unix, it is also recommended to rename the name of the history files according to the new name (Unix command 'mv'). This will maintain the coherence between the name of the history file and the name written in the history file. But then, it is also necessary to change the value of the variable 'node' in the Sysload script '/coll/conf/sldrmd'.

Solved : Agent: Rebuild agent history files

Fri, 09 Oct 2009 16:48:24 +0200

INTRODUCTION
---

- History files of Unix OS agent:
. History of activities:
. /_hst.dat
. /_hst.idx
. History of tops:
. /_hst-top.dat
. /_hst-top.idx
. History of alerts:
. /_hstevnt.dat
. /_hstevnt.idx

- History files of Windows OS agent:
. History of activities:
. \history\activity.dat
. \history\activity.idx
. History of tops:
. \history\activity-top.dat
. \history\activity-top.idx
. History of alerts:
. \history\alert.dat
. \history\alert.idx

PROCEDURE ON UNIX AND LINUX
---

The procedure is as follows:

- Stop Collector, do this by running the following commands:
. /coll/conf/sldrmd stop

- Check there are no remaining processes returned by the following command:
. ps -ae | grep sldrm

- Stop File Server, do this by running the following commands:
. /coll/conf/sldfsd stop

- Check there are no remaining processes returned by the following command:
. ps -ae | grep sldfs

- When applicable, stop the database or application Collector and check they no longer run.

- When applicable, delete former backup files.

- Run the following command:
. /tools/sld_rebuild -hst_file / [ -save_file / ]
. Note that when parameter '-save_file' is not set, a default path is given by the program (same directory, suffix '_save' added to file basenames).

- Check the rebuild was successful by looking at the rebuild log file (file '/tools/sldrebuild.log').

- Start Sysload Collector and File Server.
. /coll/conf/sldrmd start
. /coll/conf/sldfsd start

- Possibly delete the backup files.

EXAMPLES ON UNIX
---

Rebuild history files of activities, take default path for backup files:
- opt/sysload/tools/sld_rebuild -hst_file opt/sysload/moon_hst

Rebuild history files of alerts, force backup file to be stored in '/tmp':
- opt/sysload/tools/sld_rebuild -hst_file opt/sysload/moon_hstevnt -save_file /tmp/moon_hstevnt

Rebuild history files of tops:
- opt/sysload/tools/sld_rebuild -hst_file opt/sysload/moon_hst-top

PROCEDURE ON WINDOWS
---

The procedure is as follows:

- Stop Sysload Collector:
. This can be done by stopping the following service from the Windows Services panel:
. Sysload Collector
. This can be done by running the following system command:
. net stop "Sysload Collector"

- Stop Sysload File Server:
. This can be done by stopping the following service from the Windows Services panel:
. Sysload FileServer
. This can be done by running the following system command:
. net stop "Sysload FileServer"

- When applicable, stop the database or application Collector and check they no longer run.

- When applicable, delete former backup files.

- Run the following command:
. \tools\sld_rebuild.exe -hst_file [ -save_file ]
. Note that when parameter '-save_file' is not set, a default path is given by the program (same directory, suffix '_save' added to file basenames).

- Start Sysload Collector.
. This can be done by starting the following service from the Windows Services panel:
. Sysload Collector
. This can be done by running the following system command:
. net start "Sysload Collector"

- Start Sysload File Server.
. This can be done by starting the following service from the Windows Services panel:
. Sysload Collector
. This can be done by running the following system command:
. net start "Sysload Collector"

- Possibly delete the backup files.

EXAMPLES ON WINDOWS
---

Rebuild history files of activities:
- "C:\Program Files\Sysload\Tools\sld_rebuild.exe" -hst_file "C:\Program Files\Sysload\history\activity"

Rebuild history file of alerts.
- "C:\Program Files\Sysload\Tools\sld_rebuild.exe" -hst_file "C:\Program Files\Sysload\history\alert"

Rebuild history file of top.
- "C:\Program Files\Sysload\Tools\sld_rebuild.exe" -hst_file "C:\Program Files\Sysload\history\activity-top"

REMARKS
---

The Rebuild is installed by the installation program for the Operating System. Nevertheless it can be used to also rebuild the history file of a database or application agent running on the same machine.

The Rebuild can be used to re-create the index file from the data file in case the index file was deleted.

The Rebuild can be used to rebuild a history file made by a smaller version of Collector (e.g. Rebuild 5.00 okay for a history file 4.81.)

The Rebuild must be used on the same machine as the one where Collector is running. It is not recommended to copy the history file from a machine A and rebuild it on a machine B. Or when doing it, ensure it is done on the same operating system-type.

Solved : Agent: Purge agent history activity data on instances

Fri, 09 Oct 2009 16:43:50 +0200

The whole data can be purged from history files of activities for specific instances of domains with instance.

PROCEDURE ON WINDOWS
---

The procedure is as follows:

- Stop Sysload Collector:
. This can be done by stopping the following service from the Windows Services panel:
. Sysload Collector
. This can be done by running the following system command:
. Net stop "Sysload Collector"

- Stop Sysload File Server:
. This can be done by stopping the following service from the Windows Services panel:
. Sysload FileServer
. This can be done by running the following system command:
. Net stop "Sysload FileServer"

- Run the following command:
. /tools/sld_purge.exe -by_entity -hst_file -save_file
. Examples:
. "C:\Program Files\Sysload\tools\sld_purge.exe" -by_entity -hst_file "C:\Program Files\Sysload\History\actvity"

- Answer the questions.

- Start Sysload Collector.
. This can be done by starting the following service from the Windows Services panel:
. Sysload Collector
. This can be done by running the following system command:
. Net start "Sysload Collector"

- Start Sysload File Server.
. This can be done by starting the following service from the Windows Services panel:
. Sysload Collector
. This can be done by running the following system command:
. Net start "Sysload Collector"

- Check that elements are purged.

- Possiblly delete the backup files.

PROCEDURE ON UNIX AND LINUX
---

The procedure is as follows:

- Stop Collector and File Server, do this by running the following commands:
. /coll/confsldrmd stop
. /coll/confsldfsd stop

- Run the following command:
. /tools/sld_purge.exe -by_entity -hst_file -save_file
. Examples:
. /opt/sysload/sysload/tools/sld_purge.exe -by_entity -hst_file /opt/sysload/sysload/moon_hst

- Answer the questions.

- Check that elements are purged.

- Possiblly delete the backup files.

REMARKS
---

Backup files are created by default. The parameter 'save_file' is optional.

As the program asks questions interactively, it cannot be run as a scheduled task.

The whole data for specified instances are deleted, it is not possible to apply a date filter.

If nothing is to be purged in a domain, just press 'enter' when asked.

To purge something in the domain that is indicated, enter a regular expression describing the names of the instances to delete.

Examples:
- Delete information on all disks:
. Put '.*' when asked the question about disks.
. Press 'enter' on all the other domains.
- Delete information on entities of type Application 'Oracle' and 'Sara':
. Put '^Oracle$|^Sara$' when asked the question about applictions.
. Press 'enter' on all the other domains.

The test to confirm that instances have been deleted is trying to do a history chart. Deleted instances no longer appear.

Solved : Agent: Purge agent history activity data and alert data

Fri, 09 Oct 2009 16:38:53 +0200

PROCEDURE ON WINDOWS
---

The procedure is as follows:

- Stop Sysload Collector:
. This can be done by stopping the following service from the Windows Services panel:
. Sysload Collector
. This can be done by running the following system command:
. Net stop "Sysload Collector"

- When applicable stop the database or application Collector.

- Stop Sysload File Server:
. This can be done by stopping the following service from the Windows Services panel:
. Sysload FileServer
. This can be done by running the following system command:
. Net stop "Sysload FileServer"

- When applicable, delete former backup files.

- Run one of the following command:
. /tools/sld_purge.exe -hst_file -save_file -keep_days
. /tools/sld_purge.exe -hst_file -save_file -begin_date -end_date
. Examples:
. Keep the data of last 365 days:
. "C:\Program Files\Sysload\tools\sld_purge.exe" -hst_file "C:\Program Files\Sysload\History\actvity" -keep_days 365
. Delete the data of November 2006
. "C:\Program Files\Sysload\tools\sld_purge.exe" -hst_file "C:\Program Files\Sysload\History\actvity" -begin_date 2006-11-01 -end_date 2006-11-30

- Start Sysload Collector.
. This can be done by starting the following service from the Windows Services panel:
. Sysload Collector
. This can be done by running the following system command:
. Net start "Sysload Collector"

- Start Sysload File Server.
. This can be done by starting the following service from the Windows Services panel:
. Sysload Collector
. This can be done by running the following system command:
. Net start "Sysload Collector"

EXAMPLE ON WINDOWS
---

@echo off
rem Dos script to launch Sysload purge
rem Script version 1.00 (2 Feb. 2006)

set history_dir=c:\program files\sysload\history
set tools_dir=c:\program files\sysload\tools
set no_days=365

rem This script deals with history files of Sysload OS agents only, application and database agents would also need to be dealt with

rem Delete previous history backup files

del "%history_dir%\activity_save.dat"
del "%history_dir%\activity_save.idx"

del "%history_dir%\alert_save.dat"
del "%history_dir%\alert_save.idx"

rem Stop Sysload Collector and File Server

net stop "Sysload Collector"
net stop "Sysload FileServer"

rem Purge history of activities

"%tools_dir%\sld_purge.exe" -hst_file "%history_dir%\activity" -keep_days %no_days%

rem Purge history of alerts

"%tools_dir%\sld_purge.exe" -hst_file "%history_dir%\alert" -keep_days %no_days%

rem Start Sysload Collector and File Server

net start "Sysload Collector"
net start "Sysload FileServer"

PROCEDURE ON UNIX AND LINUX
---

The procedure is as follows:

- Stop Collector and File Server, do this by running the following commands:
. /coll/conf/sldrmd stop
. /coll/conf/sldfsd stop

- When applicable, stop the database or application Collector.

- When applicable, delete former backup files.

- Run one of the following command:
. /tools/sld_purge.exe -hst_file / -save_file / -keep_days
. /tools/sld_purge.exe -hst_file / -save_file / -begin_date -end_date
. Examples:
. Keep the data of last 365 days:
. /opt/sysload/tools/sld_purge.exe -hst_file /opt/sysload/sysload/moon_hst -keep_days 365
. Delete the data of November 2006
. /opt/sysload/tools/sld_purge.exe -hst_file /opt/sysload/sysload/moon_hst -begin_date 2006-11-01 -end_date 2006-11-30

- Check that things are purged.

- Possibly delete the backup files.

Solved : Backup SP Portal data and configuration files

Fri, 09 Oct 2009 16:32:53 +0200

SP Portal is essential to capacity management. It is hence recommended to integrate SP Portal data into standard backup procedures.

PROCEDURE
---

The backup procedure is as follows:

- Databases:
. The databases are 'sld_rawdata' and 'sld_perfportal'.
. These are third-party, refer to the standard procedure recommended by the manufacturer.
. Note the databases can be rebuilt from the history files of the Sysload agents, hence the databases of SP Portal may be ignored from backup procedures.

- Configuration files:
. Backup the configuration files listed in a specific FAQ on SP Portal.

- Management Server:
. Sysload Management Server is essential to SP Portal as it contains information regarding servers and groups of servers for SP Portal.
. Backup the files listed in a specific FAQ on Sysload Management Server.

Solved : Backup token server data and configuration files

Fri, 09 Oct 2009 16:31:29 +0200

The data to backup is the file containing the list of programs that are consuming licenses.

PROCEDURE ON WINDOWS
---

The procedure is as follows:

- Stop Token Server.
. This can be done by stopping the following service from the Windows Services panel:
. Sysload TokenServer
. This can be done by running the following command:
. Net stop "Sysload TokenServer"

- Backup the following data file:
. \sldtkd\sldtkd.dat

- Backup the following configuration file:
. \sldtkd\sldtkd.ini

- Start Token Server.
. This can be done by starting the following service from the Windows Services panel:
. Sysload TokenServer
. This can be done by running the following command:
. Net start "Sysload TokenServer"

PROCEDURE ON UNIX
---

The procedure is as follows:

- Stop Token Server.
. This is done by running the following command:
. /sldtkd/sldtkd stop

- Backup the following data file:
. /sldtkd/sldtkd.dat

- Backup the following configuration file:
. /sldtkd/sldtkd.ini

- Start Token Server.
. This is done by running the following command:
. /sldtkd/sldtkd start

Solved : Backup management server data and configuration files

Fri, 09 Oct 2009 15:12:50 +0200

The Management server is a critical element in the Sysload infrastructure.

It is recommended to regularly backup the configuration files and the data.

The procedure to backup the data depends whether the repository is held in a file or on SQL Server.

PROCEDURE ON WINDOWS
---

The backup procedure is as follows:
- Backup the configuration files:
. '\sldcs\sldcs.ini'.
. '\sldmgts\sldmgts.ini'.
- Backup the data:
. If the repository is in the native Sysload format:
. Backup the file '\sldmgts\storage\daily_backup\sld_objects_repository' (by default).
. This file is the backup of the online file, made the previous night (by default).
. If the data is on SQL Server:
. Refer to the standard SQL Server backup procedure.

The restore procedure is as follows:
- Stop management server.
- Stop communication server.
- Restore the configuration files back to their original location.
- Restore the data:
. If the repository is in the native Sysload format:
. Restore the data file to the directory '\sldmgts\storage\sldat' (by default).
. If the data is on SQL Server:
. Refer to the standard SQL Server restore procedure.
- Start communication server.
- Start management server.

PROCEDURE ON LINUX
---

The backup procedure is as follows:
- Backup the configuration files:
. '/sldcs/sldcs.ini'.
. '/sldmgts/sldmgts.ini'.
- Backup the data:
. Backup the file '/sldmgts/storage/daily_backup/sld_objects_repository' (by default).

The restore procedure is as follows:
- Stop management server.
- Stop communication server.
- Restore the configuration files back to their original location.
- Restore the data file back to the directory '/sldmgts/storage/sldat' (by default).
- Start communication server.
- Start management server.

Solved : Backup the agent for Windows data and configuration

Fri, 09 Oct 2009 15:11:08 +0200

PROCEDURE
---

The procedure to backup data is as follows:

- Stop Sysload Collector:
. This can be done by stopping the following service from the Windows Services panel:
. Sysload Collector
. This can be done by running the following system command:
. Net stop "Sysload Collector"

- Stop Sysload File Server:
. This can be done by stopping the following service from the Windows Services panel:
. Sysload FileServer
. This can be done by running the following system command:
. Net stop "Sysload FileServer"

- Backup the database files.

- When applicable (token lease mode activated), backup the lease file.

- Backup the Collector configuration files.

- Backup the File Server configuration files.

- When applicable, backup the Script Monitor configuration files.

- When applicable, backup the Log Analyzer configuration files.

- Start Sysload Collector.
. This can be done by starting the following service from the Windows Services panel:
. Sysload Collector
. This can be done by running the following system command:
. Net start "Sysload Collector"

- Start Sysload File Server.
. This can be done by starting the following service from the Windows Services panel:
. Sysload Collector
. This can be done by running the following system command:
. Net start "Sysload Collector"

REMARK
---

In order to be useful when restored, the period between 2 backups of the lease file should be smaller than the grace period defined in the license file.