Print Download PDF Send Feedback

Previous

Next

Backing Up

In This Section:

SecurePlatform Backup

SecurePlatform Snapshot Image Management

Before you upgrade, back up the Security Management Servers and Security Gateways.

Use the snapshot mechanism if it is available.

SecurePlatform Backup

SecurePlatform has a command line or Web GUI utility for backups of your system settings and product configuration. The backup utility can store backups locally on the Security Management Server, or remotely to a TFTP server or an SCP server. You can run the backup manually, or schedule backups.

The backups are TGZ files. When saved locally, the default path is: /var/CPbackup/backups

Backup and Restore commands require expert permissions.

Syntax:

backup [-h] [-d] [-l] [--purge DAYS] [--sched [on hh:mm <-m DayOfMonth> | <-w DaysOfWeek>] | off] [[--tftp <ServerIP> [-path <Path>] [<Filename>]] |

[--scp <ServerIP> <User name> <Password> [-path <Path>][<Filename>]] |

[--file [-path <Path>][<Filename>]]

Parameter

Description

-h

See help on the command

-d

Debug flag

-l

Enables VPN log backup (by default, VPN logs are not backed up)

--purge

Deletes older backup files, from the number of days given

--sched

Schedule backups

  • On - enter time and day of week, or date of month
  • Off - disable schedule

Example: --sched on 03:00 1

--tftp

Back up to TFTP. Enter IP addresses of TFTP servers
Optional: -path pathname of backup on TFTP

Example: --tftp 192.0.2.3 -path /var/backups/mybckup.tgz

--scp

Back up to SCP. Enter IP addresses of SCP servers, username (with access to SCP server), password, and optionally the filename

Example: --scp 192.0.2.4 usr 123 mybckup.tgz

--file

For local backups, enter an optional filename, or -path parameter and pathname

SecurePlatform Snapshot Image Management

You can back up the entire SecurePlatform operating system and installed configuration with the snapshot command. A snapshot is made automatically during upgrade with the SafeUpgrade option. You can take a snapshot manually with the snapshot command.

The snapshot and revert commands can use a TFTP server or an SCP server to store snapshots. Snapshots can also be stored locally.

Syntax:

snapshot [-h] [-d] [[--tftp <Server IP> <Filename>] |

[--scp <Server IP> <Username> <Password> <Filename>] |

[--file <Filename>]]

Parameter

Description

-h

See help on the command

-d

Debug flag

--tftp

Back up to TFTP. Enter IP addresses of TFTP servers
Optional: -path pathname of backup on TFTP

Example: --tftp 192.0.2.3 -path /var/backups/mybckup.tgz

--scp

Back up to SCP. Enter IP addresses of SCP servers, username (with access to SCP server), password, and optionally the filename

Example: --scp 192.0.2.4 usr 123 mybckup.tgz

--file

For local backups, enter an optional filename, or -path parameter and pathname

Service Contract Files

Introduction

Before upgrading a gateway or Security Management Server to R77, you need to have a valid support contract that includes software upgrade and major releases registered to your Check Point User Center account. The Security Management Server stores the contract file and downloads it to Security Gateways during the upgrade. By verifying your status with the User Center, the contract file enables you to easily remain compliant with current Check Point licensing standards.

Working with Contract Files

As in all upgrade procedures, first upgrade your Security Management Server or Multi-Domain Server before upgrading the Gateways. Once the management has been successfully upgraded and contains a contract file, the contract file is transferred to a gateway when the gateway is upgraded (the contract file is retrieved from the management).

Note - Multiple user accounts at the User Center are supported.

Installing a Contract File

Installing a Contract File on the Security Management Server

When you upgrade a Management Server, the upgrade process checks to see whether a Contract File is already present on the v. If not, you get the main options for getting a contract. You can download a Contract File or import it.

If the Contract File does not cover the Management Server, a message informs you that the Management Server is not eligible for upgrade. The absence of a valid Contract File does not prevent upgrade. You can download a valid Contract File later in SmartUpdate.

On IPSO

Contract verification on IPSO is not interactive. After successfully upgrading the gateway, the following message is displayed:

The upgrade process requires a valid contract file in order to verify that your gateway complies with Check Point licensing agreements. While the absence of a contract file does not prevent this upgrade, it is recommended that you obtain a contract file via

SmartUpdate (Licenses & Contracts menu -> Update Contracts).

For further details see: http://www.checkpoint.com/ngx/upgrade/contract/

At the earliest opportunity, obtain a valid contact file from the Check Point User Center.

Installing a Contract File On Security Gateways

After you accept the End User License Agreement (EULA), the upgrade process searches for a valid contract on the gateway. If a valid contract is not located, the upgrade process attempts to retrieve the latest contract file from the Security Management Server. If not found, you can download or import a contract.

If the contract file does not cover the gateway, a message informs you (on Download or Import) that the gateway is not eligible for upgrade. The absence of a valid contract file does not prevent upgrade. When the upgrade is complete, contact your local support provider to obtain a valid contract. Use SmartUpdate to install the contract file.

Use the download or import instructions for installing a contract file on a Security Management Server.

If you continue without a contract, you install a valid contract file later. But the gateway is not eligible for upgrade. You may be in violation of your Check Point Licensing Agreement, as shown in the final message of the upgrade process. Contact your reseller.