Missing TIR info causes incrementals to be fulls

[Seth_Bokelman]

Has anyone seen this type of error before, or know how to fix it?  Removing and reinstalling the client software didn't help, and it's up to date, version 6.5


8/11/2009 1:29:43 AM - started
8/11/2009 1:29:44 AM - estimated 586555862 kbytes needed
8/11/2009 1:29:44 AM - started process bpbrm (3612)
8/11/2009 1:29:48 AM - connecting
8/11/2009 1:29:49 AM - connected; connect time: 00:00:01
8/11/2009 1:29:54 AM - begin writing
8/11/2009 1:32:49 AM - Warning bpbrm(pid=3612) from client mercury.chfa.uni.edu: WRN - old TIR info file 'C:\Program Files\Veritas\NetBackup\tir_info\D\NetBackup_file_info.Windows' is missing. Backing up everything in 'D:'
8/11/2009 1:32:49 AM - Warning bpbrm(pid=3612) from client mercury.chfa.uni.edu: WRN - old TIR info file 'C:\Program Files\Veritas\NetBackup\tir_info\D\NetBackup_file_info.Windows' is missing. Backing up everything in 'D:'
8/11/2009 2:28:32 AM - Warning bpbrm(pid=3612) from client mercury.chfa.uni.edu: WRN - old TIR info file 'C:\Program Files\Veritas\NetBackup\tir_info\E\NetBackup_file_info.Windows' is missing. Backing up everything in 'E:'
8/11/2009 2:28:32 AM - Warning bpbrm(pid=3612) from client mercury.chfa.uni.edu: WRN - old TIR info file 'C:\Program Files\Veritas\NetBackup\tir_info\E\NetBackup_file_info.Windows' is missing. Backing up everything in 'E:'
8/11/2009 3:04:12 AM - Warning bpbrm(pid=3612) from client mercury.chfa.uni.edu: WRN - old TIR info file 'C:\Program Files\Veritas\NetBackup\tir_info\F\NetBackup_file_info.Windows' is missing. Backing up everything in 'F:'
8/11/2009 3:04:12 AM - Warning bpbrm(pid=3612) from client mercury.chfa.uni.edu: WRN - old TIR info file 'C:\Program Files\Veritas\NetBackup\tir_info\F\NetBackup_file_info.Windows' is missing. Backing up everything in 'F:'
8/11/2009 12:21:21 PM - Warning bpbrm(pid=3612) from client mercury.chfa.uni.edu: WRN - can't open object: Shadow Copy Components:\System Service\File Server Resource Manager\FSRM Configuration on Volume F:/ (BEDS 0xE0009421: No component files present on the snapshot.)
8/11/2009 12:22:49 PM - Warning bpbrm(pid=3612) from client mercury.chfa.uni.edu: WRN - old TIR info file 'C:\Program Files\Veritas\NetBackup\tir_info\C\NetBackup_file_info.Windows' is missing. Backing up everything in 'C:'
8/11/2009 12:22:49 PM - Warning bpbrm(pid=3612) from client mercury.chfa.uni.edu: WRN - old TIR info file 'C:\Program Files\Veritas\NetBackup\tir_info\C\NetBackup_file_info.Windows' is missing. Backing up everything in 'C:'
8/11/2009 1:05:51 PM - end writing; write time: 11:35:57
the requested operation was partially successful(1)

The job was successfully completed, but some files may have been
busy or unaccessible. See the problems report or the client's logs for more details.

[Seth_Bokelman]

Correction, that should say 6.5.4

[GabrielMatthews]

So we're backing up a windows 2003 server in a remote office (remote meaning it uses a slow T1), and the incremental backups are obviously a bonus in this scenario.  But, we get the same error you do:

08/13/2009 18:02:48 - Warning bpbrm (pid=3556) from client vader.qcommcorp.ad: WRN - cannot open old TIR info file 'G:\Program Files\Veritas\NetBackup\tir_info\System State:\NetBackup_file_info.vader'. Backing up everything in 'System State:'
08/13/2009 18:02:51 - Warning bpbrm (pid=3556) from client vader.qcommcorp.ad: WRN - can't open object: System State: (WIN32 -536805685: Unknown error)
08/13/2009 18:02:52 - Warning bpbrm (pid=3556) from client vader.qcommcorp.ad: WRN - cannot open old TIR info file 'G:\Program Files\Veritas\NetBackup\tir_info\System State:\NetBackup_file_info.vader'. Backing up everything in 'System State:'
08/13/2009 18:02:52 - Error bpbrm (pid=3556) from client vader.qcommcorp.ad: ERR - Error encountered while attempting to get additional files for _BACKUP_SPECIAL_OBJECTS AFTER System State:
08/13/2009 18:33:49 - Warning bpbrm (pid=3556) from client vader.qcommcorp.ad: WRN - old TIR info file 'G:\Program Files\Veritas\NetBackup\tir_info\G\NetBackup_file_info.vader' is missing. Backing up everything in 'G:'
08/13/2009 18:33:51 - Warning bpbrm (pid=3556) from client vader.qcommcorp.ad: WRN - old TIR info file 'G:\Program Files\Veritas\NetBackup\tir_info\G\NetBackup_file_info.vader' is missing. Backing up everything in 'G:'
08/14/2009 02:49:06 - Warning bpbrm (pid=3556) from client vader.qcommcorp.ad: WRN - old TIR info file 'G:\Program Files\Veritas\NetBackup\tir_info\C\NetBackup_file_info.vader' is missing. Backing up everything in 'C:'
08/14/2009 02:49:08 - Warning bpbrm (pid=3556) from client vader.qcommcorp.ad: WRN - old TIR info file 'G:\Program Files\Veritas\NetBackup\tir_info\C\NetBackup_file_info.vader' is missing. Backing up everything in 'C:'
08/14/2009 03:55:20 - Warning bpbrm (pid=3556) from client vader.qcommcorp.ad: WRN - can't open file: C:\WINNT\Profiles\All Users\Application Data\Microsoft\Microsoft Operations Manager\ForefrontClientSecurity\EventCons (WIN32 32: The process cannot access the file because it is being used by another process. )
08/14/2009 03:55:46 - Warning bpbrm (pid=3556) from client vader.qcommcorp.ad: WRN - can't open file: C:\WINNT\Profiles\NetworkService\Local Settings\Temp\MpCmdRun-85-421CFC91-A93E-42AB-A35C-F06F127FCC44.lock (WIN32 32: The process cannot access the file because it is being used by another process. )

Obviously some of those files being locked or un-openable aren't related, but I included them just in case.

In our scenario, the C drive is really full, like less than 200 megs available.  The VSP snapshots fail because it wants to create a big file on the C drive, so we instead use the Windows VSS.  Perhaps this is a similar scenario to yours?

[dustin_yonak]

Good morning Seth, I found the following TechNote that may be helpful:
http://seer.entsupport.symantec.com/docs/302249.htm

Hopefully this helps out, if not you may want to open a case with our support team so we can gather some logging to investigate further.