Can't back up the V drive?

[Steve-O_ZA]

Since Monday I have not been able to back up files on my V drive, I can still back up files on any other drive though?

The drive is not corrupt, I can read all the files without issue.

This all started when a job was stuck for about 16 hours and I had to restart the BE services to cancel it, since then when I try back up any file on the V drive the beremote service crashes and I get the following error

The connection to target system has been lost. Backup set canceled.

The connection to target system has been lost. Backup set canceled.

I the event viewer I also get this

The description for Event ID 0 from source .NET Runtime cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

.NET Runtime version : 2.0.50727.4214 - Application ErrorApplication has generated an exception that could not be handled.

Process ID=0x1f10 (7952), Thread ID=0x1fd0 (8144).

Click OK to terminate the application.
Click CANCEL to debug the application.

the message resource is present but the message is not found in the string/message table

The jobs fails when Backup exec is "Snapshot Proccessing" so I think it has something to do with VSS, but a vssadmin list writers shows no errors.

I have rebooted, reinstalled backup exec and .Net but still the same problem

This is on windows server 2008 64bit with Backup Exec 12 64 bit and the V drive is on the local media server

Any ideas please, its driving me crazy!

Thanks

Steve

[Colin_Weaver]

does something like a chkdsk on the V: drive report any issues?

[pkh]

Have you tried re-installing .NET framework 2.0?

[Steve-O_ZA]

chkdsk give me no errors...

V:\>chkdsk
The type of the file system is NTFS.
Volume label is VCB_Backup.

WARNING!  F parameter not specified.
Running CHKDSK in read-only mode.

CHKDSK is verifying files (stage 1 of 3)...
  99072 file records processed.
File verification completed.
  0 large file records processed.
  0 bad file records processed.
  0 EA records processed.
  16 reparse records processed.
CHKDSK is verifying indexes (stage 2 of 3)...
  99186 index entries processed.
Index verification completed.
  0 unindexed files processed.
CHKDSK is verifying security descriptors (stage 3 of 3)...
  99072 security descriptors processed.
Security descriptor verification completed.
  58 data files processed.
CHKDSK is verifying Usn Journal...
  610880 USN bytes processed.
Usn Journal verification completed.
Windows has checked the file system and found no problems.

 856416255 KB total disk space.
 736576692 KB in 144 files.
        76 KB in 59 indexes.
         0 KB in bad sectors.
    191947 KB in use by the system.
     65536 KB occupied by the log file.
 119647540 KB available on disk.

      4096 bytes in each allocation unit.
 214104063 total allocation units on disk.
  29911885 allocation units available on disk.

I don't have .NET 2, but I do have .NET 3.5SP1 which I have reinstalled, apparently that covers all the previous versions, and also I've never had a problem before and I can still backup other drives on the system

Thanks

Steve

[pkh]

I don't have .NET 2, but I do have .NET 3.5SP1

That is strange because when you install .NET 3.5, it automatically install .NET 3.0 and .NET 2.0.

What is so special about your V: drive that it has such a high drive letter?  It is an internal drive or an external one?  If it is a mapped drive, then you should be using the UNC path to that disk.  BE runs as a batch program and it cannot back up a mapped drive.

[Steve-O_ZA]

No, its an internal disk (actually a RAID 5 array), its just been assigned V because it's our VCB dump disk, but even if I copy a file from the C drive and try to back it up from V it crashes.

If I look at programs and features it only lists .NET 3.5

[CraigV]

Mmm...I see you're running BE 12.0...why not consider upgrading to BE 2010 R3? You'd need new license keys but you can do a straight upgrade to BE 2010 R3 once you have those...

If you do decide to do the upgrade, just stop your services and grab a copy of your Data/Catalogs folders. Also, make sure that any applications you back up are supported on the BE 2010 R3 SCL...

[ZeRoC00L]

Check windows update, there may be some .Net updates available....

[Steve-O_ZA]

Windows fully up to date.

Craig its not on the budget this year!!

[ZeRoC00L]

You do not have a valid support contract on BE anymore ?
With a support contract you can upgrade for 'free'.

[Steve-O_ZA]

Nope, unfortunately not, otherwise I'd love to get 2010!

[CraigV]

You mentioned you suspected that it was VSS but that the vssadmin command showed up nothing.

Have you tried to reregister your VSS *.dlls as per the SYmantec TN below:

http://www.symantec.com/business/support/index?page=content&id=TECH70486

I've used this to quite a bit of success of late. MIght be worth a try...

[Steve-O_ZA]

Hi Craig, I was actually looking for something like that, but I could only find one for 2003, so thanks, but unfortunately it didn't help

Thanks

Steven

[CraigV]

...and the media server is fully patched with any updates from the Symantec site?

[pkh]

Since your error message indicate an error with .NET 2.0, why don't you install .NET 2.0 and see if it solves your problem.  If not, you can uninstall it.

[Steve-O_ZA · Accepted solution]

OK I formatted the drive and now it's started working again...wierd, luckily it was on a drive I could format without too much issue, if it happens with one of the other drives, it's going to be much more of a problem!

Thanks for all the help !!