Troubleshooting Exchange 2007 backup failures using Symantec NetBackup 7

acstechs
acstechs used Ask the Experts™
on
Hello!

I've had successful backups for some time now against my Exchange 2007 clustered environment.  After upgrading to NBU 7, I am now getting error code 69 (invalid filelist specification).  I am also not able to enumerate ANY resources when selecting items to back up in the policy options.  Also, when I log in to the client and attempt to enumerate items available for backup, I do not see any Exchange resources, whereas before the upgrade I did see these resources.

Here is the contents of the bpbkar log in after a recent unsuccessful backup attempt:

8:06:26.368 AM: [5128.5016] <4> ov_log::OVInit: INF - Starting log file: C:\Program Files\Veritas\NetBackup\logs\BPBKAR\070210.LOG

8:06:26.368 AM: [5128.5016] <4> ov_log::OVInit: GENERAL Log Level: 0
8:06:26.368 AM: [5128.5016] <4> ov_log::OVInit: TCP Log Level: 0
8:06:26.368 AM: [5128.5016] <4> ov_log::OVInit: INF - the log mutex: 536
BPBKAR  NetBackup Backup/Archive  6.5GA  [Jan  4 2010]
Copyright 1993 - 2007 VERITAS Software Corporation
All Rights Reserved.

8:06:26.368 AM: [5128.5016] <2> WinMain: DAT - _pgmptr = 'C:\Program Files\Veritas\NetBackup\bin\bpbkar32.exe'
8:06:26.368 AM: [5128.5016] <2> WinMain: DAT - lpCmdLine = '-r 2678400 -ru root -dt 0 -to 0 -clnt cairexmbx-exch -class mailboxes_a-l -sched WeeklyFullA-L -st FULL -bpstart_to 300 -bpend_to 300 -read_to 300 -blks_per_buffer 512 -pdi -granular_backup -use_otm -fso -b cairexmbx-exch_1278083166 -kl 5 -ct 16 -use_ofb '
8:06:26.368 AM: [5128.5016] <2> date_debug: DAT - timezone: Pacific Standard Time, offset=28800, dst: Pacific Daylight Time
8:06:26.368 AM: [5128.5016] <2> date_debug: DAT - current time: 1278083186, 7/2/2010 8:06:26 AM
8:06:26.368 AM: [5128.5016] <2> date_debug: DAT - 01/01/94 UCT:  757382400, 12/31/1993 5:00:00 PM
8:06:26.368 AM: [5128.5016] <2> date_debug: DAT - 07/01/94 UCT:  773020800, 6/30/1994 5:00:00 PM
8:06:26.368 AM: [5128.5016] <2> WinMain: DAT - standard input handle = 608
8:06:26.368 AM: [5128.5016] <2> WinMain: DAT - standard output handle = 380
8:06:26.368 AM: [5128.5016] <2> WinMain: DAT - standard error handle = 500
8:06:26.368 AM: [5128.5016] <4> tar_backup::V_SetupJobData: INF - dwJobData: ffffffff
8:06:26.368 AM: [5128.5016] <4> tar_backup::V_SetupJobData: INF -     dwJob: ffffffff
8:06:26.384 AM: [5128.5016] <4> dos_backup::V_PreProcessing: INF - backup privileges enabled, previous = 0
8:06:26.384 AM: [5128.5016] <4> dos_backup::V_PreProcessing: INF - restore privileges enabled, previous = 0
8:06:26.384 AM: [5128.5016] <4> dos_backup::V_PreProcessing: INF - security privileges enabled, previous = 0
8:06:26.384 AM: [5128.5016] <4> dos_backup::V_PreProcessing: INF - tcb privileges enabled, previous = 0
8:06:26.384 AM: [5128.5016] <4> dos_backup::V_PreProcessing: INF - create token privileges enabled, previous = 0
8:06:26.384 AM: [5128.5016] <4> dos_backup::V_PreProcessing: INF - user name: root
8:06:26.384 AM: [5128.5016] <4> dos_backup::V_PreProcessing: INF - no access token: scheduled backup
8:06:26.384 AM: [5128.5016] <2> ov_log::V_GlobalLog: INF - BEDS_Init() Enter InitFlags:0x0
8:06:26.431 AM: [5128.5016] <2> ov_log::V_GlobalLog: INF - BEDS_Init() BEDS debgging will be enabled - dwDebugLevel = 0.
8:06:28.958 AM: [5128.5016] <2> ov_log::V_GlobalLog: INF - DumpDleInfo() DLE Device Name: C:
8:06:28.958 AM: [5128.5016] <2> ov_log::V_GlobalLog: INF - DumpDleInfo() DLE Device Name: D:
8:06:28.958 AM: [5128.5016] <2> ov_log::V_GlobalLog: INF - DumpDleInfo() DLE Device Name: Microsoft Terminal Services
8:06:28.958 AM: [5128.5016] <2> ov_log::V_GlobalLog: INF - DumpDleInfo() DLE Device Name: Microsoft Windows Network
8:06:28.958 AM: [5128.5016] <2> ov_log::V_GlobalLog: INF - DumpDleInfo() DLE Device Name: NFS Network
8:06:28.958 AM: [5128.5016] <2> ov_log::V_GlobalLog: INF - DumpDleInfo() DLE Device Name: Shadow?Copy?Components
8:06:28.958 AM: [5128.5016] <2> ov_log::V_GlobalLog: INF - DumpDleInfo() DLE Device Name: System?State
8:06:28.958 AM: [5128.5016] <2> ov_log::V_GlobalLog: INF - DumpDleInfo() DLE Device Name: Active Directory Application Mode
8:07:20.938 AM: [5128.5016] <2> ov_log::V_GlobalLog: WRN - BEDS_Init() FS_BlowOutMachine() Failed! (0x35:The network path was not found.
)
8:07:21.297 AM: [5128.5016] <2> tar_backup::V_SetupProcessContinue: TAR - CONTINUE BACKUP received
8:07:21.500 AM: [5128.5016] <2> tar_backup_tfi::setupFileDirectives: TAR - backup filename = Microsoft Exchange Mailboxes:\[A-L]*
8:07:21.500 AM: [5128.5016] <2> tar_backup::setupNBFSD_Credentials: INF - Processing nbfsd credentials and port number
8:07:22.077 AM: [5128.6188] <4> tar_base::keepaliveThread: INF - keepalive thread is active with an interval of 60 seconds
8:07:22.108 AM: [5128.5016] <2> tar_backup_vxbsa::add: INF - called with 'Microsoft Exchange Mailboxes:\[A-L]*'
8:07:22.108 AM: [5128.5016] <4> dos_backup::V_VerifyFileList: INF - unable to determine UBS type for:_BACKUP_SPECIAL_OBJECTS BEFORE Microsoft Exchange Mailboxes:
8:07:22.108 AM: [5128.5016] <4> dos_backup::V_VerifyFileList: INF - UBS Local Type for '_BACKUP_SPECIAL_OBJECTS BEFORE Microsoft Exchange Mailboxes:' --> 00000000
8:07:22.108 AM: [5128.5016] <4> dos_backup::V_VerifyFileList: INF - unable to determine UBS type for:Microsoft Exchange Mailboxes:
8:07:22.108 AM: [5128.5016] <4> dos_backup::V_VerifyFileList: INF - UBS Local Type for 'Microsoft Exchange Mailboxes:\[A-L]*' --> 00000000
8:07:22.108 AM: [5128.5016] <4> dos_backup::V_VerifyFileList: INF - unable to determine UBS type for:_BACKUP_SPECIAL_OBJECTS AFTER Microsoft Exchange Mailboxes:
8:07:22.108 AM: [5128.5016] <4> dos_backup::V_VerifyFileList: INF - UBS Local Type for '_BACKUP_SPECIAL_OBJECTS AFTER Microsoft Exchange Mailboxes:' --> 00000000
8:07:22.108 AM: [5128.5016] <4> dos_backup::V_Initialize: INF - Exchange Backup - Disabling Open File Backups, Archive Bit processing, TIR, Job Estimating and Excludes.
8:07:22.108 AM: [5128.5016] <4> backup_create: INF - NetBackup Temp Directory: 'C:\Program Files\Veritas\\NetBackup\Temp'
8:07:22.108 AM: [5128.5016] <4> dos_backup::tfs_scanstart: INF - Backup Special Objects request BEFORE Microsoft Exchange Mailboxes:
8:07:22.108 AM: [5128.5016] <2> tar_base::V_vTarMsgW: ERR - object not found for file system backup: Microsoft Exchange Mailboxes:
8:07:22.108 AM: [5128.5016] <4> tar_backup::backup_done_state: INF - number of file directives not found: 1
8:07:22.108 AM: [5128.5016] <4> tar_backup::backup_done_state: INF -     number of file directives found: 0
8:07:22.108 AM: [5128.6188] <4> tar_base::keepaliveThread: INF - keepalive thread terminating (reason: WAIT_OBJECT_0)
8:07:22.108 AM: [5128.5016] <4> tar_base::stopKeepaliveThread: INF - keepalive thread has exited. (reason: WAIT_OBJECT_0)
8:07:22.108 AM: [5128.5016] <2> tar_base::V_vTarMsgW: INF - EXIT STATUS 69: invalid filelist specification
8:07:22.108 AM: [5128.5016] <4> tar_backup::backup_done_state: INF - Not waiting for server status
8:07:22.108 AM: [5128.5016] <4> dos_backup::tfs_reset: INF - Snapshot deletion start
8:07:22.108 AM: [5128.5016] <4> OVStopCmd: INF - EXIT - status = 0
8:07:22.108 AM: [5128.5016] <2> tar_base::V_Close: closing...
8:07:22.108 AM: [5128.5016] <4> dos_backup::tfs_reset: INF - Snapshot deletion start
8:07:22.108 AM: [5128.5016] <2> ov_log::V_GlobalLog: INF - BEDS_Term(): enter - InitFlags:0x00000001
8:07:22.124 AM: [5128.5016] <16> dtcp_read: TCP - failure: recv socket (608) (TCP 10053: Software caused connection abort)
8:07:23.138 AM: [5128.5016] <16> dtcp_read: TCP - failure: recv socket (608) (TCP 10053: Software caused connection abort)
8:07:24.152 AM: [5128.5016] <16> dtcp_read: TCP - failure: recv socket (608) (TCP 10053: Software caused connection abort)
8:07:25.166 AM: [5128.5016] <16> dtcp_read: TCP - failure: recv socket (608) (TCP 10053: Software caused connection abort)
8:07:26.180 AM: [5128.5016] <16> dtcp_read: TCP - failure: recv socket (608) (TCP 10053: Software caused connection abort)
8:07:27.194 AM: [5128.5016] <16> dtcp_read: TCP - failure: recv socket (608) (TCP 10053: Software caused connection abort)
8:07:28.208 AM: [5128.5016] <16> dtcp_read: TCP - failure: recv socket (608) (TCP 10053: Software caused connection abort)
8:07:29.222 AM: [5128.5016] <16> dtcp_read: TCP - failure: recv socket (608) (TCP 10053: Software caused connection abort)
8:07:30.236 AM: [5128.5016] <16> dtcp_read: TCP - failure: recv socket (608) (TCP 10053: Software caused connection abort)
8:07:31.250 AM: [5128.5016] <16> dtcp_read: TCP - failure: recv socket (608) (TCP 10053: Software caused connection abort)
8:07:32.264 AM: [5128.5016] <16> dtcp_read: TCP - failure: recv socket (608) (TCP 10053: Software caused connection abort)
8:07:33.278 AM: [5128.5016] <16> dtcp_read: TCP - failure: recv socket (608) (TCP 10053: Software caused connection abort)
8:07:34.292 AM: [5128.5016] <16> dtcp_read: TCP - failure: recv socket (608) (TCP 10053: Software caused connection abort)
8:07:35.306 AM: [5128.5016] <16> dtcp_read: TCP - failure: recv socket (608) (TCP 10053: Software caused connection abort)
8:07:35.306 AM: [5128.5016] <4> OVShutdown: INF - Finished process
8:07:35.306 AM: [5128.5016] <4> WinMain: INF - Exiting C:\Program Files\Veritas\NetBackup\bin\bpbkar32.exe
8:07:37.334 AM: [5128.5016] <4> ov_log::OVClose: INF - Closing log file: C:\Program Files\Veritas\NetBackup\logs\BPBKAR\070210.LOG

I would appreciate any pointers... I've been troubleshooting this for two weeks and have tried everything I can find on Symantec's support site (hosts file cleanup, verifying permissions on the NetBackup service account, rebooting the clients, etc...) and haven't been able to make any progress whatsoever.  I'm coming up on two weeks of not having the Exchange store backed up.

Thank you!
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Top Expert 2010

Commented:
What are the corresponding errors in event logs
Please check under application
\application

Any other Exchange or ESE / or VSS Writer related errors.
Have you tried restarting VSS Writer and then taking a backup.

please list your steps till now.

thanks
Commented:
Per Symantec support this is a bug with NetBackup 7. We are the second customer to run into this issue and they installed a patch on our backup server that has not yet been released to the public. The bug stems from client hostnames that are longer than 12 characters. Our hostname was 14 characters. We loaded the patch and our issues appear to be resolved.
Top Expert 2010

Commented:
Wow :-)

thanks for the update on this. will save this case in my kb.

Author

Commented:
No additional comments.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial