Carnegie Mellon University School of Computer Science ———
Quick Links: StudentsFacultyStaffSubmit a Ticket
~help  /  Backup  /  Archival Service Retirement Project  /  Project Frequently Asked Questions

Archival Backup Retirement Project

Frequently Asked Questions

Expand the sections below to find answers to common questions about backup options moving forward.

No. The service is intended for servers. The Crashplan Data Protection service is recommended for laptops and singe use desktops.
No. Campus Cloud Backup protects active systems for operational recovery. Long-term archival storage is not currently part of the service.
The standard service provides 30 days of daily backup retention.
Authorized IT staff can use the Commvault Command Center for granular file-level recovery.
Not by itself. Full disaster recovery and site failover require additional planning and consultation.
When a server is unenrolled, its retained backup data expires after the standard 30 day retention window.

To begin a migration to the Computing Services backup service, your department will need the following:

Administrative Requirement

  • An authorized representative who can submit and manage service requests
  • Required privileged administrative accounts with Duo/2FA

Billing Requirements

  • A valid Oracle string for recharge billing

Technical Requirements

  • A supported server operating system
Computing Services will work with the system owner to determine the appropriate option. Depending on the system, this may include upgrading the system to support Commvault, using another data protection approach, removing the system from backup, or retiring the system.

Systems currently enrolled in the SCS Archival Backup Service (Teradactyl TiBS) that migrate to the new Computing Services Backup Service will receive a new full backup in Commvault. Historical TiBS backup data will not be transferred or imported into the new service.

Historical backups for systems currently subscribed to the SCS Archival Backup Service will remain on the legacy TiBS infrastructure and be available for restores for a limited period following migration. A final retention date has not yet been determined.

Because TiBS is a legacy platform and the underlying infrastructure is aging, the long-term availability of historical backup data cannot be guaranteed. Customers with specific historical data retention requirements should consider whether an appropriate long-term storage or archival solution is needed.

Additional information about the retention of historical TiBS backups, including the date after which restores will no longer be available, will be communicated once those details are finalized.

Learn More

Need Help?