Administration of Veritas System Recovery 2013: Exam Guide and Study Roadmap
Administration of Veritas System Recovery 2013 is intended to validate practical administration of a System Recovery environment: preparing recovery resources, managing backup images, restoring systems, and diagnosing recovery problems. The available official material does not provide a current exam blueprint, domain weights, question count, passing score, duration, or prerequisite list for this specific exam. This guide therefore helps candidates make the important decision between exam-focused review and hands-on lab preparation, while separating documented certification processes from sensible preparation recommendations.
What the exam is likely intended to validate
The useful target is operational competence, not product vocabulary alone. Broadcom describes Symantec certifications generally as securely proctored, computer-based exams based on real-world job tasks and assessing the ability to deploy, configure, utilize, troubleshoot, and optimize Symantec solutions. Apply that framework to System Recovery administration, but do not treat it as a substitute for a product-specific blueprint. Source: https://docs.broadcom.com/doc/secure-one-certification-overview-en
For this product, administration means understanding the complete recovery lifecycle. You should be able to reason from a protected Windows system and its recovery point to a usable restored system, while accounting for recovery media, target hardware, storage, boot behavior, and post-restore validation.
The official community material identifies Symantec System Recovery 2013 R2 as capable of producing backup images used for recovery operations. A separate discussion describes creating a custom recovery disk and restoring a host full backup to an ESXi guest. These are useful indicators of the practical problem space, but they are community discussions rather than an official exam blueprint. Source: https://community.broadcom.com/vmware-cloud-foundation/discussion/from-symantec-system-recovery-backup-image-recoveryed-to-esxi-server-guest-machine-can-not-boot
Who should prepare for this certification
This exam is most relevant to administrators responsible for Windows system protection and recovery, engineers who support business continuity operations, and technicians who must restore a failed machine or move a system image into a virtual test environment. Candidates who only know backup concepts but have never worked through recovery media and image selection should prioritize lab work before attempting an exam appointment.
A support engineer may approach the subject through fault isolation: identify whether the failure involves the image, recovery environment, storage access, boot configuration, or the restored operating system. A systems administrator may focus more on repeatable backup and restore procedures. Both perspectives matter because a successful administrator must configure protection and recover from it.
The available sources do not state prerequisites, required work experience, training requirements, or a specific candidate profile for Administration of Veritas System Recovery 2013. Do not infer that a particular job title, operating-system version, or vendor course is mandatory. Confirm any current eligibility rule in the registration or certification information available through the official Broadcom channel before scheduling.
What the available evidence does not confirm
No supplied official source publishes the exam’s measured domains, percentages, question count, passing score, exam duration, languages, retirement status, or current version alignment. Those omissions are important: a responsible study plan can identify product skills, but it cannot honestly assign blueprint weights or promise that a particular topic will appear.
Do not use an old practice page, an unofficial outline, or a collection of remembered questions as proof of the current exam structure. Product names and ownership have changed over time, and the supplied material includes legacy System Recovery, Backup Exec System Recovery, VMware, and newer NetBackup references. Similar terminology does not establish that all of those products are tested in this exam.
The correct next action is to check the current official certification listing and registration path for the exact exam name. If the listing provides an exam guide or objectives document, use that document to replace the provisional topic map below. Until then, treat the study areas as practical preparation recommendations rather than official domain statements.
Which System Recovery concepts deserve first attention
Start with the objects that connect protection to recovery: the protected machine, backup job or recovery point, image files, recovery disk, destination storage, and restored operating system. A candidate who can explain how those objects relate will make better decisions than someone who memorizes isolated wizard labels.
Review how a full system image differs from a file-level copy in operational purpose. The supplied community material refers to a host full backup and available image files with the .v2i extension in an automation scenario. That evidence supports studying image-based recovery and image-file handling; it does not establish every file type, feature, or limitation for the exam. Source: https://community.broadcom.com/symantecenterprise/viewdocument/automating-system-recovery-with-bac?CommunityKey=bf23126f-6eab-4bbe-965d-e26838c079e0
Build a one-page glossary in your own words. Include recovery point, custom recovery disk, bare-metal recovery, dissimilar hardware, restore destination, boot repair, and validation. For each term, write what decision it affects. For example, recovery media affects whether the machine can start the recovery environment; the image affects what state can be restored; the destination affects whether the recovered system can boot.
How to study backup configuration without memorizing screens
Study configuration as a chain of decisions: what is protected, when it is captured, where the image is stored, how it is retained, and how the result will be verified. This approach prepares you for scenario questions even when an interface label differs between installations or documentation versions.
For every protection scenario, write down the expected recovery objective before choosing settings. A server needing a complete system return requires a different validation conversation from a user who needs one file. Ask what must be available after failure, how recent the recovered state must be, and whether the recovery location differs from the original machine.
Use documentation and a lab to confirm details such as supported destinations, image dependencies, scheduling behavior, retention controls, and verification options. The supplied sources do not provide a complete System Recovery 2013 administration manual or an exam objective list, so do not invent configuration defaults or assume that a feature exists merely because another backup product provides it.
A useful exercise is to draw the dependency path for a restore. Start with the selected recovery point, list any required image components or storage locations, then identify the recovery environment and target disk. Add a validation checkpoint after each stage. This makes missing media, inaccessible storage, incompatible hardware, and boot problems visible before you attempt the procedure.
How to prepare for recovery-media tasks
Recovery media deserves hands-on practice because a backup image is not useful if the administrator cannot start the recovery tools or reach the image location. Practice creating or locating the appropriate recovery disk, booting a test machine, identifying available disks, and confirming that the recovery point is visible before committing to a restore.
Broadcom’s community material specifically states that Symantec System Recovery 2013 could create a custom recovery disk for restoring a backup image. In the reported ESXi scenario, the administrator created a blank guest machine and used a custom existing recovery disk to boot it before restoring the image. Use this as a workflow example, not as proof of a universal virtual-machine procedure. Source: https://community.broadcom.com/vmware-cloud-foundation/discussion/from-symantec-system-recovery-backup-image-recoveryed-to-esxi-server-guest-machine-can-not-boot
In a lab, test the recovery environment against the storage paths you expect to use. Record whether the environment can see the backup location, whether network access requires additional configuration, and whether the target disk is identified correctly. Keep a written recovery inventory: image location, backup date or label, source machine, target machine, and validation result.
A common mistake is to begin restoring before confirming that the image is complete and accessible. Another is to treat a bootable disk as proof that the restored operating system will boot. Separate these checks: first validate recovery-environment access, then validate image selection, then validate the restored system.
How to reason about bare-metal and dissimilar-hardware recovery
A strong candidate distinguishes restoring data from restoring a bootable operating system. Bare-metal recovery may require the recovery environment to identify storage correctly, place system data on the intended disk, and leave the restored operating system able to start on its destination hardware. Dissimilar hardware adds driver, boot-mode, and platform-compatibility questions.
The automation article describes complete Windows system restoration and full bare-metal recovery as practical uses of Backup Exec System Recovery, and it lists a recovery disk and valid recovery point among the prerequisites for its automation example. That article concerns an earlier product context, so use it to understand the recovery workflow rather than to assume that every automation component belongs to System Recovery 2013. Source: https://community.broadcom.com/symantecenterprise/viewdocument/automating-system-recovery-with-bac?CommunityKey=bf23126f-6eab-4bbe-965d-e26838c079e0
When studying a hardware-change scenario, work through four questions. Can the recovery environment access the target storage? Does the image contain the required system volumes? Does the destination use a compatible boot configuration? Will the restored operating system have the drivers and configuration needed to start? If the answer to any question is unknown, mark it as a lab task rather than guessing.
Do not describe a successful image write as a successful recovery. The final test should include booting the restored system, checking essential services and storage, confirming that the expected data is present, and recording any remediation. In production, follow change-control and application-owner validation procedures; those governance requirements are practical recommendations, not supplied exam requirements.
What virtual recovery scenarios can teach you
Virtual recovery is valuable for practicing destination planning and boot troubleshooting, but the supplied evidence does not establish a current System Recovery 2013 virtual-exam domain. Use virtualization as a controlled lab target for image restoration, hardware abstraction, and post-restore diagnosis rather than assuming that a specific hypervisor version or conversion path is required.
One Broadcom community discussion reports that VMware Converter Standalone did not allow creating virtual machines from Symantec backup files in the cited System Recovery 2013 R2 situation. The response points to a one-time virtual conversion procedure. This is historical community evidence, not a guarantee that the referenced procedure remains available or that it applies to every image. Source: https://community.broadcom.com/vmware-cloud-foundation/discussion/p2v-from-symantec-system-recovery-2013-r2-backup
A second discussion records a restore to an ESXi 6.7 guest from a System Recovery 2013 backup image and reports a Windows Installer error at first boot. The value for preparation is diagnostic: restoration can complete while the guest still fails to start. Practice separating the image-restore stage from operating-system startup and application validation. Source: https://community.broadcom.com/vmware-cloud-foundation/discussion/from-symantec-system-recovery-backup-image-recoveryed-to-esxi-server-guest-machine-can-not-boot
Do not transfer NetBackup for VMware facts into a System Recovery 2013 study plan. The supplied NetBackup article concerns Veritas NetBackup 10 support for VMware Cloud on AWS, including its own architectures and transport limitations. It may be useful only if your job separately involves that product; it is not evidence for this exam’s objectives. Source: https://knowledge.broadcom.com/external/article/329484/vmc-on-aws-veritas-netbackup-for-vmware.html
How to troubleshoot a failed restore systematically
Troubleshoot in layers instead of repeating the restore. First establish whether the recovery media starts. Next verify that the image is readable and the intended recovery point is selected. Then inspect disk mapping and restore completion. Finally diagnose operating-system boot, drivers, services, and applications. Record evidence at each layer.
Use a simple incident worksheet with columns for symptom, stage, evidence, likely cause, corrective action, and retest result. This keeps “the image restored” separate from “the guest booted” and “the workload functioned.” It also gives you a repeatable answer structure for scenario-based questions.
For a machine that fails immediately after recovery, check the target disk and boot configuration before assuming image corruption. For a recovery environment that cannot find the image, check storage connectivity, path visibility, permissions, and whether all required image files are present. For an operating system that starts but behaves incorrectly, check hardware changes, drivers, services, and application dependencies.
The community example involving the message “windows installer could not configure windows to run on this computer hardware” should be treated as a troubleshooting prompt, not a memorization target. The source does not provide a confirmed root cause or an official resolution. A careful candidate would reproduce the scenario in an isolated lab, collect logs, and consult product-specific support documentation rather than claiming one universal fix.
How to use automation evidence correctly
Automation is worth studying as a process-design problem: prepare a known recovery environment, supply a valid recovery point, launch the recovery workflow consistently, and verify the result. It is not worth memorizing an old script line by line unless the current official objectives explicitly require that technology.
The supplied automation document lists Deployment Server 6.9 with a WinPE automation environment, a BackupExec System Recovery disk, a valid recovery point with available .v2i files, and AutoIt as prerequisites for its example. It also describes sequential deployment tasks and unattended restoration. These details belong to a historical integration article and should not be presented as current System Recovery 2013 exam requirements. Source: https://community.broadcom.com/symantecenterprise/viewdocument/automating-system-recovery-with-bac?CommunityKey=bf23126f-6eab-4bbe-965d-e26838c079e0
If your role includes automation, build a small proof of concept that performs validation before destructive actions. The job should identify the target, confirm the recovery point, capture a clear log, stop on an unexpected condition, and report whether post-restore validation passed. Keep recovery images and scripts in a controlled location, and test against disposable systems.
The major pitfall is confusing unattended execution with unattended success. Automation can repeat a wrong target, an unavailable image, or an unverified restore. Design the workflow so that human approval is required where a mistake could overwrite a production disk.
Which study materials should be trusted
Use official product documentation and the current certification listing for requirements, then use a lab for behavior. The supplied sources include Broadcom documentation, knowledge articles, and community discussions, but they do not provide a complete Administration of Veritas System Recovery 2013 exam blueprint. Label each note as official requirement, documented product behavior, historical example, or personal lab observation.
The Symantec certification overview is the strongest supplied source for the general assessment model: securely proctored, computer-based exams based on real-world job tasks and skills involving deployment, configuration, utilization, troubleshooting, and optimization. The registration guide is the appropriate supplied source for the Pearson VUE process. Product-community threads are useful for scenarios and pitfalls, but they should not define exam coverage.
Avoid exam dumps and leaked-question claims. Memorizing recalled questions does not establish product competence, may reflect an obsolete exam, and cannot guarantee a passing result. Replace each questionable item with a task: configure a protection plan, locate a valid recovery point, boot recovery media, restore to a test target, and explain how you verified the outcome.
Keep version boundaries visible in your notes. System Recovery 2013, System Recovery 2013 R2, Backup Exec System Recovery, and NetBackup are not interchangeable labels. If a source names another product or release, record it as related context and verify whether the current exam documentation includes it before studying it as examinable content.
A practical four-stage preparation roadmap
A staged plan works better than reading every feature in order. First establish terminology and recovery flow, then perform controlled configuration and restore tasks, then troubleshoot deliberately introduced failures, and finally review official registration information and any current exam objectives. The sequence should move from recognition to independent decision-making.
Stage one: build the product map. Identify the protected system, recovery point, image location, recovery disk, destination disk, and validation checks. Read the official overview of certification expectations and locate the current exam listing. Write down every unanswered requirement instead of filling gaps with assumptions.
Stage two: configure and recover. In a disposable lab, create or use a representative image, prepare recovery media, confirm access to the image, and restore to a test target. Document each choice and its reason. Repeat the workflow without notes, then compare your result with the documented procedure.
Stage three: troubleshoot. Change one condition at a time: make the image location unavailable, use an incorrect target, alter the virtual hardware, or interrupt a non-production test. Observe the symptom, identify the layer where it occurs, and restore the known-good state. Never experiment with production images or disks.
Stage four: exam readiness review. Turn your lab notes into scenario questions that require an explanation, not a product slogan. Check that you can justify image selection, media choice, destination planning, validation, and escalation. Only schedule when the official registration path confirms that the exam is available and you understand the applicable process.
A sample weekly rhythm
Use short theory sessions to define one workflow, followed by a lab session that proves or challenges your understanding. End each session with a written recovery decision and one unresolved question. This prevents passive reading from becoming the main activity. Adjust the pace to your lab access and the current official objectives.
On the first study block, map terminology and recovery stages. On the next, practice image discovery and recovery-media boot. Follow with a complete test restore and validation. Reserve later sessions for failure isolation, virtual-target experiments if relevant to your role, and a timed review of your own notes. These are recommendations, not official scheduling requirements.
How to decide whether you are ready to schedule
Schedule only after you can explain and perform the recovery workflow without relying on memorized prompts. You should be able to identify the evidence needed before a restore, select a sensible recovery path, explain what can go wrong at each stage, and describe how you would validate the result. If you cannot access a lab, compensate with detailed procedural review but recognize the limitation.
Use a readiness checklist: explain the purpose of an image-based recovery; distinguish recovery media from the image itself; trace image and target-disk dependencies; plan a restore to different hardware or a virtual target; isolate media, image, disk, boot, and application failures; and document a safe rollback or escalation path.
Do not use an unofficial score threshold because no passing score for this exam is supplied. Instead, rate each capability as can explain, can perform with notes, or can perform independently. Schedule when the important recovery tasks are in the independent category and the official source confirms the exam’s current availability and delivery instructions.
What the official registration process confirms
Broadcom’s supplied registration guide states that applicable Broadcom Software certification exams are written exams hosted and administered by Pearson VUE. It also says candidates use the Clarus application to search for, register for, schedule, and pay for Pearson VUE exams. Confirm that Administration of Veritas System Recovery 2013 is listed and applicable before relying on those steps. Source: https://docs.broadcom.com/doc/symantec-proctored-exam-registration-process
The certification overview describes Symantec certifications as securely proctored, computer-based exams. Together, these sources support planning around a formal proctored assessment, but they do not establish the exact delivery option, appointment length, language, identification rules, rescheduling terms, or availability for this specific exam.
The supplied registration guide includes a general user fee of $250 for the listed Pearson VUE exams unless the candidate has a voucher. Because fees and program arrangements can change, verify the amount in the current Clarus registration flow rather than treating the historical guide value as a current price.
Before payment, check the exact exam title, current product version, eligibility or voucher conditions, candidate-account details, and cancellation or rescheduling rules shown by the official registration system. Save the confirmation and use only official support channels if the exam name or appointment options are unclear.
Common preparation mistakes to avoid
The most damaging mistake is studying unsupported detail with false confidence. Candidates often assume that a related backup product, a community answer, or a remembered exam outline proves current coverage. Keep the study scope anchored to System Recovery administration and verify every time-sensitive exam fact through the official source.
Do not spend all preparation time on interface navigation. Menus matter, but scenario decisions matter more: selecting a valid image, preparing usable media, choosing a safe target, anticipating hardware differences, and validating the result. Interfaces can vary; the recovery reasoning remains the durable skill.
Do not treat a community troubleshooting thread as a definitive procedure. The supplied ESXi discussion reports a failure, but it does not document a confirmed solution. Use it to formulate questions and lab tests, then consult authoritative product documentation for the supported resolution.
Do not perform destructive practice on a production system. Use disposable targets, copies of images where appropriate, and clear restore boundaries. A technically correct recovery method can still be operationally unsafe if the target is not positively identified.
Finally, do not schedule because a question bank feels familiar. Familiarity with answer patterns is weaker evidence than being able to explain why a recovery point is suitable, what the recovery environment must access, and how you know the restored system is usable.
Your next actions before exam day
First, locate the current official listing for the exact exam and record any objectives that are absent from the supplied material. Second, build or borrow a safe lab with a representative System Recovery image and recovery media. Third, perform one documented restore and one deliberately diagnosed failure. These actions close the largest evidence and skills gaps.
Create a source-controlled study file with four labels: official certification process, official product documentation, community scenario, and lab observation. Add the URL beside every external claim. This makes it easy to remove outdated assumptions when the official exam page changes.
Prepare a final one-page runbook containing pre-restore checks, image and target verification, recovery steps, boot validation, application checks, and escalation information. The runbook is not a substitute for understanding; it is a test of whether your understanding has become operationally organized.
When the official registration path confirms the exam, schedule through the stated process, review the appointment instructions, and stop expanding the scope with unrelated NetBackup or virtualization material unless your confirmed objectives require it. Focus the final review on decisions you can justify and procedures you can reproduce safely.
Conclusion
The supplied evidence supports a practical preparation approach centered on image-based Windows recovery, recovery media, target planning, virtual or dissimilar-hardware scenarios, troubleshooting, and validation. It does not support publishing a blueprint, domain percentages, passing score, question count, duration, language list, prerequisite, or current status for this specific exam. Verify those items through the official certification and registration channels, then use a controlled lab to turn the documented recovery workflow into independent administrative skill.
