Dell NetWorker Deploy 2023 study materials
Dell NetWorker Deploy 2023 study resources

Dell NetWorker Deploy 2023 study plan

Dell NetWorker Deploy 2023 · Give each week a clear focus.

8 weeks · About 6 hours per week

Week 1

NetWorker Architecture and Components

  • Diagram the NetWorker data path from client to storage node to device, labeling the client resource, save set, policy, workflow, action, and media pool.

  • List the core daemons (nsrd, nsrmmd, nsrjobd, nsrexecd, nsrindexd) and state the function of each in one sentence.

  • Explain how the client file index and media database (mm) differ, and what breaks when either is lost.

  • Trace a single scheduled backup from the policy resource through the workflow and action to the target pool, writing the sequence in order.

Your checkpoint

A one-page architecture diagram with a 10-term glossary and a numbered data-path trace, reviewed for accuracy against product documentation.

Week 2

NetWorker Architecture and Components & Installation and Initial Configuration

  • Compare NetWorker server, storage node, and client roles and identify which packages each role requires.

  • Document the prerequisites for a Linux server install: OS version, hostname resolution, ports, and required packages.

  • Install a NetWorker server and console in a lab VM and record every prompt and choice.

  • Verify the install by confirming the daemons start and the NMC server is reachable.

Your checkpoint

A lab build log with install commands, versions, and a checklist proving server and NMC are running.

Week 3

Installation and Initial Configuration & Client Configuration and Backup Policies

  • Configure a client resource with its save sets, schedules, and directive defaults, then run a manual backup.

  • Create a policy with one workflow and two actions (full and incremental) and assign a media pool to each.

  • Register three lab clients and confirm each appears under its assigned group.

  • Explain how retention and browse periods interact with pool settings and verify the effect on a test save set.

Your checkpoint

A policy export (text or screenshot set) plus a backup log showing one successful full and one incremental for each lab client.

Week 4

Client Configuration and Backup Policies

  • Design a backup schedule for a mixed environment: file systems daily, databases weekly full, with offsite copies.

  • Write and apply a directive that excludes a temp directory and confirm the exclusion in the backup log.

  • Calculate how many volumes a stated retention and change rate will consume, showing the arithmetic.

  • Tune client parallelism and target sessions on one client and measure the effect on job duration.

Your checkpoint

A written backup design document covering policy, schedule, pools, retention, and volume estimate, validated by one test run.

Week 5

Storage Node and Device Configuration

  • Configure a tape library and a disk device, labeling each device and its media pool.

  • Run a labeling and mount operation and confirm the volume is usable for a backup.

  • Set up a storage node on a second host and direct a client backup to it.

  • Explain clone and staged backup targets and configure one clone pool with a test clone job.

Your checkpoint

A device configuration record with device names, pools, and the log of a successful backup to the new storage node and a clone.

Week 6

Recovery and Cloning Operations

  • Restore a single file and a directory from a full backup and verify contents against the source.

  • Perform a save set recover for a deleted client and confirm index consistency.

  • Execute a clone of a full backup and restore from the clone to prove the copy is usable.

  • Document the difference between a browse and a retention recovery and when each is required.

Your checkpoint

A recovery runbook with commands and screenshots for file-level, save set, and clone-based restores, each verified.

Week 7

Monitoring, Reporting, and Troubleshooting & Security, Authentication, and Access Control

  • Read the daemon and job logs to diagnose one deliberately failed backup and record the root cause.

  • Configure an NMC user with a limited role and prove the restriction by attempting a denied action.

  • Generate a backup report and identify the top three failure causes in the lab data.

  • Explain authentication flow between NMC, the NetWorker server, and external LDAP, and test one LDAP group mapping.

Your checkpoint

A troubleshooting and access-control report containing the failed-job analysis, a role test result, and one report output.

Week 8

NetWorker Architecture and Components & Client Configuration and Backup Policies & Recovery and Cloning Operations

  • Review all weak areas flagged in earlier weeks and re-run the corresponding lab tasks.

  • Complete a timed 60-question practice set spanning all seven domains and score it.

  • Re-derive the architecture data path and policy-to-pool mapping without notes.

  • Write a one-page exam-day summary of commands, ports, and key resource relationships.

Your checkpoint

A scored practice result with a corrected error list and a final one-page summary sheet.

Milestones

Week 2: Server and NMC are installed in the lab, all core daemons are running, and the architecture diagram is complete.

Week 4: Three clients are backed up under a documented policy, and the volume estimate matches observed consumption within 20 percent.

Week 6: File-level, save set, and clone-based restores have all succeeded and are documented in the runbook.

Week 8: Practice score is at least 80 percent, and every missed question has a written correction tied to a lab task or documentation reference.