VCB issue

Greetings,

My VMWare guy moved on to another company in mid June.  He was using VCB to backup our virtual environment.  He has 5 batch files that take snap shots of the virtual servers and dumps them onto a server that is running windows 2003 and Symantec Backup Exec, and he backs up the dumped images this way.  Well, back in mid July, one of the 5 batch files began failing.  The server is a Linux Ubuntu web server, and I frankly have no idea why/ how this scheduled batch job began failing.  The batch files start at 1:00AM, and it's the 2nd of the 5 jobs that is not taking a snap shot.  Below I am going to paste text my colleague summed up for me in an email when he set VCB up and will also paste the syntax from the batch file.

My gut tells me it's not an issue with the batch file itself, but rather on the linux web server that is supposed to have it's imaged dumped.  Here is a summary of VCB from an email he sent to me in bold font:

VCB integrates with a number of third-party backup applications, including Symantec BackupExec, which we are currently using. The backup process begins with a scheduled job kicking off inside of BackupExec. The BackupExec software calls the VCB framework to handle all VMware backup commands. The first thing VCB does is take snapshot of the target virtual machine which preserves the memory, hard disk data, and VMware configuration files at the time the snapshot is taken. It also “freezes” the target hard disk, and begins writing and logging any new disk changes to the snapshot files. This prepares the filesystem for a consistent and reliable backup (since the base filesystem is no longer being written to) while leaving the virtual machine in a completely functional state.

After the snapshot is taken, for a file-level backup, the contents of each volume of the virtual disks are dumped into a directory which is specified in the VCB configuration file. For example, if I created a job to backup the contents of the C drive on mfa-helpdesk, the files would be imported to the VCB proxy in E:\VM Backups\mfa-helpdesk\letters\C. From here, BackupExec now copies this directory to tape. After the backup job is completed, VCB will remove the directory from the VCB proxy, commit all changes made to the disk since the time it was frozen, and remove the snapshot files.

The same process happens during a full VM backup (image-level backups), only the folder created on the VCB proxy will be E:\VM backups\mfa-helpdesk-fullVM. This directory will contain the actual virtual machine files that are necessary to restore the entire machine via VMware Converter. Image-level backups are supported on virtual machines running any operating system, while file-level backups are only supported on Windows virtual machines.

The entire backup process takes place over the fiber channel (SAN), uses little to no network bandwidth, and is the recommended method of backup by VMware. The majority of backups performed on our web production environment will be full VM backups due to their operating systems, but they are the quickest and easiest way to perform a full restoration of a virtual machine.

Synatx of the batch file:

"C:\Program Files\VMware\VMware Consolidated Backup Framework\vcbmounter.exe" -h mfa-hs21-1.mfa.org -u vmbackups -p S3rv!c3 -a ipaddr:mfa-prod-web1.mfa.org -t fullvm -r "e:\VM Backups\mfa-prod-web1.mfa.org-fullVM" -m san

call mfa-prod-db1.bat

Does anyone have any idea what might have hiccupped?  The server that the images are dumped to are giving no errors for 1:00 AM in the app or system logs.

Thanks,

Jon