|
From: Don jessup (djessup72, yahoo dot com) Date: 2001.10.03 - 09.54 MDT
Here is the software scenario/sequence diagram for a new module called the Antera Backup Manager. I decided that there was probably enough common funtionality in a backup that it could be put in it's own software component. If we keep this module we may not need a ADC, at least for backups. By the way, I used notepad to do the document. Let me know what you think. After doing this I realized it would be better if I worked on the individual component docs that we talked about. don __________________________________________________ Do You Yahoo!? Listen to your Yahoo! Mail messages from any phone. http://phone.yahoo.com Purpose: Show's a Scheduled Backup by the Antera Backup Manager. CRON ABM SNAPSHOT_FS BACKUPSERVICE TAPE FS DATA EHANCEMENT | | | | | | | 1. |------>| | | | | | | | | | | | | 2. | |------->| | | | | | | | | | | | 3. | |------->| | | | | | | | | | | | 4. |------>| | | | | | | | | | | | | 5. | |------->| | | | | | | | | | | | 6. | |--------|------------>| | | | | | | | | | | 7. | | | |-------->| | | | | | | | | | 8. | |<-------|-------------| | | | | | | | | | | 9. |->| |--------|-------------|---------|-----|------>| | | | | | | | | 10. | | |<-------|-------------|---------|-----|-------| | | | | | | | | 11. | | |--------|------------>| | | | | | | | | | | | 12. | | | | |-------->| | | | | | | | | | | 13. | | |<-------|-------------| | | | | | | | | | | | 14. | | |--------|-------------|---------|---->| | | | | | | | | | 15. |<-| | | | | | | | | | | | | | 16. | |------->| | | | | 1. The cron starts the ABM “Antera’s Backup Manager” at a scheduled time. 2. The ABM creates the LVM snapshot volume. 3. The ABM mounts the LVM snapshot volume. 4. The ABM generates a list of files to back up based on their extended attributes from the snapshot volume. 5. The ABM generates a flat file containing all the metadata differences since the last full backup of the filesystems metadata from the snapshot volume. 6. The ABM sends this metadata file to the backup service for backup. 7. The backup services commits the file to the backup medium. 8. The backup service informs the ABM that the backup completed. 9. The ABM sends a batch list of files to the Data Enhancement module. 10. The Data Enhancement module prepares ( virus checking, encryption, compression ) a batch of files for backup and notifies the ABM when it is done. 11. The ABM sends the list of prepared files to the backup service. 12. The backup service copies each of the prepared files to a secondary medium. 13. The backup service informs the ABM that the backup completed. 14. The ABM marks the files as on backup medium. 15. Repeat steps 9 thru 14 until list of files in step 4 is exhausted. 16. The ABM removes the snapped volume. Exceptions: 1. A currently running backup is already in progress. 2. Backup can not complete because of a tape error. 3. A virus is found. Notes: Is the GUI responsible for the following 1. Rescheduling a backup. 2. Scheduling a backup. 3. Stopping a scheduled backup. In other words who manages the cron facility? This scenario allows for checks on individual files before backup. We might just want to treat every file alike. Here is the software scenario/sequence diagram for a new module called the Antera Backup Manager. I decided that there was probably enough common funtionality in a backup that it could be put in it's own software component. If we keep this module we may not need a ADC, at least for backups. By the way, I used notepad to do the document. Let me know what you think. I probably will not get all the documents done tonight. don -- This is the antera mailing list. To unsubscribe, email majordomo, cryptofreak dot org with message body `unsubscribe antera'. Or, for more information, visit http://www.cryptofreak.org/.
This archive was generated by hypermail 2b30 : 2001.10.04 - 03.00 MDT |