Brocade Fabric Manager Administrator's Guide v6.1.0 (53-10000610-02, June 2008)

Fabric Manager Administrator’s Guide 225
53-10000610-02
Offline zone management
16
• For example, if you are restructuring your SAN and want to merge Fabric A with Fabric B, Fabric
A loses all of the zone databases associated with it. Prior to the merge, export the offline zone
databases associated with Fabric A so that you can later import them into the merged fabric.
• If you downgrade the seed switch, you should first export all of the offline zone databases
associated with the fabric so that you do not lose the zone databases. If you upgrade the seed
switch later, you can then import the zone databases.
You can export and import only one zone database at a time.
Concurrent editing
Concurrent editing of the same zone database is permitted only from two different clients. When
editing the live zone database, the last save operation overwrites the previously saved zone
database. When you save a zone database to the Fabric Manager repository, the saved copy is
added to the set of existing zone databases.
Database reversion
If you have made modifications to the zone database that is on the fabric, saved those changes to
an offline zone database, and then saved those changes to the fabric, you can later revert back to
the version of the zone database that was on the fabric before you applied the changes.
For example, assume the zone database on the fabric contains one configuration and two zones:
Zone DB (not named): Config1, Zone1, Zone2
You modify the zone database to add a zone, save it offline as ZoneDB2, and also apply the
changes to the fabric:
Zone DB (not named): Config1, Zone1, Zone2, Zone3
ZoneDB2: Config1, Zone1, Zone2, Zone3
Another user modifies the zone database to add an alias, saves it offline as ZoneDB3, and applies
the changes to the fabric:
Zone DB (not named): Config1, Zone1, Zone2, Zone3, Alias1
ZoneDB2: Config1, Zone1, Zone2, Zone3
ZoneDB3: Config1, Zone1, Zone2, Zone3, Alias1
If you select ZoneDB3 and roll back the changes, the zone database on the fabric reverts back to
what it was before ZoneDB3 was applied:
Zone DB (not named): Config1, Zone1, Zone2, Zone3
ZoneDB2: Config1, Zone1, Zone2, Zone3
ZoneDB3: Config1, Zone1, Zone2, Zone3, Alias1
If you select ZoneDB2 and roll back the changes, the zone database on the fabric reverts back to
what it was before ZoneDB2 was applied:
Zone DB (not named): Config1, Zone1, Zone2
ZoneDB2: Config1, Zone1, Zone2, Zone3
ZoneDB3: Config1, Zone1, Zone2, Zone3, Alias1