Bars - Invalid use of Null

[darren.staples]

have ran Bars (Backup And Restore System) on 3 different systems. 2 are fine, but 3rd one gets the following 3 errors:

[07:17:38 AM] Failed to backup files from Alternate file path - Invalid use of Null.

[07:17:38 AM] Could not backup files from Alternate file location path.

07:17:50 AM] Could not backup Cisco CallManager successfully on x.x.x.x

here is snippet of befor and after errors:

[07:16:04 AM] Backing up Cisco CallManager Registry.

[07:16:05 AM] Backing up DCD Database.

[07:16:27 AM] DC Schema information backed up successfully.

[07:16:28 AM] DC Directory configuration file backed up successfully.

[07:16:28 AM] DC Directory database backed up successfully.

[07:16:28 AM] Staging TFTP files from C:\Program Files\Cisco\TFTPpath.

[07:17:38 AM] Failed to backup files from Alternate file path - Invalid use of Null.

[07:17:38 AM] Could not backup files from Alternate file location path.

[07:17:39 AM] Staging DSN information from x.x.x.x.

[07:17:40 AM] Staging BAT CSV files.

[07:17:40 AM] Staging BAT Template files.

[07:17:50 AM] Could not backup Cisco CallManager successfully on x.x.x.x

there is no alternate file location in any CCM for TFTP - only "File Location"

[bmelzow]

I am getting the same error in my backup log.

[02:00:40 AM] Staging TFTP files from C:\Program Files\Cisco\TFTPpath.

[02:01:41 AM] [Error] Failed to backup files from Alternate file path - Invalid use of Null.

[02:01:41 AM] [Error] Could not backup files from Alternate file location path.

[02:01:41 AM] Staging DSN information from Covcmpub1.

[02:01:53 AM] [Error] Could not backup Cisco CallManager successfully on xxxx.

Any help would be greatly appreciated. If I find an answer I'll be sure to let you know.

[wrkemmer]

I am also getting this exact error after installing BARS. Backups using the old IP Telephony Backup went through with no errors. My main concern is that my backups are valid and that this error will not prevent recovery.

Any information would be appreciated.

[darren.staples]

Bars and STI Backup seem to be independent of each other; meaning that you should be able to run both - having different schedules (location can be same, as sti create .sti and Bars creates a .tar) you may want to confirm this with Cisco (and/or) try in a non production system. Have installed both on a Callmanager (pub) but only tried backing up with Bars on this system (Lab), BARs works fine - in this case (failing on production as stated in initial note)

[ssmith222]

BARS Invalid Use of Null Fix

CCM Admin go to Service Parameters, under the Service menu. Select the server being backed-up and select Cisco Tftp. Make sure all of the Alternate File Locations Parameter Values are empty. Click on Update. This will reset the AlternateFileLocation values to “”. Apparently these values can be altered during software updates. BARS should run successfully with out the Alternate file location path errors.