Emc Networker Delegation Model for Robo Environment
Total Page：16
File Type：pdf, Size：1020Kb
EMC NETWORKER DELEGATION MODEL FOR ROBO ENVIRONMENT Puneet Goyal Technical Specialist HCL Comnet Table of Contents Introduction ................................................................................................................................ 4 Goal and Objective .................................................................................................................... 6 Audience .................................................................................................................................... 6 What is Delegation Model? ........................................................................................................ 6 The Concept .............................................................................................................................. 7 Understanding the customer’s backup environment and architecture ......................................... 9 Collecting features which can be used in the solution ...............................................................10 Authentication-related feature ................................................................................................10 Backup/Cloning-related feature .............................................................................................11 Recovery-related feature .......................................................................................................13 VMware-related Feature ........................................................................................................16 Storage-related feature ..........................................................................................................19 Hardware-related feature .......................................................................................................21 Support-related features ........................................................................................................22 Drawing the prototype ...............................................................................................................22 Considerations ......................................................................................................................26 Implementing the model ............................................................................................................26 Creating attributes specific to ROBO sites .............................................................................27 Authentication users with LDAP.............................................................................................27 Deciding access rights for the local IT admin .........................................................................28 Deciding the privileges ..........................................................................................................28 Creating restricted data zones (RDZ) for ROBO sites ............................................................29 Testing the console view as a local IT admin .........................................................................32 Testing recovery ....................................................................................................................32 Delegating the part ....................................................................................................................33 Delegating index to centralized repository .............................................................................33 2014 EMC Proven Professional Knowledge Sharing 2 Delegating ROBO site backups to local IT .............................................................................34 Delegating ROBO site recovery to local IT ............................................................................34 Delegating ROBO site tape management to local IT ..............................................................35 Delegating ROBO site administration to local IT ....................................................................36 Gaining the claps ......................................................................................................................36 Appendix ...................................................................................................................................37 Disclaimer: The views, processes or methodologies published in this article are those of the author. They do not necessarily reflect EMC Corporation’s views, processes or methodologies. 2014 EMC Proven Professional Knowledge Sharing 3 Introduction Most global clients who demand backup have inventory centers, branch offices, and remote offices spread across the world along with a main data center (Figure 1). The main data center is generally safe and has all that is required for a backup and disaster recovery solution. However, business and user data which resides at remote and branch offices often do not have a proper backup and disaster recovery solution. The situation becomes more difficult for backup administrators when they speak a different language. Most users prefer having their local IT onsite for their data recovery. The situation becomes worse when they themselves don’t know where exactly the share was coming on their local machine. These users mainly put their business-critical data on groupshares and homeshares. These people are mainly from non-IT backgrounds and need their data back at any cost. Figure 1: Remote office connected with main data center and disaster recovery site Delegation Model is a special type of model in which customers route all their data recovery through their own local IT residing at their local sites such as remote office/branch office (ROBO) instead of backup administrators. This reduces the backup administrator’s workload and makes it easier for users to recover their data, though backup administrators are still responsible for disaster recovery. Delegation model is just a general term to delegate some part 2014 EMC Proven Professional Knowledge Sharing 4 of the administrative work to another group. Generally, customers want to customize the model to best fit their needs. Until now, solution architects used EMC Avamar® for their backup accounts in ROBO environments. However, not every account can accommodate the new solution in the existing setup. In my experience, accounts which have EMC NetWorker® as a backup solution can be also be used as part of a delegation model for ROBO environment. This use case of NetWorker has not been explored until recently. In 2013, EMC completely changed EMC NetWorker, making it more adaptable to the backup environment and fulfilled almost all customer expectations. The new features added in this software—such as Restricted Data Zone (RDZ), support for Windows 2012 R2, latest database support, online savesets cloning, block-based backup, and NetWorker Snapshot Management (NSM)—improved space recovery for Advanced File Type Device (AFTD) and many other features completely changed the software. It is now much more compatible and can now be used for ROBO environments. NetWorker is now not only a backup solution but it also interacts with the console user in a very friendly way. The error messages and option for client side logs which it displays are now very easy to understand. Using basic EMC NetWorker functionality can provide a ROBO backup solution using the existing backup solution. It even provides a disaster recovery solution as the software makes a central repository of all of its indexes so it would be much easier to make a disaster recovery copy of the solution. The wide adaptability and acceptability of the solution for operating systems, databases, applications, backup devices, and more makes it responsive to customer needs. This Knowledge Sharing article takes you on a journey to implement Delegation model by using NetWorker as the main backup product. 2014 EMC Proven Professional Knowledge Sharing 5 Goal and Objective The goal of this article is to provide a foundational understanding of delegation model and assist in developing a “blueprint” for the tailored solution which can be extracted by the NetWorker and some backup device. This article introduces a method of designing a service-based branch infrastructure design. The branch environment is typically part of a larger network that supports an organization's main sites and data centers. However, branch sites introduce a number of significant constraints that modify the options that are available to solution designers. This article explains how to look at the specific requirements of the branch office within the larger context of an organization's IT services. Audience While Engineering personnel are the intended audience, this article is also suitable for solution designers who find difficulty offering other products besides NetWorker due to budget issues or environment adaptability. What is Delegation Model? A Delegation model is a model designed for the customer in such a way that only disaster recovery part remains with the service/support vendor. The rest, such as backup, recovery, and reporting remains with the customer. The delegation model offers a way to delegate administration, monitoring, reporting and planning to the customer while keeping disaster recovery with the service company. In short, it is the “Model to increase virtual backup administrators”. Figure 2 depicts a brief idea of what responsibilities are given the local IT and what remain with the backup administrators for the ROBO environment. 2014 EMC Proven Professional Knowledge Sharing 6 Figure