Dear guys ,
recently i installed Backup Exec For Server From Symantec
my server is windows 2008 enterprise sp1

Everything is done when i will create backup jobs to do backup from local server disk drives and folders BUT ,
When i want to backup specified client's folder or disk after job start i will get this error

V-79-57344-65225 - A failure occurred accessing the Writer metadata.

Here is the screenshot

[img][/img]

This error refrences to a support page that will say

Open disk management and assign the System Reserved partition a drive letter

Link :

But i don't have any System Reserved partition , i did many thing even reinstall server
But on partiotioning section of installation , setup process didn't ask me to create MSR Partition

I asked in symantec forums after many days nothing useful


Now , did anyone have same situation with backup progressing and this crappy partition ?
Can i create it manually !?

Dani AI

Generated

Short, practical summary and next steps for (Windows Server 2008 / Backup Exec V-79-57344-65225)

The error you see is Backup Exec failing while VSS tries to read writer metadata. The vendor guidance to “assign a drive letter to the System Reserved partition” only helps if Windows actually created a separate System‑Reserved/boot partition. Windows will create that small partition on some clean installs (Windows 7 / Server 2008 R2 era), but it is not always present—many installs put the boot files on the main C: volume instead. Check which volume the OS marks as the “System” volume before changing anything. (learn.microsoft.com)

Quick checks (do these first)

  • Open Disk Management (diskmgmt.msc) and look at the “Status”/“Boot”/“System” columns to see which volume holds the boot manager.
  • On an elevated command prompt run vssadmin list writers to confirm all VSS writers are stable. If a writer shows Failed, that usually explains Backup Exec failures.
  • If a small System partition exists but has no letter, temporarily assign one (or bring the volume online) so the backup process can access it. Example diskpart steps:
    
    diskpart
    list volume
    select volume <n>      <- the 100MB/System volume
    assign letter=S
    exit

vssadmin list writers


If writers are failing, restart the Volume Shadow Copy service and related COM services, then reboot and recheck. ([learn.microsoft.com](https://learn.microsoft.com/en-us/troubleshoot/windows-server/backup-and-storage/no-vss-writers-listed-run-vssadmin-list-writers?utm_source=openai))

If there is no separate System Reserved partition
- That’s OK — the boot files may already be on C:. Don’t create or move partitions unless you understand boot records; doing so can render the server unbootable. If you must create/move a system partition (rare), use Microsoft tools like `bcdboot` to populate the new system partition properly. Also check that Windows automount is enabled and the system volume is online (otherwise a hidden SRP can remain offline and break backups). ([learn.microsoft.com](https://learn.microsoft.com/en-us/windows-server//administration/windows-commands/bcdboot?utm_source=openai))

Recommended sequence
1) Identify the “System” volume in Disk Management.  
2) Run `vssadmin list writers` and check Event Viewer for VSS errors; restart services and reboot if writers are failed.  
3) If a small System volume exists, bring it online / assign a letter and retry the job.  
4) If none exists and Backup Exec still fails, avoid manual partition surgery — either follow the vendor KB steps carefully or open vendor/Microsoft support. Veritas’s article on this UMI contains the standard troubleshooting steps used for this exact BE error. ([veritas.com](https://www.veritas.com/support/en_US/article.100016172?utm_source=openai))

Caution: modifying or moving boot files/partitions can break boot. Take a full image or snapshot before changing partitions or running bcdboot.

Pls i really need to solve this problem :(

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.