EMC E20-597 (Backup & Recovery Specialist for Storage Administrators) exam dumps vce, practice test questions, study guide & video training course to study and pass quickly and easily. EMC E20-597 Backup & Recovery Specialist for Storage Administrators exam dumps & practice test questions and answers. You need avanset vce exam simulator in order to study the EMC E20-597 certification exam dumps & EMC E20-597 practice test questions in vce format.

Mastering the E20-597 Exam: Foundational Concepts of NetWorker

The E20-597 Exam, officially titled the Specialist - Systems Administrator, NetWorker Exam, was designed to validate a candidate's proficiency in managing a Dell EMC NetWorker environment. This certification demonstrated the essential skills required for the day-to-day administration of this powerful enterprise backup and recovery solution. While the exam code itself may now be part of a legacy certification track, the principles and knowledge it covers remain highly relevant. Understanding these core topics is fundamental for any data protection professional working with NetWorker or similar enterprise backup systems. This series will serve as a comprehensive guide to those topics.

This examination targeted individuals responsible for installing, configuring, and maintaining a NetWorker data protection infrastructure. It assumed a foundational knowledge of networking concepts, storage hardware, and operating systems like Windows and UNIX or Linux. Passing the E20-597 Exam signified that an administrator had the capability to ensure data was being reliably backed up, was recoverable in various scenarios, and that the backup environment itself was performing optimally. The curriculum focused heavily on practical, real-world tasks that a systems administrator would encounter on a daily basis, making its content timeless for learning the software.

The structure of the E20-597 Exam covered a wide range of subjects, from the basic architecture and components of NetWorker to the intricacies of performing different types of backups and recoveries. It also delved into media management, system monitoring, and troubleshooting common issues. By breaking down these knowledge domains, candidates could systematically prepare for the certification. This guide will follow a similar structured approach, starting with the most basic building blocks of NetWorker and progressively moving towards more advanced operational topics, mirroring the logical flow of the E20-597 Exam objectives.

Ultimately, preparing for the topics covered in the E20-597 Exam is about more than just a certification. It is about building a deep understanding of how to protect an organization's most valuable asset: its data. The skills validated by this exam are critical for ensuring business continuity and disaster recovery readiness. Whether you are studying for a current certification or simply aiming to master NetWorker administration, the framework provided by the E20-597 Exam serves as an excellent and thorough educational blueprint for achieving data protection competency.

Understanding Dell EMC NetWorker

Dell EMC NetWorker is a comprehensive, enterprise-level backup and recovery software solution. Its primary purpose is to centralize and automate data protection processes across a wide variety of physical and virtual environments. It is designed to be highly scalable, capable of serving the needs of a small office with a few servers to a large, global enterprise with complex data centers. NetWorker provides a single point of administration for protecting diverse operating systems, applications, and databases. This centralized control is a key theme you would need to grasp for the E20-597 Exam.

The core philosophy of NetWorker is to move data from production systems, known as clients, to secure storage media for safekeeping. This process is managed through a set of policies and schedules that define what data is backed up, when it is backed up, and for how long it is retained. The software is engineered for reliability and performance, incorporating features to minimize the impact on production systems during backup windows and to ensure that data can be restored quickly and accurately when needed. Understanding this fundamental data flow is essential for any administrator preparing for E20-597 Exam related topics.

NetWorker supports a vast ecosystem of technologies. This includes traditional file systems on Windows, Linux, and UNIX servers, as well as complex applications like Microsoft SQL Server, Oracle databases, Microsoft Exchange Server, and SAP. It also integrates deeply with virtual environments such as VMware vSphere and Microsoft Hyper-V, providing specialized tools for protecting virtual machines efficiently. This versatility is a major strength of the platform and a significant area of focus within the E20-597 Exam curriculum, which requires administrators to be familiar with protecting these different data types.

Furthermore, NetWorker is not limited to traditional tape or disk storage. It has evolved to embrace modern data protection technologies, including integration with purpose-built backup appliances like Dell EMC Data Domain. This integration allows for advanced features such as source-side and target-side deduplication, which significantly reduces the amount of storage capacity required for backups and the network bandwidth needed to transfer data. A solid understanding of how NetWorker interacts with these modern storage solutions is a critical competency for any NetWorker administrator.

Core Architectural Components

The architecture of NetWorker is a key area of study for the E20-597 Exam, as it forms the basis for all operations. The entire environment is logically grouped into what is known as a NetWorker data zone. A data zone is a collection of systems that are managed by a single, central NetWorker Server. This server acts as the brain of the operation, coordinating all backup and recovery activities within its zone. Understanding the boundaries and components of a data zone is the first step in comprehending how NetWorker functions as a cohesive system.

Within a data zone, there are three primary functional components that you must understand: the NetWorker Server, the NetWorker Client, and the NetWorker Storage Node. Each component has a distinct and vital role. The NetWorker Server manages the entire data zone, the Clients are the production systems that contain the data to be protected, and the Storage Nodes are responsible for writing the backup data to the physical storage media. The interaction between these three components defines the flow of data during any protection operation.

This modular architecture provides significant flexibility and scalability. For instance, in a very small environment, a single physical machine could potentially host all three roles: Server, Storage Node, and Client. However, in a large enterprise, these roles would be distributed across many different dedicated servers to handle the workload efficiently. An administrator could have dozens of Storage Nodes and thousands of Clients, all managed by one central NetWorker Server. This ability to scale out is a fundamental design principle tested in the E20-597 Exam.

The communication between these components is also a critical aspect of the architecture. The NetWorker Server communicates with Clients to initiate backups and with Storage Nodes to manage the data storage devices. The Clients, in turn, send their backup data directly to the designated Storage Nodes. This division of labor ensures that the NetWorker Server is not a bottleneck for data transfer, allowing the system to handle numerous concurrent backup streams efficiently. A clear grasp of these communication paths is crucial for both configuration and troubleshooting.

The Role of the NetWorker Server

The NetWorker Server is the most critical component in any data zone. As the central administrative hub, it is responsible for coordinating every aspect of the backup and recovery process. It maintains a comprehensive set of databases that track all the necessary information for data protection. This includes configurations for all clients, policies, schedules, and storage devices. A deep understanding of the server's role is a major part of the knowledge required for the E20-597 Exam. Without a functioning NetWorker Server, no backups or restores can be initiated or managed.

One of the server's primary responsibilities is scheduling. Administrators define policies that specify when backups should run, what data should be included, and where it should be stored. The NetWorker Server's scheduling engine then automatically initiates these jobs at the designated times. It orchestrates the entire process, instructing a specific client to begin its backup and telling a specific storage node which device and media to use. This automation is a cornerstone of NetWorker's value, reducing the need for manual intervention and minimizing the risk of human error.

The server also maintains two critical databases: the media database and the client file indexes. The media database contains information about every volume (tape or disk) used for backups, including what data is on it, when it was written, and where it is physically located. The client file indexes, on the other hand, contain a record of all the files that have been backed up for each client, along with their versions and timestamps. These indexes are essential for browsing and selecting specific files for recovery, making them a vital part of the restore process.

Furthermore, the NetWorker Server is responsible for managing the lifecycle of the backup data. This includes tasks like tracking the retention period for each backup save set. Once a backup has exceeded its configured retention time, the server marks it as recyclable. This allows the space it occupies on the backup media to be reclaimed for new backups. This process of data lifecycle management ensures that storage resources are used efficiently over time, a key administrative task covered in the E2t0-597 Exam.

Exploring NetWorker Clients

A NetWorker Client is any machine on the network whose data needs to be protected. This can be a file server, a database server, an application server, or even a user workstation. The client system has a small piece of NetWorker software installed on it, often referred to as the client agent or daemon. This software is responsible for reading the data from the client's local disks and preparing it to be sent over the network for backup. The configuration and management of these clients are central themes of the E20-597 Exam.

The client software operates under the direction of the NetWorker Server. When a scheduled backup is initiated, the server contacts the client and instructs it on what data to back up. This data is defined in what is called a "save set." A save set can be a specific directory, an entire file system, or a more abstract object like a complete database. The client agent processes this request, reading the specified data and packaging it into a stream that can be sent to a Storage Node.

One of the important functions of the client agent is to interact with the operating system and applications to ensure data consistency. For example, when backing up a live database, simply copying the files could result in an inconsistent and unusable backup. The NetWorker client software includes application-specific modules that can communicate with the database application to put it into a proper backup mode. This ensures that the data is captured in a consistent state, from which a successful recovery can be performed. This application-aware backup capability is a critical concept.

Clients are highly configurable. An administrator can define specific directives for a client to control how its data is handled. For instance, directives can be used to exclude certain types of files from a backup, such as temporary files or multimedia files, to save backup capacity. They can also be used to enable special features like software compression or encryption on the client side before the data is even sent across the network. Mastering these client-side configurations is a necessary skill for optimizing any NetWorker environment.

NetWorker Storage Nodes Explained

A NetWorker Storage Node is a system that manages the backup storage devices. Its primary function is to receive the backup data stream from the clients and write that data onto the physical media, such as tape drives, virtual tape libraries (VTLs), or disk-based backup units. The Storage Node acts as a data mover, offloading the intensive I/O operations from the NetWorker Server and allowing for a more distributed and scalable backup architecture. The E20-597 Exam requires a thorough understanding of the Storage Node's role and configuration.

Storage Nodes are directly connected to the storage hardware. This physical connection allows them to control the devices for operations like loading and unloading tapes, formatting new media, and writing and reading data. A single Storage Node can manage multiple storage devices simultaneously, enabling it to handle concurrent backup streams from many different clients. This parallelism is key to achieving high backup throughput and meeting tight backup windows in large environments. The NetWorker Server directs clients to send their data to a specific Storage Node based on policy configurations.

The concept of a Storage Node provides immense flexibility. In a small setup, the NetWorker Server can also act as the sole Storage Node. However, in a larger or geographically distributed environment, dedicated Storage Nodes can be strategically placed. For example, a Storage Node can be located in a remote office to back up local clients to a local tape library. This prevents large amounts of backup data from having to traverse a wide area network (WAN), which can be slow and expensive. This distributed model is a powerful architectural feature.

Configuring a Storage Node involves defining the storage devices it controls. This includes telling NetWorker about the tape libraries, the individual drives within those libraries, and any disk-based storage units that are attached. Once these devices are configured, they can be organized into pools of media. These pools can then be targeted by backup policies, allowing administrators to direct certain types of backups to specific types of media. Proper configuration and management of Storage Nodes and their associated devices are fundamental administrative tasks.

The NetWorker Management Console (NMC)

The NetWorker Management Console, commonly known as the NMC, is the primary graphical user interface (GUI) for managing and monitoring a NetWorker data zone. It is a centralized web-based or Java-based application that provides administrators with a comprehensive view of their entire data protection environment. From the NMC, an administrator can perform nearly all configuration, management, and monitoring tasks. Proficiency with the NMC is absolutely essential for anyone preparing for the E20-597 Exam, as it is the main tool for daily operations.

Through the NMC, administrators can configure all aspects of the NetWorker environment. This includes defining new clients, setting up storage nodes and their devices, creating data protection policies, defining backup schedules, and managing media pools. The interface is organized logically, with different sections dedicated to configuration, monitoring, and reporting. This allows for an intuitive workflow, guiding the administrator through the steps required to set up and maintain a robust backup strategy. The ability to navigate and utilize the NMC effectively is a core competency.

Monitoring is another critical function of the NMC. It provides a real-time view of all backup and recovery jobs that are currently running. Administrators can see the status of each job, its progress, the amount of data transferred, and the estimated completion time. If a job fails, the NMC displays detailed error messages and logs that are crucial for troubleshooting. This centralized monitoring capability allows a small team of administrators to oversee a very large and complex backup infrastructure from a single pane of glass.

The NMC also includes powerful reporting capabilities. It can generate a wide variety of standard reports, such as backup success rates, media usage, and client backup summaries. These reports are invaluable for capacity planning, performance analysis, and demonstrating compliance with data protection service level agreements (SLAs). Administrators can also create custom reports to meet specific business needs. Using the NMC to monitor system health and report on its status is a key responsibility for any NetWorker administrator.

Preparing for NetWorker Installation

Before beginning the installation of Dell EMC NetWorker, thorough preparation is crucial for a smooth and successful deployment. This preparation phase, a topic often covered conceptually in the E20-597 Exam, involves several key steps. First and foremost is understanding the system requirements for each NetWorker component: the Server, the Storage Nodes, and the Clients. This includes verifying supported operating system versions, required memory, CPU resources, and sufficient disk space. The NetWorker Server, in particular, requires adequate disk space for its databases, which will grow over time.

Next, network configuration and name resolution are of paramount importance. NetWorker relies heavily on a stable and correctly configured network. All components within the data zone—Server, Storage Nodes, and Clients—must be able to resolve each other's hostnames, both forward (name to IP address) and reverse (IP address to name). Using a Domain Name System (DNS) is the recommended best practice. Any inconsistencies in name resolution are a common source of post-installation problems, so verifying this beforehand can save significant troubleshooting time later.

A critical part of the preparation is planning the architecture itself. This involves deciding which machine will host the NetWorker Server role and which machines will be dedicated Storage Nodes. The placement of Storage Nodes should be strategic, considering network topology to minimize backup traffic over slow WAN links. You must also plan for the storage devices that will be used, ensuring they are physically connected to the designated Storage Nodes and that the necessary drivers and firmware are up to date. This planning phase ensures the deployment aligns with the organization's data protection goals.

Finally, you must obtain the necessary NetWorker software and licensing information. The software is typically downloaded from the vendor's official support portal. Licensing in NetWorker can be complex, often based on the capacity of data being protected or the number of clients and advanced features being used. Having the license enablers ready before installation will allow you to activate the full functionality of the product immediately after the core components are installed. Careful planning is the foundation upon which a stable NetWorker environment is built.

Step-by-Step NetWorker Server Installation

The installation of the NetWorker Server is the first and most critical step in building a new data zone. The process, while guided by an installer wizard, requires careful attention to detail. The E20-597 Exam would expect an administrator to be intimately familiar with this procedure. The process begins by launching the installation package on the designated server hardware, which should already meet all the prerequisites identified during the planning phase. The installer will typically prompt for an installation path; it is best practice to install NetWorker on a dedicated volume with sufficient space for future growth.

During the installation, you will be prompted to make several key decisions. One of the first is to select which components to install. On the main server, you would select the NetWorker Server and, typically, the NetWorker Client components. It is also common practice to install the Storage Node component on the server itself, especially in smaller environments, allowing the server to manage local backup devices. This creates a combined Server and Storage Node, which is a very common configuration.

A pivotal moment in the installation process is the configuration of the NetWorker Management Console (NMC) server. The NMC is the graphical interface for managing NetWorker. The installer will ask if you want to install the NMC server on this machine. This requires the installation of a web server and a database to store the NMC's configuration and reporting data. You will need to define an administrator password for the NMC, which will be the primary credential used to log in and manage the entire data zone.

After the software files are copied, the installer will perform initial configuration tasks, such as starting the necessary services or daemons. Once the installation is complete, it is essential to perform a post-installation check. This involves verifying that all NetWorker services are running correctly and attempting to log into the NetWorker Management Console for the first time using the credentials you created. A successful login is the first confirmation that your NetWorker Server has been installed correctly and is ready for further configuration.

Configuring NetWorker Clients

Once the NetWorker Server is operational, the next logical step is to configure the clients that need to be protected. This process involves two main parts: installing the NetWorker client software on the target machine and then defining that machine as a client resource on the NetWorker Server. The E20-597 Exam curriculum places significant emphasis on client configuration, as it is a fundamental, recurring task for any administrator. The client software installation is straightforward, involving running the installer on the client machine and selecting only the "Client" component.

After the software is installed on the client, it must be configured on the NetWorker Server via the NetWorker Management Console (NMC). This is done by creating a new Client resource. The creation wizard will ask for several key pieces of information. The most important of these is the client's name, which must match the hostname that the server uses to resolve the client's IP address. Any mismatch here will result in communication failures.

Within the client resource configuration, you define the "save set" for the client. The save set specifies which data on the client will be backed up. This can be as broad as "All," which includes all local file systems, or it can be a specific list of directories or drives. For example, you might configure a file server client to back up only the D:\Data and E:\Shares volumes, ignoring the operating system drive. Defining the save set correctly is crucial for ensuring that critical data is protected while avoiding the unnecessary backup of transient or non-essential files.

Another important aspect of client configuration is specifying the client's "server." In most cases, this will be the primary NetWorker Server. However, the client software includes a security feature where it maintains a list of servers that are authorized to back it up. During the client creation on the server, the server will automatically attempt to update this list on the client. This security measure prevents a rogue server from connecting to a client and pulling data from it. Proper client configuration is the bedrock of a reliable backup system.

Setting Up Storage Nodes and Devices

Configuring Storage Nodes and the devices they control is a hands-on process that is critical for the flow of backup data. After installing the Storage Node software on a designated machine, you must configure it within the NetWorker Management Console (NMC). This establishes the communication link between the NetWorker Server and the Storage Node, allowing the server to delegate data writing tasks. The E20-597 Exam would require a candidate to demonstrate knowledge of configuring various types of storage devices, from simple disk units to complex tape libraries.

The first step after installing the software is to create the Storage Node resource on the NetWorker Server. This tells the server about the existence of the Storage Node and its hostname. Once this is done, you can begin to configure the devices that are physically attached to that Storage Node. NetWorker typically has an auto-detect feature that can scan the Storage Node's hardware and identify connected devices like tape libraries and drives. This simplifies the initial setup process significantly.

For tape libraries, the configuration involves defining the library itself (the robotic arm) and the individual tape drives within it. Each drive will be represented as a separate device resource in NetWorker. You will need to ensure that NetWorker can control the library's robotics to mount and unmount tapes as needed for backup and recovery operations. This often requires specific device drivers and configuration at the operating system level before NetWorker can manage the hardware effectively.

For disk-based backups, the process is generally simpler. You would create a device of the type "adv_file." This type of device corresponds to a directory on the Storage Node's local file system. NetWorker will then write the backup data into this directory, creating files that represent the backup volumes. Configuring disk-based devices is a common practice for faster backup and recovery operations. Properly setting up and labeling all devices is essential before they can be assigned to media pools and used in backup workflows.

Managing Media Pools and Labels

Once storage devices are configured, the next step is to organize the backup media using pools and labels. This management is a core administrative function tested in the E20-597 Exam. A media pool is a logical collection of backup volumes, whether they are physical tapes or disk-based volumes. Pools are used to segregate backup data for organizational and management purposes. For example, you might create a "Daily-Backups" pool for daily incremental backups and a separate "Monthly-Archives" pool for full monthly backups that have a longer retention period.

When a backup job runs, it is configured to write to a specific pool. NetWorker will then look for an available, labeled volume in that pool to write the data to. If it's a tape library, NetWorker will instruct the robotics to load a suitable tape from the designated pool into a free drive. This policy-based media selection ensures that different types of data are written to the correct media set, which simplifies tracking and lifecycle management. For instance, you would not want short-term daily backups to be written to tapes intended for long-term archival.

Before a volume can be used by NetWorker, it must be labeled. Labeling is the process of writing a NetWorker-specific internal header to the media. This header gives the volume a unique name and assigns it to a specific pool. You can label tapes one by one or in batches. This process initializes the media for use within the NetWorker environment. An unlabeled volume cannot be used for a backup operation. The NMC provides a straightforward interface for managing the labeling and recycling of media.

The concept of recycling is tied directly to pools and data retention policies. When all the backups on a volume have exceeded their retention period, NetWorker marks the volume as "recyclable." This means it is eligible to be relabeled and reused for new backups. This automated process is crucial for the efficient use of storage media. The administrator's role is to monitor the status of media within pools, ensuring there are always enough appendable or recyclable volumes available to meet the demands of the upcoming backup schedule.

The NetWorker Management Console (NMC) Configuration

Beyond its role as a monitoring tool, the NetWorker Management Console (NMC) itself requires some initial and ongoing configuration. A deep dive into the E20-597 Exam topics would include understanding how to set up and customize the NMC for a production environment. The NMC server maintains its own database for storing historical reporting data and its user configurations. Managing the size and location of this database is an important administrative task to prevent it from filling up its disk volume.

One of the primary configuration tasks within the NMC is setting up notifications. NetWorker can be configured to send email alerts for various events. This is extremely important for proactive administration. You can configure notifications for events like backup failures, successful completions, or specific error conditions. These alerts ensure that administrators are immediately aware of any issues within the backup environment without having to constantly watch the console. Setting up the SMTP server details and defining the notification rules is a key setup step.

Customizing the views and reports within the NMC is another important configuration aspect. While the default views are useful, administrators can create custom layouts that show the specific information most relevant to their operational needs. Similarly, the reporting engine can be used to schedule the automatic generation and emailing of key reports. For example, a daily report summarizing the status of all backups from the previous night can be automatically sent to the IT management team each morning.

Furthermore, the NMC server's own data protection is a critical consideration. The NMC contains valuable historical data and the configuration for all reports and user accounts. Therefore, the NMC server itself should be configured as a NetWorker client, and its internal database must be included in a backup schedule. This ensures that in the event of a failure of the NMC host machine, you can recover the management and reporting interface along with all its historical data, a key principle of comprehensive data protection strategy.

User and Role-Based Access Control

In any enterprise software, security and access control are paramount. NetWorker provides a robust framework for managing user authentication and authorization, a topic that an administrator preparing for the E20-597 Exam must master. Instead of having a single administrative password shared among multiple users, NetWorker allows you to create individual user accounts. This allows for accountability, as actions within the system can be audited and traced back to a specific user.

NetWorker employs a Role-Based Access Control (RBAC) model. This means that instead of assigning permissions directly to users, you assign users to roles, and permissions are granted to the roles. NetWorker comes with several predefined roles, such as "Application Admin," "Backup Admin," and "Security Admin." Each role has a specific set of privileges that are aligned with a particular job function. For example, a Backup Admin might be able to start and stop backups, but they might not have the permission to create new user accounts.

This RBAC model greatly simplifies user management. When a new employee joins the team, you simply need to create a user account for them and assign them to the appropriate role based on their responsibilities. You can also create custom roles with a granular selection of privileges if the predefined roles do not fit your organization's security policies perfectly. This allows for the implementation of the principle of least privilege, where users are only given the minimum level of access required to perform their jobs.

User authentication can be managed externally. NetWorker can be integrated with external directory services like LDAP or Active Directory. This allows users to log in to the NetWorker Management Console using their standard corporate credentials, which simplifies password management and enhances security. Configuring this external authentication is a common administrative task in larger organizations. A solid grasp of creating users, managing roles, and integrating with external authentication sources is essential for securing the NetWorker environment.

Designing Effective Backup Strategies

A core competency for any data protection administrator, and a major focus of the E20-597 Exam, is the ability to design an effective backup strategy. This goes beyond simply configuring jobs; it involves understanding the business requirements for data protection. The first step is to perform data classification. Not all data is of equal importance. You must work with business stakeholders to identify critical systems and data that require the most aggressive protection, versus less critical data that can be backed up less frequently.

This classification directly informs the creation of Service Level Agreements (SLAs) for data protection. An SLA defines key metrics such as the Recovery Point Objective (RPO) and the Recovery Time Objective (RTO). RPO dictates the maximum acceptable amount of data loss, measured in time. For instance, a critical database might have an RPO of 15 minutes, requiring very frequent backups. RTO defines how quickly a system must be restored after a disaster. A high-priority application might have an RTO of one hour, influencing the choice of backup storage technology for faster restores.

Based on the RPO and RTO requirements, you can then design the backup schedules and methods. Critical systems may require daily full backups, while less critical file servers might be adequately protected with a weekly full backup followed by daily incremental backups. The strategy must balance the need for protection against the impact on production systems, network bandwidth, and backup storage capacity. An effective strategy is always a compromise between these factors.

The choice of backup target is another crucial element of the strategy. High-performance disk storage, perhaps on a deduplicating appliance, is ideal for staging recent backups to meet aggressive RTOs. For long-term retention and archival, lower-cost options like physical tape or cloud object storage might be more appropriate. A well-designed strategy often employs a tiered approach, automatically moving older backups from expensive, high-performance storage to more cost-effective, long-term media. This entire design process is fundamental to the role of a NetWorker administrator.

Configuring Backup Groups and Workflows

In NetWorker, the primary mechanism for executing backups is through the configuration of Groups and Workflows. Understanding how to effectively use these constructs is a practical skill essential for the E20-597 Exam. A Group is a collection of clients that are logically managed together. When a group is started, NetWorker will attempt to back up all the clients defined within that group. Grouping clients can be done based on various criteria, such as geographical location, operating system type, or the application they are running.

The properties of a group control its overall behavior. For example, you can set a "start time" for the group, which defines when the backups for the clients in that group should automatically begin. You can also define the parallelism for the group, which limits how many clients within that group can be backed up simultaneously. This is an important setting for controlling the load on the NetWorker Server and the backup network. Proper group configuration helps to ensure that backups are completed within the designated backup window.

More modern versions of NetWorker have introduced the concept of Protection Policies and Workflows, which offer a more granular and powerful way to manage data protection. A Workflow is a sequence of actions that are performed. The most basic workflow would contain a single backup action. However, workflows can be more complex, for instance, defining a backup action that is immediately followed by a clone action. This would automatically create a second copy of the backup on different media for redundancy.

Within a workflow, you define which clients are part of the protection policy, what data to back up (the save set), where the data should be sent (which storage node and pool), and when the workflow should run (the schedule). This policy-based approach is highly efficient, allowing an administrator to manage the protection of hundreds of clients by simply associating them with the correct policy. Mastering the creation and management of these policies and workflows is central to day-to-day NetWorker administration.

Understanding Backup Levels

NetWorker supports several different backup levels, and a clear understanding of each is fundamental knowledge for the E20-597 Exam. The backup level determines which files are included in a backup operation. The most common levels are Full, Incremental, and Differential, though NetWorker also supports other levels for specific use cases. The choice of which levels to use, and in what combination, has a significant impact on backup time, storage consumption, and the complexity of restores.

A Full backup, as the name implies, backs up all the specified data, regardless of whether it has changed since the last backup. A full backup provides a complete, self-contained baseline of the data at a specific point in time. While they are the most straightforward to restore from, they also consume the most time and storage space. Typically, a full backup is performed periodically, for example, once a week, to establish a new baseline.

An Incremental backup only backs up the data that has changed since the last backup of any level (full or incremental). This is determined by checking the file's modification timestamp. Incremental backups are very fast and consume minimal storage space, making them ideal for daily backups. However, to perform a full restore, you would need the last full backup plus every single incremental backup taken since that full. This can make the restore process more complex and time-consuming.

A Differential backup backs up all the data that has changed since the last full backup. Each successive differential backup will grow larger as more files change. The advantage of a differential backup is that a full restore only requires two backup sets: the last full backup and the most recent differential backup. This simplifies the restore process compared to using incrementals. A common strategy is to perform a weekly full backup, followed by daily differential backups, providing a good balance between backup performance and restore simplicity.

Advanced Client Configuration for Backups

Beyond defining the save set, NetWorker offers advanced configuration options at the client level to fine-tune backup operations. These advanced features, often covered in the E20-597 Exam, allow administrators to address specific requirements and optimize performance. One of the most powerful tools for this is the use of Directives. Directives are special instruction files that are processed by the client agent during a backup. They allow for very granular control over how the backup is performed.

For example, a directive can be used to exclude specific files or directories from a backup. This is useful for preventing the backup of temporary files, log files that are not needed for recovery, or other non-essential data. This can significantly reduce the size of the backup and shorten the backup window. Directives can also be used to apply specific settings to certain types of files, such as enabling software compression only for highly compressible file types.

Another advanced feature is client-side parallelism. By default, the client agent may back up file systems or save sets in a serial fashion. You can configure parallelism on the client to allow it to send multiple backup streams to the storage node simultaneously. For a client with multiple fast disks and a high-speed network connection, this can dramatically increase the overall backup throughput. This is particularly useful for large file servers with several independent volumes.

Furthermore, you can configure clients to use specific network interfaces for backup traffic. In a server with multiple network cards, you might have one interface dedicated to production user traffic and another dedicated to backup traffic. By specifying the backup network interface in the client configuration, you can isolate the backup data flow, ensuring that it does not impact the performance of the server's primary applications. Mastering these advanced settings allows an administrator to move from basic configuration to true environment optimization.

Performing Filesystem Backups

The most common type of backup operation in any environment is the filesystem backup. This involves protecting the files and directories that reside on the operating system's volumes. The E20-597 Exam would expect a comprehensive understanding of this process. In NetWorker, this is achieved by defining the save set on the client resource to include the specific drive letters (on Windows) or mount points (on UNIX/Linux) that need to be protected. A save set of "All" is a common starting point, which tells NetWorker to back up all local filesystems.

During a filesystem backup, the NetWorker client agent traverses the specified directory tree. For each file it encounters, it checks its modification time against the timestamp of the last backup to determine if it needs to be included in the current backup, depending on the backup level (e.g., incremental). The agent is responsible for reading the file data and sending it, along with its metadata (permissions, ownership, timestamps), to the designated storage node.

NetWorker is designed to handle the complexities of different file systems. It correctly backs up and restores special file types, such as symbolic links on Linux or NTFS permissions and alternate data streams on Windows. This ensures that when data is restored, it is returned to its original state with all its attributes intact. This fidelity is a critical feature of an enterprise backup solution. The client file index on the NetWorker Server is updated with an entry for every file that is backed up.

Administrators can monitor the progress of a filesystem backup through the NetWorker Management Console. The console will show which file system is currently being processed, the speed of the data transfer, and the total amount of data backed up. If the backup encounters an issue, such as being unable to read a locked file, it will be logged in the backup details. Understanding how to read these logs is a key troubleshooting skill for resolving filesystem backup issues.

Backing Up Applications and Databases (Modules)

Protecting applications and databases requires a more sophisticated approach than simply backing up their files from the filesystem. Live applications, especially databases, are constantly writing to their files. If these files are backed up while in this active state, the backup will likely be inconsistent and unusable for a proper recovery. The E20-597 Exam places a strong emphasis on understanding how to correctly protect these critical workloads. NetWorker addresses this challenge through the use of specialized application modules.

A NetWorker Module is an add-on software component that integrates NetWorker with a specific application, such as Microsoft SQL Server, Oracle, or Microsoft Exchange. This module is installed on the client server that is running the application. It acts as an intermediary, using the application's own native backup APIs to ensure a consistent and reliable data capture. For example, the NetWorker Module for Microsoft SQL will use the SQL Server VDI (Virtual Device Interface) API to stream a consistent backup of a database directly to the NetWorker storage node.

When you configure a backup for an application client, you do not specify filesystem paths in the save set. Instead, you use a special save set syntax that is specific to the module. For an SQL server, the save set might be MSSQL:, which tells the NetWorker client to invoke the SQL module to discover and back up all the databases on that instance. You can also specify individual databases, such as MSSQL:HR_DATABASE.

The configuration and execution of these backups are still managed centrally from the NetWorker Server. The administrator can schedule the application backups using the same policies and workflows as filesystem backups. The module handles all the complex interaction with the application behind the scenes. This provides a unified data protection experience, allowing administrators to manage the protection of files, virtual machines, and complex applications all from a single console, a key benefit of the NetWorker platform.

Cloning and Staging for Data Lifecycle Management

Backing up data is only the first step in a comprehensive data lifecycle management strategy. Creating secondary copies of backups and moving them between different storage tiers are common requirements. NetWorker facilitates this through processes known as cloning and staging, which are important concepts for the E20-597 Exam. Cloning is the process of making a copy of an existing backup save set. This creates a bit-for-bit identical copy of the backup on different media.

Cloning is most often used to create a second copy for disaster recovery purposes. For example, a backup might initially be written to a local disk-based backup appliance for fast restores. A cloning policy can then be configured to automatically create a copy of that backup onto tape. These tapes can then be physically transported to a secure offsite storage facility. This ensures that even if the entire primary data center is lost, there is still a copy of the data available for recovery.

Staging, on the other hand, is a process of moving a backup from one storage pool to another, after which the original copy is deleted. Staging is typically used for data tiering. An administrator might configure a policy to back up all data to a high-performance, but expensive, disk pool first. After 30 days, a staging policy could automatically move these backups to a lower-cost, high-capacity disk pool or to a tape pool for long-term retention.

Both cloning and staging are managed through policies on the NetWorker Server. They can be scheduled to run automatically after a backup completes or during off-peak hours. These features are essential for implementing tiered storage strategies, which help to balance performance, cost, and retention requirements. By automating the movement and copying of data, NetWorker reduces the administrative burden and ensures that data protection policies are consistently enforced throughout the entire lifecycle of the data.

The Fundamentals of Data Recovery

The ultimate purpose of any backup system is the ability to recover data when it is needed. A backup is worthless if it cannot be restored. Therefore, recovery operations are arguably the most critical aspect of a NetWorker administrator's job and a heavily weighted topic in the E20-597 Exam. Understanding the fundamental principles of recovery is the first step. Recovery always begins with a request, which could be for a single lost file, a corrupted database, or an entire failed server.

The recovery process in NetWorker relies on the metadata that the server meticulously maintains. The two key pieces of information are the client file index and the media database. When a user needs to restore a file, the administrator first searches the client file index for that client. This index provides a browsable, point-in-time view of all the backed-up files, allowing the user to select the specific version of the file they wish to restore.

Once the desired files or save sets are selected for recovery, NetWorker consults its media database. The media database knows exactly which volume (tape or disk) contains the required backup data. NetWorker then orchestrates the recovery process. It will instruct the storage node to make the required media available. If it is a tape, it will command the tape library to load the correct tape into a drive. The data is then read from the media and sent back to the client.

The NetWorker client agent on the target machine receives the restored data and writes it back to the file system. The entire process is managed and monitored from the NetWorker Management Console (NMC). The administrator can watch the progress of the recovery and will be notified upon its successful completion or if any errors are encountered. A solid theoretical and practical understanding of this end-to-end data flow is essential for any data protection professional.

Performing Filesystem Restores

Restoring files and directories is the most common type of recovery operation that a NetWorker administrator will perform. The E20-597 Exam would expect candidates to be proficient in this task using the tools provided by NetWorker. The primary interface for this is the NetWorker Management Console (NMC), which offers a user-friendly graphical wizard for recovery. The process begins by selecting the client from which the data was originally backed up.

The next step is to browse the client's file index to find the data you want to restore. The NMC allows you to browse by a specific point in time. You can select a date and time, and the interface will show you a view of the client's file system as it existed at the time of the backup. This is a powerful feature that allows you to recover a file from before it was accidentally deleted or corrupted. You can navigate the directory tree and select individual files or entire folders to be marked for recovery.

Once you have selected the items to be restored, you must specify the destination. By default, NetWorker will restore the data to its original location on the original client. However, you also have the option to restore the data to a different directory on the same client or even to a completely different client altogether. This flexibility is very useful for various scenarios, such as recovering files to a temporary location for inspection before overwriting the production data.

After confirming all the options, you start the recovery process. The NMC will display the status of the restore job in its monitoring window. You can see which save sets are being read, the progress of the data transfer, and any messages or errors that occur. A successful filesystem restore operation concludes with the data being available at the specified destination, with its original permissions and timestamps intact, assuming the destination file system supports them.

Go to testing centre with ease on our mind when you use EMC E20-597 vce exam dumps, practice test questions and answers. EMC E20-597 Backup & Recovery Specialist for Storage Administrators certification practice test questions and answers, study guide, exam dumps and video training course in vce format to help you study with ease. Prepare with confidence and study using EMC E20-597 exam dumps & practice test questions and answers vce from ExamCollection.