IT Phrase - DATA and Cloud-based DR - part 2

Cloud DR Issues
1. Network bandwidth - must have enough throughput (pemprosesan) capability between primary site and the cloud to ensure data can be replicated in a timely fashion without too much lag in concurrency and also need enough bandwidth available to recover changed data back to the primary site once DR issue is over
2. Network security - data moving to the cloud will be outside of the protection of private network in data center so data encrypted at offsite is highly required and to ensure that the encryption process does not interfere with normal operation
3. Network addressing - as application workloads are moved to the cloud, IP addresses will change. Moving an application to cloud will require changes to DNS(to point to new server/data location) and modification to the application in some cases. Compare to primary and secondary servers are kept onsite , IP addressing can be managed relatively easily either through implementing a level 3 network between sites or by routing.
4. Network latency(潜伏) -
5. Licensing - DR instances require purchasing licences, depending on the terms of the application vendor.
6. Cost - include providing the cloud services, additional network capacity, licensing dedicated backup software and extra application licenses


sources frm:

http://searchdisasterrecovery.techtarget.com/feature/Cloud-based-disaster-recovery-service-grabs-spotlight?utm_medium=EM&asrc=EM_NLN_52095022&utm_campaign=20160107_Advantages%20of%20cloud-based%20disaster%20recovery_esullivan&utm_source=NLN&track=NL-1821&ad=905194&src=905194