Chapter 6
Evaluation Criteria
Rollback and recovery features should include the following capabilities:
· Once again, multi-vendor support is paramount--Using a different solution for each
vendor's products will simply increase management overhead; one solution must be able
to deal with the broadest possible range of network devices.
· Rollback should be an automated process that can be initiated only by authorized
administrators under a role-based security model--Rollback should not require an
administrator to select specific pieces of a configuration to roll back; administrators
should simply select a prior configuration version from the database and have the
solution deploy it either immediately or on a schedule.
· The ability to deploy archived configuration files to any device--At the very least, you
should be able to retrieve an archived configuration, modify it, and deploy it to a device.
This step is essential in a disaster recovery plan in which you might need to deploy
slightly modified configurations to devices at a disaster recovery facility.
Figure 6.13 shows a useful evaluation checklist for this functionality.
Figure 6.13: A tool evaluation checklist for the change rollback and recovery functionality.
125
Summary :
Chapter 6 Evaluation Criteria Rollback and recovery features should include the following capabilities: · Once again, multi-vendor support is paramount--Using a different solution for each vendor's products will simply increase management overhead;
Tags :
deploy,recoery,configuration,ealuation,solution,rollback,select,functionality,disaster,administrators,deices,simply,figure