Projet CrashPlan EPFL

Résultat appel d'offres sur invitation

Trois fournisseurs furent sollicités dans le cadre de l'appel d'offres: Code42, DataCastle et Druva. Code 42 fournit une offre CrashPlan et Druva une offre inSync. Voici la conformité avec les critères de l'appel d'offres:

    Code 42
CrashPlan
Druva
inSync
MANDATORY REQUIREMENTS    
  [1] As a end user, I am able to use any of these Endpoints OS (this implies that all features and criteria described hereafter apply to these operating systems    
1.a Windows (7 and later) yes yes
1.b Mac (OS X 10.9 and later) yes yes
1.e Ubuntu (14.04 and later) yes yes
  [2] As an end user or entity admin (faculty or central service, etc.)    
2.a I am authenticated by AD yes yes
  [3] As an institution, I want that my data to be secure    
3.a If the backup of the data transits on the Internet, encryption (at least AES-128) is done before sending to the server yes yes
3.b If the backup is done only inside the EPFL network, or by VPN, any encryption would suffice, provided that it is not only encoding (type Base64). yes yes
  [4] As an institution    
4.a I want the solution be able to support up to 5'000 endpoints yes yes
4.b I want agents on devices contact the server (not the reverse) yes yes
4.c I want the solution runs on EPFL premises yes yes
4.d I want data be stored on physical DAS Hard Disks yes yes
4.e I want the server-side of the backup solution to run on Windows 2012 R2 (or later) or on Linux RedHat (7.x or later) yes yes
  [5] As an end user    
5.a I am able to control & manage my own backup/restore through the dedicated client or a simple web interface (frontend) yes yes
5.b I can see my own statistics (GB backed up, frequency, last backup, backed up devices, etc.) yes yes
5.c I can select directories to be backed up (Data) yes yes
5.d I can configure the Backup solution autonomously, without help of central IT staff. If and only if the user is a local admin or has root access, this includes installation. yes yes
  [6] As main admin    
6.a I can manage the solution globally (all users) and can delegate management of a subset of features (see points below) to faculty IT staff (entity admins) yes yes
6.b I can delegate to any entity administrator the possibility to add new devices to backup in the organizations they manage yes yes
6.c I can delegate to any entity administrator the possibility to remove devices (i.e. stop backing them up) from the organizations they manage, regardless of who previously added the devices. yes yes
6.d I can delegate to any entity administrator the possibility to define quota within boundaries of their organizations (by user, by device type (smartphone, tablet, desktop or laptop computer), by operating system, by device) yes yes
6.e I can delegate to any entity administrator the possibility to define quota exceptions within their organization. yes yes
6.f I can adjust the Data retention time between one to six month yes yes
6.g In addition to the support on the supplier's website, all EPFL's main admins can have direct technical support (by email, call phone, videoconference, etc.) from expert of the Backup solution in less than 4 business hours. yes yes
OPTIONAL REQUIREMENTS    
  [1] As Institution    
1o.a All data can be stored on a NetApp NAS (OS:ONTAP 9.1, server Netapp: FAS 8040) yes yes
1o.b All data can be stored on SDS (Software Defined Storage) solutions (block storage) yes yes
1o.c Backup solution also works securely from point to point on external Cloud yes yes
  [2] As user    
2o.a I can share my data for file collaboration no no
2o.b I can migrate my data from an old endpoint (on all supported OS) and be able to restore my data and my personal settings to my new endpoint. yes yes
2o.c I can restore my documents or mobile device data securely from anywhere in the world. Restore is done safely through the Frontend via https or through the Backup solution client. yes yes
2o.d I can control the CPU, memory and network bandwidth the backup client is allowed to use when I am present (working on my computer) or away yes yes
2o.e The backup starts silently and automatically yes yes
2o.f My backup client can run on Linux RedHat (7.1 and above) yes no
2o.g My backup client can run on CentOS (6.6 and above) yes yes
2o.h I can decide to hide, by encryption, my own data backed up in the storage servers (my data is hidden to backup administrators) yes yes
2o.i I can backup my mobile device (At least iOS, Android) anywhere in the world no yes
2o.j I can manage Network policy (Ex: no backup if 3G, backup only on intranet...) yes yes
2o.k In order to avoid costly overage charges, I can disable the backup process for any wireless network yes yes
2o.l I can schedule my preferred backup times by choosing a week day and time. Example: each weekday at 1 AM. no yes
2o.m I am associated via AD to the entity, or to the entities, to which I belong (i.e. where my user account lies) yes yes
  [3] As a entity admin (faculty or central service, etc.)    
3o.a I can see my global entity statistics (GB backed up, frequency, last backup, backed up devices, etc.) yes yes
3o.b I can access the Frontend to see any entity's user statistics (GB backed up, frequency, last backup, backed up devices, etc.) yes yes
3o.c I can access the Frontend to see global users statistics (Ex: Ranking of users by volume of data, etc.) yes yes
3o.d I can access the Frontend to check the use of each of my users: GB backed up, frequency, last backup, backed up devices, etc. yes yes
3o.e I can access the Frontend to manage the quotas of my users yes yes
3o.f I can access the Frontend to manage my users backup strategy if necessary (Ex: schedule backup, exclude directories, etc) yes yes
3o.g I can access the Frontend to assign a "standard" or default policy to my users yes yes
3o.h I can access the Frontend to define VIP policy: more quotas for specific users yes yes
3o.i I can schedule the preferred backup times for the users I manage by choosing a week day and time. Example: each weekday at 1 AM. no yes
3o.j I am authorized by a dedicated AD admin group yes yes
  [4] As main admin    
4o.a If needed, I can use scripts to facilitate deploying the solution throughout the organization (Ex: automatic installation and configuration of the new backup clients on Windows, Mac and Linux). yes yes
4o.b The data backed up is replicated to at least two backup storage locations without requiring each client to copy its data to the secondary location. Replication mechanism can rely on OS features and is to be explained. no yes
4o.c I can scheduled reports and alarms (for example, if free storage falls below 1TB, etc.) can be sent to administrators (main or/and entity) when there is an issue that requires their attention. yes yes
4o.d I can provide audit reports and usage reports (storage used, user count by entity, total user count, etc.) yes yes
4o.e If needed, I can use Open APIs to customize the Backup solution to meet our organizational needs. Examples: billing by entity/organisation, webservices, Reports, statistics, etc. Available APIs are to be listed and described. yes yes
4o.f I can delegate to any entity administrator the possibility to define file/folder or path exceptions that mustn't be backed up: by "sub-organization" (eg. a faculty administrator can define quotas per institute or laboratory), by user, by device type (smartphone, tablet, desktop or laptop computer), by operating system, by device yes yes
4o.g I can delegate to any entity administrator the possiility to wipe remote device (eg. in case of theft) yes (Win BitDefender) yes
4o.h I can delegate to any entity administrator the possibility to restore a device in the scope of their delegation without support of central IT staff yes yes
4o.i The existence of a delegation on part of the infrastructure mustn't grant any privileges to other parts of the infrastructure or the central configuration yes yes
Posted by Thomas Becker on Tuesday 5 December 2017 at 15:14
Comments
RSS