There's a much lower risk of data transfer issues when performing offline migration because physical storage media and local uploads are generally more reliable than using the internet. Some data may also need to be recopied due to failed transmissions over a flaky connection, exacerbating the time and difficulty required to perform online migration. If a network connection is intermittent - or bandwidth availability fluctuates unpredictably - an online migration could take longer than is acceptable. The reliability of the network connection must also be considered when evaluating on-premises-to-cloud migration methods. And the faster the migration is completed, the fewer differences there are likely to be. However, the amount of syncing to perform will depend on how much difference there is between the on-premises and cloud-based copies of the data once the migration is complete. Tools like rsync - which supports copying only those files that are different between two data sources - or commercial tools based on rsync, are useful for this purpose. Another approach is to perform the migration, then do a data sync between the on-premises and cloud-based data copies that only updates the data that has changed since migration. However, that might not be acceptable if you have mission-critical workloads that can't be suspended. One way to address this challenge is to shut down workloads prior to migration so data remains consistent between the on-premises and cloud-based copies. This happens because data will constantly change while workloads are running, so if you begin migration based on one version of on-premises data, the on-premises data is likely to change by the time the migration finishes. This is crucial if workloads remain operational on premises while migration is underway, the data moved into the cloud might end up being different than the most up-to-date data that exists on premises. Total transfer time is important to consider not just because it determines how long the migration process will take, but also how much data syncing must be performed post-migration to ensure the cloud-based copy of your data perfectly represents the most recent on-premises version of the data. However, 1,000 TB would likely take more than 100 days to transfer over the same network connection - in which case, an offline migration would be a better approach. Although an online migration might be the easiest and most popular choice, it can be problematic for organizations with large amounts of data and a strict migration time frame.įor example, if an organization has only 1 TB of data to migrate and a 1 GBps network connection is available, the online migration should take under three hours using a standard internet connection. The biggest factors to consider when choosing an on-premises-to-cloud migration method are how much data you need to move and how quickly you have to move it. Most cloud providers don't charge ingress fees for incoming data - they only charge for egress, meaning data that leaves their clouds - so there's no added cost due to ingress. Online migration typically also offers cost savings compared to offline approaches, because the only expense is whatever it costs to pay for the bandwidth necessary to transfer data from on premises to a cloud. Online migrations are simpler overall because IT teams can copy data in one step from their local infrastructure to the cloud. What is online cloud migration?Īn online cloud migration uses a network - either a cloud provider's direct connection service or the public internet - to transfer data and applications to a cloud data center in real time. They must also manage the physical security risks that could arise from unauthorized parties accessing portable storage media that contains sensitive data. This method also typically requires more planning and effort than an online migration because admins must acquire portable storage media and manage the multistep process of moving it physically to a cloud provider. This on-premises-to-cloud migration approach usually costs more than an online transfer because enterprises need to rent or purchase large volumes of storage media, and then pay to relocate it. Once data is in the cloud, the offline migration is considered complete and the portable storage media can be decommissioned or reused. After that, the provider uploads the data to its cloud via a local network connection - which is faster than the public internet - or connects the storage media directly to its cloud servers. Under this method, admins acquire portable storage media, copy data from local systems onto it, then physically deliver the media to a cloud provider. In an offline migration, an enterprise uses physical storage media - such as portable disk drives or storage appliances - to move workloads to a cloud environment.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |