Available On Demand
The last several years have seen tech vendors relentlessly pushing customers to store all of their data in the cloud. While it is true that cloud storage use is at an all-time high, it is also true that data does not have to reside on a particular cloud forever. Changing business needs may warrant you to bring some data back on premises. Likewise, an organization may wish to migrate its data to a less expensive cloud or implement a multi-cloud strategy. Whatever the reason, data egress plans are often thwarted by the cost of the transfer. Megacloud providers often build in data egress fees as a way of disincentivizing the removal of data. This webcast explains what you need to know about data egress. You will learn:
- Why data egress is sometimes necessary
- The dirty tricks that cloud providers use to lock you into their service
- Other things to consider before moving your data
- Alternative cloud service providers that offer transparent, predictable pricing without egress fees
If you have already registered, click here to access
Brien Posey is a 15-time Microsoft MVP with over two decades of IT experience. Prior to becoming a freelance writer and speaker, Posey was the Chief Information Officer for a national chain of hospitals and healthcare facilities. Previously, Posey served as the lead network engineer for the United States Department of Defense at Fort Knox, and as a network administrator for some of the largest insurance companies in America. In addition to his continued work in IT, Posey has spent the last two years training as a commercial Scientist-Astronaut candidate for a mission to study polar mesospheric clouds from space.
Trenton R. Baker is the Sr. Product Marketing Manager for KeepItSafe, a j2 Global company based in Hollywood, CA. Trenton’s experience includes 20+ years in the tech industry, particularly focused upon B2B solution-centric technologies for virtualization, software-defined storage, and cloud-based backup and disaster recovery. Follow Trenton on Twitter @Cerebreate or @KeepItSafe.