Forum Discussion

Ashleigh_Steven's avatar
15 years ago

VCB Backups causing Unable to read next index. VFM error = 6

Hi,

Can someone please help?

I am backing up a Virtual Machine (windows 2000 Server) on a incremental file level and full backup vdmk and file level.

Full backup completes successfully.

Incremental file level completes with errors;

25/11/2009 12:32:23 PM - estimated 0 kbytes needed
25/11/2009 12:32:24 PM - started process bpbrm (4804)
25/11/2009 12:32:27 PM - connecting
25/11/2009 12:32:28 PM - connected; connect time: 00:00:01
25/11/2009 12:32:33 PM - begin writing
25/11/2009 12:32:50 PM - Error bpbrm(pid=4804) from client realm23.toll.com.au: ERR - Unable to read next index. VFM error = 6
25/11/2009 12:32:51 PM - Error bpbrm(pid=4804) from client realm23.toll.com.au: ERR - Unable to read next index. VFM error = 6
25/11/2009 12:32:51 PM - Error bpbrm(pid=4804) from client realm23.toll.com.au: ERR - Unable to read next index. VFM error = 6
25/11/2009 12:32:51 PM - Error bpbrm(pid=4804) from client realm23.toll.com.au: ERR - Unable to read next index. VFM error = 6
25/11/2009 12:32:52 PM - Error bpbrm(pid=4804) from client realm23.toll.com.au: ERR - Unable to read next index. VFM error = 6
25/11/2009 12:32:52 PM - Error bpbrm(pid=4804) from client realm23.toll.com.au: ERR - Unable to read next index. VFM error = 6
25/11/2009 12:32:53 PM - Error bpbrm(pid=4804) from client realm23.toll.com.au: ERR - Unable to read next index. VFM error = 6
25/11/2009 12:32:53 PM - Error bpbrm(pid=4804) from client realm23.toll.com.au: ERR - Unable to read next index. VFM error = 6
25/11/2009 12:32:54 PM - Error bpbrm(pid=4804) from client realm23.toll.com.au: ERR - Unable to read next index. VFM error = 6
25/11/2009 12:32:54 PM - Error bpbrm(pid=4804) from client realm23.toll.com.au: ERR - Unable to read next index. VFM error = 6
25/11/2009 12:32:55 PM - Error bpbrm(pid=4804) from client realm23.toll.com.au: ERR - Unable to read next index. VFM error = 6
25/11/2009 12:32:55 PM - Error bpbrm(pid=4804) from client realm23.toll.com.au: ERR - Unable to read next index. VFM error = 6
25/11/2009 12:32:56 PM - Error bpbrm(pid=4804) from client realm23.toll.com.au: ERR - Unable to read next index. VFM error = 6
25/11/2009 12:32:56 PM - Error bpbrm(pid=4804) from client realm23.toll.com.au: ERR - Unable to read next index. VFM error = 6
25/11/2009 12:32:57 PM - Error bpbrm(pid=4804) from client realm23.toll.com.au: ERR - Unable to read next index. VFM error = 6
25/11/2009 12:32:57 PM - Error bpbrm(pid=4804) from client realm23.toll.com.au: ERR - Unable to read next index. VFM error = 6
25/11/2009 12:32:58 PM - Error bpbrm(pid=4804) from client realm23.toll.com.au: ERR - Unable to read next index. VFM error = 6
25/11/2009 12:32:58 PM - Error bpbrm(pid=4804) from client realm23.toll.com.au: ERR - Unable to read next index. VFM error = 6
25/11/2009 12:32:59 PM - Error bpbrm(pid=4804) from client realm23.toll.com.au: ERR - Unable to read next index. VFM error = 6
25/11/2009 12:32:59 PM - Error bpbrm(pid=4804) from client realm23.toll.com.au: ERR - Unable to read next index. VFM error = 6
25/11/2009 12:32:59 PM - Error bpbrm(pid=4804) from client realm23.toll.com.au: ERR - Unable to read next index. VFM error = 6
25/11/2009 12:33:00 PM - Error bpbrm(pid=4804) from client realm23.toll.com.au: ERR - Unable to read next index. VFM error = 6
25/11/2009 12:33:00 PM - Error bpbrm(pid=4804) from client realm23.toll.com.au: ERR - Unable to read next index. VFM error = 6
25/11/2009 12:33:01 PM - Error bpbrm(pid=4804) from client realm23.toll.com.au: ERR - Unable to read next index. VFM error = 6
25/11/2009 12:33:01 PM - Error bpbrm(pid=4804) from client realm23.toll.com.au: ERR - Unable to read next index. VFM error = 6
25/11/2009 12:33:02 PM - Error bpbrm(pid=4804) from client realm23.toll.com.au: ERR - Unable to read next index. VFM error = 6
25/11/2009 12:33:02 PM - Error bpbrm(pid=4804) from client realm23.toll.com.au: ERR - Unable to read next index. VFM error = 6
25/11/2009 12:33:03 PM - Error bpbrm(pid=4804) from client realm23.toll.com.au: ERR - Unable to read next index. VFM error = 6
25/11/2009 12:33:03 PM - Error bpbrm(pid=4804) from client realm23.toll.com.au: ERR - Unable to read next index. VFM error = 6
25/11/2009 12:33:04 PM - Error bpbrm(pid=4804) from client realm23.toll.com.au: ERR - Unable to read next index. VFM error = 6
25/11/2009 12:33:04 PM - Error bpbrm(pid=4804) from client realm23.toll.com.au: ERR - Unable to read next index. VFM error = 6
25/11/2009 12:33:05 PM - Error bpbrm(pid=4804) from client realm23.toll.com.au: ERR - Unable to read next index. VFM error = 6
25/11/2009 12:33:05 PM - Error bpbrm(pid=4804) from client realm23.toll.com.au: ERR - Unable to read next index. VFM error = 6
25/11/2009 12:33:06 PM - Error bpbrm(pid=4804) from client realm23.toll.com.au: ERR - Unable to read next index. VFM error = 6
25/11/2009 12:33:06 PM - Error bpbrm(pid=4804) from client realm23.toll.com.au: ERR - Unable to read next index. VFM error = 6
25/11/2009 12:33:07 PM - Error bpbrm(pid=4804) from client realm23.toll.com.au: ERR - Unable to read next index. VFM error = 6
25/11/2009 12:33:07 PM - Error bpbrm(pid=4804) from client realm23.toll.com.au: ERR - Unable to read next index. VFM error = 6
25/11/2009 12:33:08 PM - Error bpbrm(pid=4804) from client realm23.toll.com.au: ERR - Unable to read next index. VFM error = 6
25/11/2009 12:33:08 PM - Error bpbrm(pid=4804) from client realm23.toll.com.au: ERR - Unable to read next index. VFM error = 6
25/11/2009 12:33:09 PM - Error bpbrm(pid=4804) from client realm23.toll.com.au: ERR - Unable to read next index. VFM error = 6
25/11/2009 12:33:09 PM - Error bpbrm(pid=4804) from client realm23.toll.com.au: ERR - Unable to read next index. VFM error = 6
25/11/2009 12:33:10 PM - Error bpbrm(pid=4804) from client realm23.toll.com.au: ERR - Unable to read next index. VFM error = 6
25/11/2009 12:33:10 PM - Error bpbrm(pid=4804) from client realm23.toll.com.au: ERR - Unable to read next index. VFM error = 6
25/11/2009 12:33:10 PM - Error bpbrm(pid=4804) from client realm23.toll.com.au: ERR - Unable to read next index. VFM error = 6
25/11/2009 12:33:11 PM - Error bpbrm(pid=4804) from client realm23.toll.com.au: ERR - Unable to read next index. VFM error = 6
25/11/2009 12:33:11 PM - Error bpbrm(pid=4804) from client realm23.toll.com.au: ERR - Unable to read next index. VFM error = 6
25/11/2009 12:33:12 PM - Error bpbrm(pid=4804) from client realm23.toll.com.au: ERR - Unable to read next index. VFM error = 6
25/11/2009 12:33:13 PM - Error bpbrm(pid=4804) from client realm23.toll.com.au: ERR - Unable to read next index. VFM error = 6
25/11/2009 12:33:13 PM - Error bpbrm(pid=4804) from client realm23.toll.com.au: ERR - Unable to read next index. VFM error = 6
25/11/2009 12:33:14 PM - Error bpbrm(pid=4804) from client realm23.toll.com.au: ERR - Unable to read next index. VFM error = 6
25/11/2009 12:33:14 PM - Error bpbrm(pid=4804) from client realm23.toll.com.au: ERR - Unable to read next index. VFM error = 6
25/11/2009 12:33:15 PM - Error bpbrm(pid=4804) from client realm23.toll.com.au: ERR - Unable to read next index. VFM error = 6
25/11/2009 12:33:15 PM - Error bpbrm(pid=4804) from client realm23.toll.com.au: ERR - Unable to read next index. VFM error = 6
25/11/2009 12:33:16 PM - Error bpbrm(pid=4804) from client realm23.toll.com.au: ERR - Unable to read next index. VFM error = 6
25/11/2009 12:33:16 PM - Error bpbrm(pid=4804) from client realm23.toll.com.au: ERR - Unable to read next index. VFM error = 6
25/11/2009 12:33:17 PM - Error bpbrm(pid=4804) from client realm23.toll.com.au: ERR - Unable to read next index. VFM error = 6
25/11/2009 12:33:17 PM - Error bpbrm(pid=4804) from client realm23.toll.com.au: ERR - Unable to read next index. VFM error = 6
25/11/2009 12:33:18 PM - Error bpbrm(pid=4804) from client realm23.toll.com.au: ERR - Unable to read next index. VFM error = 6
25/11/2009 12:33:18 PM - Error bpbrm(pid=4804) from client realm23.toll.com.au: ERR - Unable to read next index. VFM error = 6
25/11/2009 12:33:19 PM - Error bpbrm(pid=4804) from client realm23.toll.com.au: ERR - Unable to read next index. VFM error = 6
25/11/2009 12:33:19 PM - Error bpbrm(pid=4804) from client realm23.toll.com.au: ERR - Unable to read next index. VFM error = 6
25/11/2009 12:33:20 PM - Error bpbrm(pid=4804) from client realm23.toll.com.au: ERR - Unable to read next index. VFM error = 6
25/11/2009 12:33:20 PM - Error bpbrm(pid=4804) from client realm23.toll.com.au: ERR - Unable to read next index. VFM error = 6
25/11/2009 12:33:21 PM - Error bpbrm(pid=4804) from client realm23.toll.com.au: ERR - Unable to read next index. VFM error = 6
25/11/2009 12:33:28 PM - end writing; write time: 00:00:55

7 Replies

  • Anonymous's avatar
    Anonymous
    What version of Netbackup and VCB using?

    Analyze the bpfis logs on the proxy server.

    Make sure the guest OS does not have encrypted/compressed filesystems.

    Vmware Tools are installed OK/up to date

    6.5.4 fixes a lot of bugs/issues with Netbackup for Vmware (VCB) backups. Consider upgrading your master/media (vcb) servers.

  • Anonymous's avatar
    Anonymous
    Also troubleshoot with a test of a File Level backup direct on the Proxy server. This only mounts the snapshot on the Proxy ready for the backup software, doesnt actually backup anything.

    Handy if having problems with File Level backups at the Incremental part of the backup. Without having NetBackup in the equation.

    • Use the vcbMounter.exe utility to perform a VM mount.
    The syntax is:

    vcbMounter.exe –h <hostname> -u <user> -p <password> -a ipaddr:<VM FQDN> -r <mount point> -t <Type> -m <mode>

    The <hostname> should be the IP address or FQDN of the vCenter server or ESX server. If the VMs reside on ESX servers in a cluster, it
    must be the vCenter Server.

    In this example, the command is:

    vcbMounter.exe –h 192.168.141.10 –u vcbuser –p vcbuser –a ipaddr:192.168.141.140 –r e:\mnt\testvcb –t file –m san

    This command is case sensitive. In this example, the IP address point to the vCenter Server. The path “E:\mnt” must already exist on the VCB proxy. The “testvcb” directory will be created by the vcbMounter utility and should not be present.
     

    • The VCB Proxy will now have access to the files on “ <mount point>\letters\<drive letter>. In this example, they are available on
    E:\mnt\testvcb\letters\c.


    • The files are now available on the mount point for backup to tape by the backup software.
     
    •  Use the vcbMounter.exe utility to “unmount” the VM files.
    The syntax is:

    vcbMounter.exe –h <hostname> -u <user> -p <password> -U <mount point>

    Please note that the second “-U” is capitalized and indicates “unmount”.
    In this example, the command is:

    vcbMounter.exe –h 192.168.141.10 –u vcbuser –p vcbuser –U E:\mnt\testvcb

  • Anonymous's avatar
    Anonymous
    Is one of the volumes on this VM a RAW disk?

    recommend you upgrade to 6.5.5 now lots of bug fixes since 6.5.2 and enhancements and support added.

  • Log file for bpbkar:

    Server: REALM23;

    12:50:56.141 AM: [5552.4680] <2> tar_backupt_tfi::create: TAR - Incremental backup using file dates since: 14/12/2009 6:25:57 PM
    12:50:56.141 AM: [5552.4680] <2> tar_base::V_vTarMsgW: TRV - BACKUP 20/12/2009 12:50:56 AM realm23.toll.com.au VCB-ESXDov143 Diff-Inc INCR 14/12/2009 6:25:57 PM
    12:50:56.141 AM: [5552.4680] <2> dtcp_write: TCP - success: send socket (1872), 106 of 106 bytes
    12:50:56.141 AM: [5552.4680] <2> dtcp_read: TCP - success: recv socket (676), 14 of 14 bytes
    12:50:56.141 AM: [5552.4680] <2> tar_backup::V_SetupProcessContinue: TAR - CONTINUE BACKUP received
    12:50:56.141 AM: [5552.4680] <2> tar_backup_tfi::setupFileDirectives: TAR - Processing filename list
    12:50:56.141 AM: [5552.4680] <2> dtcp_read: TCP - success: recv socket (676), 4 of 4 bytes
    12:50:56.141 AM: [5552.4680] <2> dtcp_read: TCP - success: recv socket (676), 197 of 197 bytes
    12:50:56.141 AM: [5552.4680] <2> tar_backup_tfi::setupFileDirectives: TAR - backup filename = BACKUP \\.\C:\ USING \\?\Volume{77be05d5-c512-11de-b007-001185e748c6}\ OPTIONS:ALT_PATH_PREFIX=C:\Program Files\Veritas\NetBackup\temp\_vrts_frzn_img_8084,FITYPE=MIRROR,MNTPOINT=\\.\C:\,FSTYPE=NTFS
    12:50:56.141 AM: [5552.4680] <2> dtcp_read: TCP - success: recv socket (676), 4 of 4 bytes
    12:50:56.141 AM: [5552.4680] <2> dtcp_read: TCP - success: recv socket (676), 197 of 197 bytes
    12:50:56.157 AM: [5552.4680] <2> tar_backup_tfi::setupFileDirectives: TAR - backup filename = BACKUP \\.\D:\ USING \\?\Volume{45da82c6-cdbc-11de-a00d-001185e748c6}\ OPTIONS:ALT_PATH_PREFIX=C:\Program Files\Veritas\NetBackup\temp\_vrts_frzn_img_8084,FITYPE=MIRROR,MNTPOINT=\\.\D:\,FSTYPE=NTFS
    12:50:56.157 AM: [5552.4680] <2> dtcp_read: TCP - success: recv socket (676), 4 of 4 bytes
    12:50:56.157 AM: [5552.4680] <2> dtcp_read: TCP - success: recv socket (676), 197 of 197 bytes
    12:50:56.157 AM: [5552.4680] <2> tar_backup_tfi::setupFileDirectives: TAR - backup filename = BACKUP \\.\E:\ USING \\?\Volume{45da82ff-cdbc-11de-a00d-001185e748c6}\ OPTIONS:ALT_PATH_PREFIX=C:\Program Files\Veritas\NetBackup\temp\_vrts_frzn_img_8084,FITYPE=MIRROR,MNTPOINT=\\.\E:\,FSTYPE=NTFS
    12:50:56.157 AM: [5552.4680] <2> dtcp_read: TCP - success: recv socket (676), 4 of 4 bytes
    12:50:56.157 AM: [5552.4680] <2> dtcp_read: TCP - success: recv socket (676), 8 of 8 bytes
    12:50:56.157 AM: [5552.4680] <4> tar_base::startKeepaliveThread: INF - keepalive thread started
    12:50:56.157 AM: [5552.6836] <4> tar_base::keepaliveThread: INF - keepalive thread is active with an interval of 60 seconds
    12:50:56.157 AM: [5552.6836] <2> dtcp_read: TCP - success: recv socket (676), 4 of 4 bytes
    12:50:56.157 AM: [5552.6836] <4> bpio::read_string: INF - read non-blocking message of length 1
    12:50:56.157 AM: [5552.6836] <2> dtcp_read: TCP - success: recv socket (676), 1 of 1 bytes
    12:50:56.157 AM: [5552.6836] <4> tar_backup::readServerMessage: INF - keepalive message received
    12:50:56.157 AM: [5552.6836] <4> tar_base::keepaliveThread: INF - sending keepalive
    12:50:56.157 AM: [5552.6836] <2> dtcp_write: TCP - success: send socket (1872), 1 of 1 bytes
    12:50:57.219 AM: [5552.4680] <4> V_Snapshot::V_Snapshot_AddMappings: INF - Volume Snapshot Mapping: \\?\Volume{023d5f60-7e83-11dd-ba49-806e6f6e6963}\ --> Volume{77be05d5-c512-11de-b007-001185e748c6}
    12:50:57.219 AM: [5552.4680] <4> V_Snapshot::V_Snapshot_AddMappings: INF - Volume Snapshot Mapping: \\?\Volume{7b17c9c1-7ee5-11dd-ad25-001185e748c6}\ --> Volume{45da82c6-cdbc-11de-a00d-001185e748c6}
    12:50:57.219 AM: [5552.4680] <4> V_Snapshot::V_Snapshot_AddMappings: INF - Volume Snapshot Mapping: \\?\Volume{023d5f59-7e83-11dd-ba49-806e6f6e6963}\ --> Volume{45da82ff-cdbc-11de-a00d-001185e748c6}
    12:50:57.219 AM: [5552.4680] <4> dos_backup::V_VerifyFileSystem: INF - Verifying: \\.\C:\
    12:50:57.219 AM: [5552.4680] <4> dos_backup::V_VerifyFileSystem: INF - Verifying: \\.\D:\
    12:50:57.219 AM: [5552.4680] <4> dos_backup::V_VerifyFileSystem: INF - Verifying: \\.\E:\
    12:50:57.219 AM: [5552.4680] <4> dos_backup::V_VerifyFileList: INF - UBS Local Type for '\\.\C:\' --> 00000000
    12:50:57.219 AM: [5552.4680] <4> dos_backup::V_VerifyFileList: INF - UBS Local Type for '\\.\D:\' --> 00000000
    12:50:57.219 AM: [5552.4680] <4> dos_backup::V_VerifyFileList: INF - UBS Local Type for '\\.\E:\' --> 00000000
    12:50:57.219 AM: [5552.4680] <2> ov_log::V_GlobalLog: INF -  v_beds::V_FindFirst() ENTER Name:Shadow Copy Components Mode:0
    12:50:57.219 AM: [5552.4680] <2> ov_log::V_GlobalLog: INF - bedsShadowCopyInit():ENTER (Reason:2048)
    12:50:57.219 AM: [5552.4680] <2> ov_log::V_GlobalLog: INF - bedsShadowCopyInit():Found Resource DLE for 'Shadow?Copy?Components'
    12:50:57.219 AM: [5552.4680] <2> ov_log::V_GlobalLog: DBG -  v_beds::V_FindFirst() Device:Shadow Copy Components Obj: Pattern:(null)
    12:50:57.391 AM: [5552.4680] <2> <FROM BEDS>: Status E_NOINTERFACE (0x80004002) returned creating IVssBackupComponentsEx2 interface when initializing shadow copy
    12:50:57.719 AM: [5552.4680] <2> <FROM BEDS>: Calling IVssBackupComponents::GatherWriterMetadata...
    12:50:58.891 AM: [5552.4680] <2> <FROM BEDS>: ...completed IVssBackupComponents::GatherWriterMetadata
    12:50:58.891 AM: [5552.4680] <2> <FROM BEDS>: brUtil::brUtil( img ) Constructor
    12:50:58.891 AM: [5552.4680] <2> ov_log::V_GlobalLog: INF - Successfully attached to Device 'Shadow?Copy?Components' BackupReason:0x800
    12:50:59.094 AM: [5552.4680] <2> <FROM BEDS>: Informational status CODE (0x00000002) returned calling FindFirstFile for C:\WINDOWS\system32\perf?00?.bak when getting additional files
    12:50:59.094 AM: [5552.4680] <2> <FROM BEDS>: Informational: Writer MSDEWriter contains no components in SHADOW::EnumSpecFiles
    12:50:59.094 AM: [5552.4680] <2> <FROM BEDS>: Informational: Writer:SQL Server Logical Path:null Component:null exclusions not used
    12:50:59.126 AM: [5552.4680] <2> ov_log::V_GlobalLog: INF -  v_beds::V_FindFirst() EXIT Name:Shadow Copy Components: bRC:true LastError:0x0:
    12:50:59.141 AM: [5552.4680] <4> TransporterLegacyLocal::winClientShm(): INF - Mapping for shared memory is  (Global\NetBackup Media Manager SHM Info Path realm23.toll.com.au_1261230615) .
    12:51:00.141 AM: [5552.4680] <4> TransporterLegacyLocal::winClientShm(): INF - Shared memory detail (media_shm_info = 30 262144 1423331265 5672 0 0 0 0 1).
    12:51:00.141 AM: [5552.4680] <4> TransporterLegacyLocal::winClientShm(): INF - SHMID = 1423331265, BUF_PTR = 0x3720000, BUF_CONTROL = 0x3ea0000, readyptr = 0x3ea02d0.
    12:51:00.141 AM: [5552.4680] <4> Packer::open(): INF - Started Backup...
    12:51:00.141 AM: [5552.4680] <4> Transporter::setThrottlingParameters(): INF - Throttling parameters set in Transporter
    12:51:00.141 AM: [5552.4680] <4> backup_create: INF - NetBackup Temp Directory: 'C:\Program Files\Veritas\\NetBackup\Temp'
    12:51:00.141 AM: [5552.4680] <2> tar_base::V_vTarMsgW: INF - Estimate:-1 -1
    12:51:00.141 AM: [5552.4680] <2> dtcp_write: TCP - success: send socket (1872), 21 of 21 bytes
    12:51:00.141 AM: [5552.4680] <4> dos_backup::tfs_startraw: INF - checking for: C:\
    12:51:00.141 AM: [5552.4680] <4> V_DetermineMountInfo: INF - Checking Volume \\?\Volume{023d5f60-7e83-11dd-ba49-806e6f6e6963}\ for '\'
    12:51:00.141 AM: [5552.4680] <4> V_DetermineMountInfo: INF -   Adding NTFS Volume \\.\C: ==> \\?\Volume{023d5f60-7e83-11dd-ba49-806e6f6e6963}\
    12:51:00.141 AM: [5552.4680] <4> dos_backup::tfs_startraw: INF - RAW: \\.\
    12:51:00.157 AM: [5552.4680] <4> dos_backup::tfs_startraw: INF - RAW: C:
    12:51:00.157 AM: [5552.4680] <2> tar_backup_tfi::flash_start_state: FlashBackup of Raw partition \\.\C:\,
     Frozen Device \\?\Volume{77be05d5-c512-11de-b007-001185e748c6}\'
    12:51:00.157 AM: [5552.4680] <4> tar_base::V_vTarMsgW: INF - tar message received from vxms_start
    12:51:00.157 AM: [5552.4680] <2> tar_base::V_vTarMsgW: INF - FIML startup time = 0
    12:51:00.157 AM: [5552.4680] <2> dtcp_write: TCP - success: send socket (1872), 28 of 28 bytes
    12:51:25.704 AM: [5552.4680] <4> tar_base::V_vTarMsgW: INF - tar message received from set_globals
    12:51:25.704 AM: [5552.4680] <2> tar_base::V_vTarMsgW: INF - arg list: rawdisk C:\ inctime 1260775557 Startblk 0
    12:51:25.704 AM: [5552.4680] <2> dtcp_write: TCP - success: send socket (1872), 58 of 58 bytes
    12:51:25.704 AM: [5552.4680] <4> tar_base::V_vTarMsgW: INF - tar message received from set_globals
    12:51:25.704 AM: [5552.4680] <2> tar_base::V_vTarMsgW: INF -   clientname realm23.toll.com.au, buid realm23.toll.com.au_1261230615, filnum 0
    12:51:25.704 AM: [5552.4680] <2> dtcp_write: TCP - success: send socket (1872), 86 of 86 bytes
    12:51:25.719 AM: [5552.4680] <4> tar_base::V_vTarMsgW: INF - tar message received from vxms_error_handler
    12:51:25.719 AM: [5552.4680] <2> tar_base::V_vTarMsgW: INF - VxMS error - severity 1.
    12:51:25.719 AM: [5552.4680] <2> dtcp_write: TCP - success: send socket (1872), 31 of 31 bytes
    12:51:25.719 AM: [5552.4680] <4> tar_base::V_vTarMsgW: INF - tar message received from vxms_error_handler
    12:51:25.735 AM: [5552.4680] <2> tar_base::V_vTarMsgW: INF - VxMS Error message 1 = pgnerr: plugin ntfs returned error 1024: Provider internal error
  • Anonymous's avatar
    Anonymous
    You might want to create debugging for file mapping during backup, as it looks like there is an issue when index/mapping of the drive is about to begin.

    This is detailed in the following guide:

    NB 6.5.4 VMware Administrators Guide
    http://seer.entsupport.symantec.com/docs/325876.htm
    Page 54-55 Enabling VxMS logging

    This might give you more troubleshooting information to go on.
  • VxMS NTFS Mapping Plug-in;

    Event Type: Warning
    Event Source: VxMS NTFS Mapping Plug-in
    Event Category: None
    Event ID: 1024
    Date:  8/01/2010
    Time:  4:40:04 PM
    User:  N/A
    Computer: VCBOPDOP02
    Description:
    The description for Event ID ( 1024 ) in Source ( VxMS NTFS Mapping Plug-in ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Error: 0x00000400, in file .\NtfsMftParser.cpp, line 5283