These statistics are used on some displays ( e.g. Protector stores in its logs database both logs and statistics. If your database retains logs for a year and you want to import them all then specify 52. To only import the last weeks’ worth of data then supply 1 to this option. Specify the time period, in weeks before now, from which to import data. The ‘log-import’ tool options can be displayed using the following command:

If this is not possible see the ‘Free Space Problems’ section below. The amount of free disk space should be at least double that of the size of the ‘/ db/saves/ logdaemon’ directory. Warning: There must be sufficient free disk space for the import. This will import the previous 13 weeks of logs from the 7.0 logs database into the 7.1 database. To perform an import using defaults issue the following command: These instructions are the same for both Windows and Linux masters. Any active replications must be in the paired state before you start the upgrade.įor full details on upgrade paths, see the upgrade path matrix by clicking on “View Full Specifications” here: Įnsure the Protector services are running and then in a command prompt (or terminal) navigate to the Protector/bin directory. The master should be upgraded before upgrading any clients.īefore upgrading, unmount any mounted snapshots.ĭo not upgrade while replications are pairing. Therefore, it is important to check that all features you are using are available before upgrading. Some features included in version 6.x are no longer available in version 7.x. Subsequent upgrades to any later version will support push upgrades to all supported operating systems. You must manually upgrade all Windows machines to Protector 6.7.7 or later. Prior to upgrade please refer to the upgrade section of the user guide for guidanceĭue to a change in the certificate used to sign Windows binaries, you cannot push upgrade Protector on a Windows machine until that machine is upgraded to Protector version 6.7.7 or later.

Impact integration guide 7.1