VCB file-level backup cause vcb-proxy stop responding

[CogemeInformati]

Situation:

Virtual infrastructure with 4 Esx 3.5 update 3 nodes, VC 2.5 on dedicated VM, VCB 1.5 on phisical backup server (W2003, Symantec BE 12.5) that is vcb-proxy server

Problem:

This become some days ago. Vcb mount script for file-level backup start correctly, snapshot ok on VC, destination folders created on vcb-proxy but nothing copied there.Trying to access machine via Remote desktop or console is impossible, the only thing to do is phisical shutdown!

Some things to know:

We don't have machine old syslog to know if theproblem appear after some upgrades (windows update or others)

Upgraded Esx, Vc, VCb a mont ago --> ok without problems on vcb and backups

Upgraded Symantec Backup Exec to version 12.5 three weeks ago --> ok without problems on vcb and backups

Upgraded Symantec antivirus from Corporate to Endpoint 11 (MR3) about 10 days ago --> ok without problems on vcb and backups

Tested operations:

vcb mount full vm operations: ok

vcb mount file-level: stop responding

others vcb script (as vcbcleanup or vcbvmname): ok

modify file-level script into full-vm script: ok

try with other vc authorized account: stop responding

try reinstall vcb: stop responding

try exclude vcb destination folder from antivirus monitoring: stop responding

try disable antivirus: stop responding

try starting vmware virtual mount manager extended (vmount2.exe) as vcb authorized user: stop responding

try restart VC server: stop responding

Any help appreciated. Thanks. Bye.

[celak]

Hi cogeme,

1)

Just in case, have you checked your VCB Proxy (Win2003) automount settings.

diskpart > automount disable

diskpart > automount scrub

2)

Do you have any other pending snapshots of these volumes?

3)

And one important thing is permissions on the backup area.

In file level if you are mounting NTFS volumes , and you don't have the appropriate access rights to files and folders you may have this issue.

At least Administrator must have the read access on all objects in the NTFS volume.

Good luck.

[CogemeInformati]

Hi celak,

1. executed dispart automount disable and scrub

2. there are no other sessions, we run vcbcleanup anytime we are going to test the vcb mounter

3. we have re-checked permission, there were right.

Try vcb mount but problem persist.

[Christian_Somme]

Hi!

Any new solutions or ideas?

Have you fixed it?

I got the same Problem since 2 weeks.

Greetings

Chris