TIG will monitor client and third party enterprise backup solutions, such as Veritas NetBackup and Tivoli Storage Manager, including locally or remotely conducted solutions. TIG will monitor backup status via traps from SNMP-enabled backup software and events generated by system and application log files, and will notify the client or partner of issues associated with backup.

Backup Management

TIG will monitor client and third party enterprise backup solutions, such as Veritas NetBackup and Tivoli Storage Manager, including locally or remotely conducted solutions. TIG will monitor backup status via traps from SNMP-enabled backup software and events generated by system and application log files, and will notify the client or partner of issues associated with backup.

Backup Restore

Backup Restore includes the management of backups conducted by TIG or TIG partners; customer notification of failed backups; re-execution of failed or incomplete backup jobs; and the coordination of restoration from backup media.

Patch Installation

TIG assumes responsibility for testing and implementing security and functionality patches on the managed environment. TIG categorizes new software, provided by software vendors, into one of three categories: Patches, Releases, or Versions.

Patches
Software added to a production server, either to (a) protect against security vulnerability, or (b) correct the software to provide functionality described or expected in the original Release of the software. As an example, Microsoft Corporation sometimes refers to Patches as "hot fixes." If an identified patch affects the customer's environment, TIG will work with the customer's development team to test the patch in the customers test/staging environment before releasing into production.

Release
Software to update or enhance the software to provide functionality not originally described or expected in the original Version. Furthermore, the update may cure a security threat by replacing the current release with a new release of code that does not contain the vulnerability. Release management requires the removal or upgrade of the current application and replacement with the new release. Releases are customarily designated by a number to the right of the decimal point in a Version number (i.e. Version 1.1 is Version 1, Release 1, and a new Release would be designated as Version 1.2, read as Version 1, Release 2). Each Release is substantially similar to and is marketed under the same Version number (the number to the left of the decimal) and nomenclature. As an example, Microsoft Corporation sometimes refers to Releases as "Service Pack Releases," and in some cases, multiple "hot fixes" are bundled together and are included along with the Release.

Version
Software to perform a specific function set of functions, or a framework for programming functions. Versions are not marketed under the same Version number (the number to the left of the decimal) and nomenclature.