Viewable by the world

The IBM Tivoli Storage Manager (TSM) provided by UC Berkeley, is being discontinued on October 31, 2020. Systems using this service will need to be configured by October 31, 2020 at the very latest to ensure that data continues to be backed up.

Important dates to consider when making your decision:

October 31, 2020

  • Last day to have your system backed up using the current TSM backup service

  • Last day to perform self-service restores

November 1, 2020

  • Assisted TSM restore becomes available. Restores may experience delays of up to 4 business days compared to self-service restores

December 31, 2020

  • Last day assisted TSM restores available. If you decide to wait until after October 1 to migrate off of TSM, your backed up data will have less than a 90-day retention period


In order to ensure that your data remains protected, you will need to choose a new backup solution and configure your system(s) to use the new solution before UC Berkeley turns down the existing service.

UC Berkeley is migrating their campus users to a new software solution provided by Commvault.  You can choose to use this new service facilitated by the LBL IT Division.  More information about the UC Berkeley Commvault service is available below.

The IT Division can also help facilitate use of other backup software (open source or commercial) that utilizes cloud storage from providers like AWS or Google with easy cloud storage billing to your LBL project code.  More information about some of those options and how to set up cloud storage accounts that bill to your LBL project code is available at https://go.lbl.gov/backup-resources. Please contact [email protected] with questions about these options.

UC Berkeley Commvault Service

  • Server backups work similarly to the current TSM Backups

  • Software agent installed on your systems, no need to open any firewall ports on the clients.

  • Option to have up to two copies of data stored on UC Berkeley storage infrastructure (San Diego and Berkeley) - This is planned to become private cloud storage by January 1, 2021.

  • Monthly costs for backed data are $0.28/GB (per month) for the first copy and $0.17/GB (per month) for a second copy if your data is backed up to both the UC Berkeley campus and the UC Berkeley infrastructure at UC San Diego.

  • There is no extra charge for restoring data from your backups.

  • All costs are billed to your project/activity as a recharge each month, no PO or new procurement is required

  • Client defined retention policy - current standard is 90 days

  • 24X7 self-service restore capability via web interface

  • Data encryption keys managed by UC Berkeley and LBL IT Division.  Help is available to restore data or reset account passwords if you lose access to your credentials.

  • Options include a single administrator per server using the administrator email or creating an administrator group allowing for multiple administrators. If you want to get your server managed by multiple backup admins, create a Google Group account (https://identity.lbl.gov/creategroups/) and use its email address as login credential. 

If you would like to use the UC Berkeley Commvault service please contact the IT Backup services team at [email protected] at your earliest convenience to coordinate setting up your new account and options.

Installation

Once all necessary configuration information is collected, you will be provided with a software download link and an XML file containing the proper configuration. You can customize the exclude/include using the web interface after the installation.

Transition and billing

Once Commvault backups start, UCB normally runs the systems in parallel for a few weeks or so while building up a full set of Commvault backups (we can reduce the time or stop TSM backups earlier if dual backups cause any problems).

After that, UCB retires TSM and switches to Commvault for billing.  UCB will initially lock your billing into a range representing the last 6 months of TSM backups.  This gives UCB a chance to avoid any nasty surprises if for some reason your backup size is dramatically different on the two systems, and lets UCB figure out what's going on before there's any fiscal impact.


  • No labels