Skip to main content

We've Moved!

Product Documentation has moved to docs.hitachivantara.com
Hitachi Vantara Knowledge

How to import Logs from Protector 6.x or Protector 7.0 to Protector 7.1 after Upgrade

Before you begin

Version 7.1 of Hitachi Protector switches from using MongoDB to Postgres for its databases. Protector will not to automatically transfer the logs from an existing installation during upgrade. The rationale for this was that such a transfer might take several hours (or longer) and therefore the upgrade process would be inappropriately long.

For customers wishing to retain all, or some, of their logs from their earlier installations a manual import method has been developed which can be executed post upgrade. The import utilises a command line tool called ‘log-import.exe’ (or ‘log-import’ on Linux systems) which resides in the Protector/bin installation directory.

Prior to running the log import tool upgrade the whole environment to 7.1 and ensure that the system and the logs are functioning correctly.

These instructions assume the import is being performed on a Windows master – the procedure is the same on Linux systems barring the tool name and path formats.

Procedure

  1. Ensure the Protector services are running.

  2. In a command prompt (or terminal) navigate to the Protector/bin directory. To perform an import using defaults issue the following command:

    > log-import.exe

    This will import the previous 13 weeks of logs (and statistics logs) from the pre 7.1 logs database into the 7.1 database.

    WARNINGThere must be sufficient free disk space for the import. The amount of free disk space should be at least double that of the size of the ‘<Protector>/db/saves/logdaemon’ directory.

    For a more detailed description of the log-import cli tool refer to <link to Porting legacy logs in to a newly upgraded 7.1 log database> (this is a new section to be created as defined below)

 

  • Was this article helpful?