The Backup/Archive strategy varies depending on a variety of factors:
a.    Type of data.
b.    Is it necessary to backup/archive all data?
c.    Backup/archive scheduling window.
d.    Length of data retention.
e.    Disaster Recovery.
 

The default strategy is to run an initial full backup and then incremental backups thereafter.  Along with the above onsite retention policy, a copy of the backup/archived data will be sent to secure offsite storage, in case of a disaster.  

For workstations/laptops, it is recommended that only user data be backed up.   This minimizes the impact to the workstation’s resources and the length of the backup/archive window.  

For servers the same factors apply, but the backup may include non-user data.   The exclude list on these systems should have only files that are “always open” such as databases.  Live databases must have the data “dumped” to ordinary files for backups/archives, unless there is a TSM module available to interface directly with the DBMS. 

For critical servers, archives and “backup sets” can be done.  Archives are full backups that are intended to be retained indefinitely.  Backup sets are full backups optimized for quick recovery of entire systems.  It is not recommended that archives or backup sets be done daily but on a monthly, quarterly or yearly schedule.    Depending on the amount of data this process may take considerable time to complete and is normally done on weekends.   Backup sets are offered only for servers.  

NOTE: Special retention policy requests will be reviewed on a case by case basis.   Lower retention reduces cost, but minimizes the ability to restore from older versions.  

Please see the glossary for defination of terms.