DS News

DS News June 2019

DSNews delivers stories, ideas, links, companies, people, events, and videos impacting the mortgage default servicing industry.

Issue link: http://digital.dsnews.com/i/1121263

Contents of this Issue

Navigation

Page 72 of 99

» VISIT US ONLINE @ DSNEWS.COM 71 cases are environments that are already heavily virtualized. e relevant VM images can then simply be copied, where they would be ready for service restoration on demand. An ideal infrastructure cloud service provider will likely have the application architecture described and managed in an orchestration tool or other cloud infrastructure management system. With these, replicating the functionality can be a simple activity. e worst recovery-elapsed time is probably when functionality is replicated only when disaster strikes. A better solution is the active- passive form, where resources are held on standby. In active mode, the replicated resources are participating in the production. Planning, Preparing, and Provisioning: is is the functionality around processes that lead up to the actual DR failover response. e most important factor in this category is adequate monitoring so that more time is available. Failover Capability: Appropriate load balancing is required to ensure that redirection of the user service requests occurs properly and in a timely manner. SMARTER SOLUTIONS It is easy to see why many firms elect to make the cloud part of their solution. According to the 2017 Legal Technology Survey from the American Bar Association, cloud usage grew more than 40% from 2016 to 2017, from 37% to just over 52%. If you are ready to make that move, there are some things you need to consider. » Assessing the risks associated with a cloud service provider (CSP): · e elasticity of the CSP: Can the CSP provide all the resources if BCDR is invoked? · Contractual issues: Will any new CSP address all contractual issues and SLA requirements? · Available network bandwidth for timely replication of data. · Available bandwidth between the impacted user base and the BCDR locations. · Legal and licensing constraints that could prohibit the data or functionality to be present in the backup location. » Common pitfalls of cloud computing: · On-premises apps do not always transfer since many older apps were not developed with cloud-based services in mind making it difficult to "forklift" them to the cloud with minimal or no changes. · Lack of training and awareness: New development techniques and approaches require training and willingness to utilize new services. When cloud-based environments are required/requested, this may introduce challenges with IT staff. · Lack of documentation and guidelines: Best practices require developers to follow relevant documentation and methodologies. Given the rapid adoption of evolving cloud services, this has led to a disconnect between the CSP and application developers on how to utilize, integrate, or meet vendor requirements. · Complexities of integration: Integrating new applications with existing ones is a key part of transitioning to the cloud. When developers and operational resources do not have open access to supporting components and services, integrations can be complicated and troubleshooting becomes difficult. » Make sure your CSP has service level agreements that align with your needs: · Availability (for example, 99.99% of services and data) · Performance (expected response times versus maximum response times) · Security and privacy of the data (encrypting all stored and transmitted data) · Logging and reporting (audit trails of all access and the ability to report on key requirements and indicators) · DR expectations (worse-case recovery commitment, RTOs, the maximum period of tolerable disruption) · Location of the data (ability to meet requirements or consistent with local legislation) · Data format and structure (data retrievable from the provider in a readable and intelligent format) · Portability of the data (ability to move data to a different provider or to multiple providers) · Identification and problem resolution (help desk/service desk, call center, or ticketing system) · Change-management process (updates or new services) · Exit strategy with expectations on the provider to ensure a smooth transition e cloud is the future, but it must be embraced wisely. An ideal infrastructure cloud service provider will likely have the application architecture described and managed in an orchestration tool or other cloud infrastructure management system. With these, replicating the functionality can be a simple activity.

Articles in this issue

Links on this page

Archives of this issue

view archives of DS News - DS News June 2019