Sécurité : Dispositifs de gestion de la sécurité Cisco IronPort

Sauvegardez la base de données d'un périphérique de M-gamme de Cisco à l'autre

18 octobre 2016 - Traduction automatique
Autres versions: PDFpdf | Anglais (23 avril 2015) | Commentaires

Introduction

Ce document décrit comment la sauvegarde la base de données (DB) d'un périphérique de M-gamme de Cisco à l'autre.

Contribué par Fraidoon Sarwary, ingénieur TAC Cisco.

Conditions préalables

Conditions requises

Cisco recommande que vous ayez la connaissance des versions 7.2 et ultérieures d'AsyncOS.

Problème

Commencez la sauvegarde du DB à un périphérique secondaire de M-gamme.

Solution

Voici les conditions requises avant que vous commenciez la sauvegarde du DB à un périphérique secondaire de M-gamme.

  • Les deux périphériques de M-gamme doivent être sur la même version d'AsyncOS (7.2 et plus tard seulement)
  • Le périphérique de M-gamme de cible doit avoir assez d'espace disque pour la sauvegarde. Naviguez vers l'administration système > la Gestion de disque (voir la documentation en ligne sur la façon dont allouer si un certain disque est laissé plus de).

Si vous n'avez pas assez d'espace disque pendant l'installation, vous pourriez recevoir un message semblable à ceci :

Verifying target machine for version compatibility and disk space...
Backup cannot be scheduled. Reason: There is not enough space for Centralized
Spam Quarantine, Centralized Email Tracking, Centralized Reporting. Please
increase disk allocation for these services on the target machine.


OU

Verifying target machine for version compatibility and disk space...
Backup cannot be scheduled. Reason: There is not enough space for Centralized
Web Tracking. Please increase disk allocation for these services on the target
machine.


Vérifiez le quota disque comme mentionné précédemment sur la machine cible.

Les deux appliances de Gestion de la sécurité (SMAs), un M650 (source de système m650sma.run Désigné de DB), et cible M1050 (sauvegarde de destination de système m1050sma.run Désigné et IP 192.168.15.1 de DB).

Ouvrez une session au CLI sur la M-gamme de source (dans notre test sma1.example.com) et sélectionnez ces commandes :

sma1.example.com> backupconfig

Choose the operation you want to perform:
- VIEW - View scheduled backups
- VERIFY - Verify if backup can be scheduled to a remote machine
- SCHEDULE - Schedule backup to an appliance
- CANCEL - Cancel a scheduled backup
- STATUS - Show the status of a backup in progress.
- SETUP - Configure backup parameters.
[]> setup

Enter level of verbosity:
[0]> 0<this can be 0 or 3 0=lowest verbosity of backup logs and 3= highest>

Compression is desirable on slow connections, but will only slow down
 backup on
fast networks. Would you like to enable compression? [N]>   
<hit enter here to pick default withing the brackets [N]>

Choose the operation you want to perform:
- VIEW - View scheduled backups
- VERIFY - Verify if backup can be scheduled to a remote machine
- SCHEDULE - Schedule backup to an appliance
- CANCEL - Cancel a scheduled backup
- STATUS - Show the status of a backup in progress.
- SETUP - Configure backup parameters.
[]> verify

Enter the IP address of a machine to transfer data to.
[]> 192.168.15.1

Enter a name to identify this appliance
[]>sma2.example.com

Please enter username and password:
Username:
[]> admin

Password:
[]> <enter admin password for the target SMA>
Verifying target machine for version compatibility and disk space...
Backup can be scheduled on to 192.168.15.1.

Choose the operation you want to perform:
- VIEW - View scheduled backups
- VERIFY - Verify if backup can be scheduled to a remote machine
- SCHEDULE - Schedule backup to an appliance
- CANCEL - Cancel a scheduled backup
- STATUS - Show the status of a backup in progress.
- SETUP - Configure backup parameters.
[]> schedule

Enter the IP address of a machine to transfer data to.
[]> 192.168.15.1

Enter a name to identify this appliance
[]>sma2.example.com

Please enter username and password:
Username:
[]> admin

Password:
[]> <type the admin password on the target SMA>
Verifying target machine for version compatibility and disk space...
1. Set up a repeating backup schedule
2. Schedule a single backup
3. Start a single backup now
[1]>

1. Daily
2. Weekly
3. Monthly
[1]> 3

What day of the month would you like the backup to occur?
[1]>  <hit enter here>

What time of day would you like the backup to start?  Please enter in HH:MM
format.
[]> 02:00

Please enter a name for this backup job:
[]> weekly

Backup "weekly" has been scheduled successfully.

Choose the operation you want to perform:
- VIEW - View scheduled backups
- VERIFY - Verify if backup can be scheduled to a remote machine
- SCHEDULE - Schedule backup to an appliance
- CANCEL - Cancel a scheduled backup
- STATUS - Show the status of a backup in progress.
- SETUP - Configure backup parameters.
[]> view

Scheduled Backups:
# Name   IP              Schedule
= ====== =============== ================================
1 weekly To 192.168.15.1 on day 1 of every month at 02:00


Choose the operation you want to perform:
- VIEW - View scheduled backups
- VERIFY - Verify if backup can be scheduled to a remote machine
- SCHEDULE - Schedule backup to an appliance
- CANCEL - Cancel a scheduled backup
- STATUS - Show the status of a backup in progress.
- SETUP - Configure backup parameters.
[]> <hit enter until your back in CLI>

sma1.example.com> commit

Please enter some comments describing your changes:
[]> scheduled a weekly backup

Changes committed: Wed Mar 16 18:09:51 2011 GMT
sma1.example.com>


Document ID: 117840