Computing at UW-MadisonDivision of Information Technology
Students Faculty/Staff Services Services A through D Services E through L Services M through R Services S through Z Help Desk Tech Store About DoIT   

Bucky Backup

Technical Overview

First, some definitions:

  • Node: A node is a container within the Bucky Backup system that holds all of the data you back up. This includes all file spaces, which in turn, includes active & inactive backed-up files, and any archives you've created.
  • Scheduler: A component of the TSM Client that is installed on your system that transfers your files to the Bucky Backup system at the scheduled time. Installing the Scheduler is part of all Client Installation instructions on this site.
  • Options file: The component of the TSM Client that defines the scope & behavior of your backups & other settings (usually dsm.opt or dsm.sys).
  • Incremental Backup: When the Scheduler examines each file within the scope of your backup and only sends over the files that have changed, or are new, since the last backup. All scheduled backups are incremental backups.
  • Archive: An archive is a point-in-time backup that is stored separately from the data backed up via the scheduler and manual backups, but in the same file space. They can only be created manually. Archives are useful if you want to store a set of files at their current versions on a permanent or only-for-X-days basis. Most Bucky Backup customers do not use archives.
  • Data Retention: The length of time that data is available for restore from Bucky Backup.
  • Number of Versions: The maximum number of versions of a file that can be stored in Bucky Backup. (ie. The X most recent versions of a particular file that have been backed up within the retention period are available for restore.)
  • Active File: A file that still exists on your system that is within the scope of your scheduled backups. The most recent version of active files are always available for restore, regardless of the retention period.
  • Inactive File: A formerly active file that is either deleted from your system, or is now outside of the scope of your scheduled backups (due to changes to your INCLUDE / EXCLUDE statements in your options file). An active file cannot become inactive until an incremental backup occurs that notices the change.
  • Management Class: A container within the Bucky Backup system that defines data retention & number of versions. There can be, and usually is, different behavior for active & inactive files. Backed-up files & archives are "bound" to a management class that defines this behavior.
  • File Space: A container within the Bucky Backup system that holds all active & inactive files, and any archives you've created, for a particular drive or partition on your system. File spaces are unique per machine name and require manual deletion if you ever want to delete them.

Scheduled Incremental Backups:

The Scheduler checks in with the Bucky Backup server every 4 hours to verify the backup schedule. It will begin an incremental backup when it is within the time frame specified by your backup schedule (this is usually every night).

A log of scheduler activity is kept in a file called dsmsched.log. There is also an error log called dsmerror.log. Please see the Tips for your particular operating system for the specific locations of these files.

If you miss a scheduled backup, or the backup fails, the Bucky Backup system sends an email to the registered Node Administrator.

What gets backed up:

Be default, all local drives / partitions on your system get backed up. You can restrict which drives & Windows Objects are considered for backup with the DOMAIN statement in your Options File. You can further restrict what gets backed up with INCLUDE & EXCLUDE statements. Please see the Tips for your particular operating system for the specifics.

Data Retention & Number of Versions:

Your default data retention & number of versions depends on what you selected when you signed up for Bucky Backup.

  • If you picked 3 versions, Bucky Backup will keep up to 3 versions of each active file for up to 180 days, and 1 copy of each inactive file for up to 180 days. The 1 exception is that the most recent version of an active file is always available for restore, regardless of when it was backed up. If you back up a 4th version of an active file within 180 days, the oldest version gets deleted from the system. Previous versions of an active file will also get deleted from the system at the end of the retention period (180 days).

  • If you picked 5 versions, Bucky Backup will keep up to 5 versions of each active file for up to 365 days, and 1 copy of each inactive file for up to 365 days. The 1 exception is that the most recent version of an active file is always available for restore, regardless of when it was backed up. If you back up a 6th version of an active file within 365 days, the oldest version gets deleted from the system. Previous versions of an active file will also get deleted from the system at the end of the retention period (365 days).

Every part of the data retention & number of versions kept described above can be changed. It can be changed for all files, or for just some. You will need to check with DoIT SysOps to see if a management class exists on the Bucky Backup server with the behavior you want, then update your options file to bind the files to that management class. Please see the Tips for your particular operating system for the specifics.

Archives:

You can manually create an archive any time you want. The easiest way is to start the "Backup-Archive GUI" and click the big Archive button. Archives will be bound to your default management class & will expire (be deleted) at the end of your default data retention period unless you click the Options button, check the "Override include/exclude list" box & pick an alternate management class. If you aren't sure what the retention periods are for the listed alternate management classes, or you want a specific one created, email DoIT SysOps.

File Space Maintenance:

If you change your machine's name, start backing up a different machine to the same node, or exclude a drive or partition from backups that used to be included, you should consider deleting your old filespaces to avoid unnecessary storage costs for your old / existing data. Please see the Tips for your particular operating system for the specifics.