SaaS Agreements – SLA – Data Backup

When providing SaaS services you must specify in your SaaS agreement who is responsible for the backup/loss of customer data. The extent of your backup duties should be included in the service level agreement (SLA) and these will be dependent on a number of factors set out below.

Backup Process

You should set out details about the nature of the backups and the data media being used, for example:

  • will the backup be made to tape or disk or using some other media
  • how often will the backup media be changed/rotated/updated
  • how often will backups be made i.e. hourly/daily/monthly
  • will incremental backups be made

Security

In view of customer concerns over data security it is essential that you provide details of where and how the backup media will be stored, for example:

  • will this be at a physically separate location
  • will a provider other than the hosting centre be used
  • what security is in place at the storage location
  • who has access to the facility
  • is emergency power available

Disaster Recovery

This should be considered as an add on extra, to cover the eventuality that the hosting centre (where the SaaS software and data backups are created)  becomes unusable.  The disaster recovery centre should be physically remote from your hosting centre to avoid a double hit! Other points to consider are:

  • carefully define what a “disaster” is
  • set out expected data recovery times
  • test your disaster recovery procedure at least once a year

Commercial Considerations

The exact nature and extent of any data backup (and related disaster recovery) services that you offer to SaaS customers will depend on:

  • how much has the customer pays for the SaaS solution, maintenance and support
  • whether or not service credits are offered for breaches of error fix times
  • whether the SaaS application is business critical i.e. online banking
  • what is standard in that particular business area

Exclusions

Ensure that errors or problems caused by something beyond your control are excluded from your obligations i.e. loss of data caused by the customer’s failure to use the specified browser, hardware, virus checking programmes etc.

Help

Irene Bodle is an IT lawyer specialising in SaaS agreements with over 10 years experience in the IT sector. If you require assistance with any SaaS, ASP, software on demand contracts or any other IT legal issues contact me:

irene.bodle@bodlelaw.com
www.bodlelaw.com

To register for my newsletter click here

______________________________________________________

Other related articles:

SaaS Agreements – SLA – Error Fix Times

There are no standard fix times for remedying software errors, problems and bugs in a SaaS agreement.  Fix times need to be tailored to the services being provided and should be set out in the service level agreement (SLA). The following factors need to be considered when SaaS suppliers establish fix times in their SaaS agreement.

Duty to Acknowledge, Respond and Fix Errors

Time to acknowledge, respond or fix a SaaS software problem should start to run upon receipt of a customer message, from acknowledgement of the error, or some other trigger event.

Nature and Severity of the Problem

How severe is the problem or error? i.e. critical, medium or low

Is the problem an error (a software problem that can be reproduced) or is it a bug?

Type of SaaS Solution

Is the SaaS application business critical? i.e. online banking

What is standard in that particular business area?  i.e. online recruitment, accounting, banking

Commercial Considerations

How much has the customer paid for the SaaS solution, maintenance and support?

Are service credits offered for breaches of the fix times?

Practical Issues

Is there a global support hotline?

Are IT staff available to work 24 x 7?

Does the SaaS provider have access to the third party data centre?

What are the terms of the hosting agreement with the third party data centre?

Exclusions

Ensure that errors or problems caused by something beyond your control are excluded from fix times i.e. the customer’s inability to connect to the Internet.

Exclude errors or problems in the SaaS agreement which are caused by the customer i.e. the customer’s failure to use the specified browser, hardware etc.

Help

Irene Bodle is an IT lawyer specialising in SaaS agreements with over 10 years experience in the IT sector. If you require assistance with any SaaS, ASP, software on demand contracts or any other IT legal issues contact me:

irene.bodle@bodlelaw.com
www.bodlelaw.com

To register for my newsletter click here

______________________________________________________

Other related articles: