A lift-and-shift approach is simplest for most legacy applications, but for systems with a long life span, consider refactoring the design to use native cloud databases and other services. Migrate latency-sensitive applications to multiple cloud regions, using an application load balancer, such as AWS Elastic Load Balancing, Azure Front Door or Traffic Manager, or a virtual appliance, like F5 BIG-IP, to optimize client connections.Organizations that expect to have a high percentage of WFH employees after the pandemic emergency passes should consider the following storage strategies: Synchronize on-premises and cloud environments using the provider's synchronization service, like AWS DataSync or Azure File Sync, or manually using a command like rsync, and direct WFH users to the cloud shares.
Organizations with on-premises file shares using basic NAS protocols, like NFS and SMB, should migrate data to a managed NAS service, such as Amazon FSx for Windows File Server, Amazon Elastic File System, Azure Files or Google Cloud Filestore.In contrast, Avere uses a vFXT instance in the cloud as a proxy to bridge on-premises NAS filers and cloud storage on Google Cloud, Azure and others. For example, Panzura works with Amazon S3, making the cloud object store the authoritative source that replicates to Panzura filers and clients - both PC and mobile. The details of doing this will vary with the local software being used, but extending a global file system to the cloud is relatively straightforward.
Organizations with extensive and sophisticated NAS deployments, particularly those with geographically distributed storage arrays using a global file system, should integrate the existing NAS environment with their primary cloud service.The best approach would be to use one that's part of or integrated with your organization's standard productivity software - e.g., Apple iWork, Google G Suite or Microsoft 365.
0 kommentar(er)
