Hi Kate, At the 2016 PASIG and iPRES conferences, Matthew Addis gave a shot talk on this topic: - Here’s someone’s blog summary: https://preservationmatters.blogspot.nl/2016/10/exit-strategies-and-techniques-for.html - Here’s his PASIG slides: https://ipr16.organizers-congress.org/frontend/organizers/media/iPRES2016/_PDF/IPR16.Proceedings_4_Web_Broschuere_Link.pdf - Here’s his iPRES paper abstract: https://ipr16.organizers-congress.org/frontend/organizers/media/iPRES2016/_PDF/IPR16.Proceedings_4_Web_Broschuere_Link.pdf
Related literature from the iPRES proceedings: - Schaffer, H. Will You Ever Need an Exit Strategy? In IT Pro. 4-6. March/April 2014 https://www.computer.org/csdl/mags/it/2014/02/mit2014020004.pdf Warm regards, Erwin Erwin Verbruggen Project lead R&D T +31 35 677 16 91 | M +31 6 153 603 71 Skype: erwinverbruggen Netherlands Institute for Sound and Vision Media Parkboulevard 1, 1217 WE Hilversum | Postbus 1060, 1200 BB Hilversum | beeldengeluid.nl > On 17 Jan 2017, at 15:15, Beaudet, David <d-beau...@nga.gov> wrote: > > Kate, I saw your question last week and happened to be in AWS training so I > asked a gentleman who works for AWS sales to get his perspective. Not too > surprisingly, he suggests engaging professional services to assist in an exit > from AWS. > > ---- > > "Professional services or a partner would be the fastest way to recover data > when exiting AWS. A cloud provider going out of business is a real concern > when you're dealing with smaller providers. As you know the cloud industry is > simultaneously growing and consolidating on a few major providers at a very > fast rate. Having worked for a smaller IaaS provider, I've seen the > difficulty for smaller providers to compete via product and financially (very > thin margins if your platform is not fully automated, which most "cloud > providers" are not). With Azure and AWS, going out of business is a small > risk. Google you could be a little more leery of them pulling the plug since > they have a history of stopping major initiatives (Google Glass, Google > Fiber). > > > > With AWS, we have a standard term agreement with 30 days guaranteed that AWS > will not touch your environment (https://aws.amazon.com/agreement/). This can > be negotiated when you establish an Enterprise Agreement with AWS. As a > self-service platform, AWS does not offer support migrating clients out." > > ---- > > > > Regarding recoverability of cloud-based data, I asked him whether he thought > it would make sense to push backups to another cloud provider. > > > > ---- > > "Certainly pushing backups to another provider is an option. My thought is, > does the risk justify the cost in this scenario. If you're with the major 3 > cloud players, I see very little risk of the provider going under, and you'll > have to pay storage and data transfer fees to the duration of this strategy. > Based on the size of your environment, it may be worth saving the money and > being prepared to pay for professional services to help you exit efficiently > in the off chance you need to make a quick exit." > > ---- > > > > Happy to put you in touch with him directly if it would be useful. > > > > Dave Beaudet > > National Gallery of Art > > _______________________________________________ > You are currently subscribed to mcn-l, the listserv of the Museum Computer > Network (http://www.mcn.edu) > > To post to this list, send messages to: mcn-l@mcn.edu > > To unsubscribe or change mcn-l delivery options visit: > http://mcn.edu/mailman/listinfo/mcn-l > > The MCN-L archives can be found at: > http://www.mail-archive.com/mcn-l@mcn.edu/
_______________________________________________ You are currently subscribed to mcn-l, the listserv of the Museum Computer Network (http://www.mcn.edu) To post to this list, send messages to: mcn-l@mcn.edu To unsubscribe or change mcn-l delivery options visit: http://mcn.edu/mailman/listinfo/mcn-l The MCN-L archives can be found at: http://www.mail-archive.com/mcn-l@mcn.edu/
