PowerPoint PresentationAlcatel-Lucent University
University
During class please switch off your mobile, pager or other that may interrupt.
Entry level requirements:
How to take a manual backup via the AWS
How to schedule periodic backups via the AWS
*
NT
NT
NT
NT
BACKUP
RESTORE
AWS
The backup of a database also includes the profiles. So when you restore the configuration there’s NO need to download the profiles prior to the restore.
*
Backup Parts: ASAM Core & Service Hub
A backup of 7302 ISAM has the following 2 main blocks:
Backup of the ASAM-part
VLAN parameters
Backup/Restore features can be configured via ANEL and/or EML view
Configurable options
Configured via administration
Erase persistency = empty MIB on NT
After x number of changes
Related to SNMP set commands
Configuration
Backup/Restore
ANEL
Configuration
EML-USM
Configure
Supervision
Backup/Restore
Manual backup/restore
Performing a manual backup/restore can be done via the ANEL or EML view
The backup file name exists out of following items:
File name
For Autobackup, filename prefix is “Autobackup” and suffix is “AUTO”
For manual backup, name given by operator
ASAM release & software information
EML-USM
Backup
Restore
Files
Configuration
Backup/Restore
You can take a backup of the ASAM-CORE and of the service hub configuration data in one go: when you enter the backup command:.
From ANEL: Configuration Backup/Restore Backup
From EML-USM: Supervision Backup/Restore Backup
You can check a checkbox to backup the configuration of the service hub (subNE) too.
Backup file name examples:
Kris_L6GQAA11.618_2005_5_11_11_48_46(ASAM-core backup)
SubNE.LANX_Kris_LANX_2.0_LANX_R2.0.5.9_2005_5_11_11_50_36(SHUB backup)
It is possible to make a manual backup, or list the backup files of multiple ISAMs at the same time.
This is not possible via the EML view because then you are performing commands on that specific ISAM. But when operating in the ANEL view and selecting multiple “Supervised” ISAMs this is possible
When performing a backup on multiple ISAMs at the same time, all the backups will have the same name. But each of the backups are stored in their own specific ISAM directory on the AWS
2.bin
backup files on unix level
*
Example setup:
ftp server @ 172.31.79.244 with directory fdisam1 created in the ftp root-dir with R/W access
ftp user: isadmin, password isadmin
Define transfer protocol: TFTP / FTP / SFTP
configure system security filetransfer protocol ftp
Specify the backup server + username and password
configure system security filetransfer server 172.31.79.244 user-name isadmin password isadmin
2 options:
*
configure software-mngt database auto-backup-intvl 24
Activate automatic backup mode
configure software-mngt database backup activate:172.31.79.244:fdisam1
*
CLI - Manual backup / Restore
Mode (TFTP / FTP / SFTP) and server (user, pwd) as defined before
Remark: also FTP and SFTP manual backup/restore supported
Activate the manual backup mode
configure software-mngt database backup activate manually
To start a backup manually:
admin software-mngt database upload actual-active:172.31.79.244:dm.tar
Also ‘previous-active’ could be specified, see speaker notes
To start a restore manually:
admin software-mngt database download actual-active:172.31.79.244:dm.tar
The filename MUST be dm.tar for manual backup and restore
Verify progress
leg:isadmin>admin>software-mngt>database$ show software-mngt upload-download
===========================================================================================
===========================================================================================
actual-active:<...> ! actual database for active OSWP
preferred-active:<...>! preferable database for active OSWP
previous-active:<...> ! previous database for active OSWP
failed-active:<...> ! failed databse for active OSWP
actual-not-acti*:<...>! actual database for not-active OSWP
preferred-not-a*:<...>! preferable database for not-active OSWP
previous-not-ac*:<...>! previous database for not-active OSWP
failed-not-acti*:<...>! failed database for not-active OSWP
*
BEFORE the Restore
AFTER the Restore
- active becomes previous
After rebooting the system, the preferable becomes active and the active one becomes the previous.
Alcatel-Lucent University Antwerp
*
Exercises
Backup / Restore of ASAM-CORE and service hub
Take a manual backup of your ISAM (both ASAM-CORE and service hub!) using the AWS. How do you proceed? (2 possibilities). What is the file name given by the AWS?
Show a list of all backups of the ISAM you have been working on (2 possibilities).
Can I take a backup of multiple ISAMs at the same time? Y/N
If it possible, how? Do it. How are the different backups differentiated?
Display a list of all backup files at Unix level. In which directory do you need to look?
Restore the ASAM-CORE backup taken in (1). (Notify the other trainees working on the same ISAM!) What happens?
Can I restore ASAM-CORE backups on multiple ISAMs at the same time?
*
Exercises
Backup / Restore of ASAM-CORE and service hub
Try to find out if the automatic backup feature is active and at what time the backup is taken.
Delete the backup files you created on the AWS.
Review Questions
What is the meaning of "backing-up the ASAM”?
How can you see a list of all the backups of the ASAM available in the ASAM? (2 possibilities)
In which window can you perform a manual backup?
*