HP StorageWorks 12000 - Virtual Library System EVA Gateway Manual page 178

cartridges. For example, if you create 1000 cartridges in the replication target is can take 40
minutes create the matching 1000 cartridges on the source device and complete the "Adding
Cartridge" operations for all 1000 cartridges.
• Up to Date. The source virtual cartridge is fully synchronized with the matching target cartridge
(i.e., the mirror is in sync).
• Waiting for Backup Data. Waiting for the backup application to update the source virtual cartridge
(append or overwrite with new backup data). Note that replication is only performed on backups
that occur after the replication configuration is performed, so even if there are existing backups
on the source virtual cartridges when replication is configured they won't replicate until they are
updated.
• In Use. The source virtual cartridge has been loaded into a virtual tape drive (this always overrides
any replication job which will be restarted once the cartridge is unloaded from the drive).
Once a source virtual cartridge has been modified with new backup data, then the cartridge is queued
for replicating with the following states:
• Backup Postprocessing. The source virtual cartridge has been modified but replication is waiting
for the deduplication to finish analyzing it to determine what data is unique in the new backup.
(All data is unique if this is a new backup, if deduplication was disabled in the GUI for this backup,
or if the backup data type is not supported by deduplication.) Virtual cartridges that have been
pre-formatted by the backup application (e.g., Data Protector) but have not been used yet for
backups will also appear in this state.
• Out of Sync. The source virtual cartridge has been modified (last mirror date on the source virtual
cartridge is newer than its last write date) and is ready for replication (deduplication has finished
analyzing it) but is currently outside of the replication window policy defined in the echo copy
pool. The "Copy Now" task can be used to manually override the replication window.
• Mirror Scheduled. When the replication window starts, the modified source virtual cartridge is
queued up for processing. If a source virtual cartridge is modified within a replication window
then it will be added to the queue as soon as the backup postprocessing is complete (it does not
have to wait until the next window starts).
The queued cartridges are then processed, running as many concurrent replication jobs as allowed
based on the "max jobs" setting in the replication target on the target device (the default is to run four
replication jobs concurrently). You can view the active jobs in the replication job reporting screens
but the following source cartridge states also show the progress of an active job:
• Mirror Preprocessing. The active replication job is gathering together all the data needed for the
replication transfer including the unique data (the deltas) on the cartridge and replication metadata.
• Mirroring. The active replication job is transferring the data (deltas plus metadata) over the
LAN/WAN link to the target device.
• Mirror Postprocessing. The active replication job has successfully transferred the delta data over
to the target device and is now converting it to a fully intact cartridge on the target device (to
provide maximum restore performance).
• Mirror Broken. This state shows an unexpected error occurred while running the replication job.
You can use "Restart Broken Mirror" to attempt to recover from the error.
• Restoring. This state is when a Restore over LAN/WAN is being performed.
NOTE:
If an active replication job was interrupted (e.g., the cartridge was loaded into a virtual tape drive
or the link failed), this will cancel/reschedule the replication job and return it to "Mirror Scheduled"
status (if within a replication window) or "Out of Sync" (if outside of a replication window) so that
the replication job is run again once the interruption is resolved.
178 Virtual Library Systems