Relocatable user backup
It is proposed that this article be deleted because of the following concern:
If you can address this concern by improving, copyediting, sourcing, renaming, or merging the page, please edit this page and do so. You may remove this message if you improve the article or otherwise object to deletion for any reason. Although not required, you are encouraged to explain why you object to the deletion, either in your edit summary or on the talk page. If this template is removed, do not replace it. This message has remained in place for seven days, so the article may be deleted without further notice. Find sources: "Relocatable user backup" – news · newspapers · books · scholar · JSTOR Nominator: Please consider notifying the author/project: {{subst:proposed deletion notify|Relocatable user backup|concern=neologism}} ~~~~Timestamp: 20091012161108 16:11, 12 October 2009 (UTC) Administrators: delete |
Relocatable user backup (RUB) is a concept which allows users to restore or relocate backups to another system or site. It is one of the primary ways to mitigate the threat of service-provider lock-in in a software as a service model.
The concept requires 3 fundamental components :
- The user must be able to initiate and receive backups from the service provider and store them locally
- The user must be able to restore the backup to an environment other than that provided by the service provider, preferably locally
- The backup must encapsulate all content, metadata, system and application state which allow the easy restoration of the backup into a standard framework either provided and maintained by the service provider or the wider software community.
The third component also contains the implication that either the application itself is provided with the backup, or there is a consistent and ongoing application upgrade path to prevent the situation where the restore of a RUB is prevented due to an obsolete version of application software.