Backup Exec 8.6 Open File Option not compatible with XP-SP2

[PollekePik]

when I backup a remote Windows XP2 with Backup Exec 8.6 , using Open File option, I'm experiencing the "OFO failed to initialize" problem. The backup runs but not using Open file option (so by locking the files)

Veritas seems to refuse to confirm this as a bug. I'm having a e-mail discussion with their tech support that is leading nowhere. They suggest me several KB articles that a) are not related to this problem and b) I've tried them all nevertheless.

Something is really broken.

Of course:
- Windows Firewall turned off (even the service is stopped) by means of group policy (and these are applied!)
- OFO re-installed on the remote machines to be sure
- Restrict Anonymous support is enabled on both the server and the remote machines
- Job running with domain admin privileges.

In the Veritas Newsgroup I see several other people having the same problem. Yet no solution. Can anyone help??

TIA

Paul

 

[Rovent]

Have you tried running the backup engine in debug mode, and checked that for anything odd? The two or three times i've done this, it's all been greek to me, but maybe you can see where the OFO fails to launch.

stop the job engine service, place the line '-debug' in the parameter field, and start the service again. run a couple of jobs that always seem to fail. then, stop the service and clear the parameter. if you don't, the dump file get's pretty large. . .

let us know what you find

 

[stevet3]

Also debug the remote XP machine the same way. The OFO error will show up in the remote agent debug.
Can you provide the exact error or snippet of the job log and error.

 

[PollekePik]

Hi guys,

I already had debugged the server job but it didn't make me wiser. I now debugged the REmote Agent as you suggested.
I ran a small test that had to backup a) a folder and some subfolders and b) the System State on \\PC14N.

As expected, the OFO failed to intialize and I got the Alert at appr. 9:40:27. I responded "OK" to this alert at appr. 9:41:02.
When you look into the debug log of the remote machine, you'll find this error:
3fc 14/10/2004 9:40:26: FS 9 failed to initialize: -1
3fc 14/10/2004 9:40:26: FS 16 failed to initialize: -1

OK so it shows an error but it doesn't make me any wiser.

Below is the entire log from the remote Agent.

5f0 14/10/2004 9:36:55: Running... 'Q' to stop
3fc 14/10/2004 9:40:26: Client thread starting
3fc 14/10/2004 9:40:26: FS_InitFileSys
3fc 14/10/2004 9:40:26: loaded bedsnt5.dll
3fc 14/10/2004 9:40:26: loaded bedssql.dll
3fc 14/10/2004 9:40:26: loaded bedssql2.dll
3fc 14/10/2004 9:40:26: loaded bedsxchg.dll
3fc 14/10/2004 9:40:26: loaded bedsxese.dll
3fc 14/10/2004 9:40:26: loaded bedsnote.dll
3fc 14/10/2004 9:40:26: loaded bedsmdoc.dll
3fc 14/10/2004 9:40:26: FS 9 failed to initialize: -1
3fc 14/10/2004 9:40:26: FS 16 failed to initialize: -1
3fc 14/10/2004 9:40:26: Informational: Restrict Anonymous Support is enabled
3fc 14/10/2004 9:40:26: Informational: Restrict Anonymous Support is enabled
3fc 14/10/2004 9:40:26: Informational: Restrict Anonymous Support is enabled
3fc 14/10/2004 9:40:26: Backup of \\PC14N\C$ requested
3fc 14/10/2004 9:40:26: FS_CreateTempDLE
3fc 14/10/2004 9:40:26: 0 = 1
3fc 14/10/2004 9:40:26: 1 = 1
3fc 14/10/2004 9:40:26: 2 = 1
3fc 14/10/2004 9:40:26: 3 = 1
3fc 14/10/2004 9:40:26: 4 = 1
3fc 14/10/2004 9:40:26: Informational: Restrict Anonymous Support is enabled
3fc 14/10/2004 9:40:26: 5 = 0
3fc 14/10/2004 9:40:26: Informational: Device \\PC14N\C$ is from a local Windows 2000 system
3fc 14/10/2004 9:40:26: Error 2 attempting to open the TS Database registry key
3fc 14/10/2004 9:40:26: Entering SetupLocalShareInfo
3fc 14/10/2004 9:40:26: SnapVolume failed w/ Error: 0x1.
3fc 14/10/2004 9:40:26: [no resource for 3893]
3fc 14/10/2004 9:40:26: Informational: Local share path C: used to populate the System Protected File table
3fc 14/10/2004 9:40:52: ~PushStream()
3fc 14/10/2004 9:40:52: Flushing...
3fc 14/10/2004 9:40:52: Flush complete
3fc 14/10/2004 9:40:52: [no resource for 3894]
3fc 14/10/2004 9:40:52: Snap object found, stopping any snap in progress
3fc 14/10/2004 9:40:52: Client thread terminating
660 14/10/2004 9:40:57: Client thread starting
660 14/10/2004 9:40:57: Informational: Restrict Anonymous Support is enabled
660 14/10/2004 9:40:57: Informational: Restrict Anonymous Support is enabled
660 14/10/2004 9:40:57: Informational: Restrict Anonymous Support is enabled
660 14/10/2004 9:40:57: Backup of \\PC14N\System?State requested
660 14/10/2004 9:40:57: SnapVolume failed w/ Error: 0xa1.
660 14/10/2004 9:40:57: [no resource for 3893]
660 14/10/2004 9:42:56: Exporting Registration Database to file: C:\WINDOWS\system32\config\RDB8DDAC
660 14/10/2004 9:43:34: ~PushStream()
660 14/10/2004 9:43:34: Flushing...
660 14/10/2004 9:43:34: Flush complete
660 14/10/2004 9:43:34: [no resource for 3894]
660 14/10/2004 9:43:34: Snap object found, stopping any snap in progress
660 14/10/2004 9:43:34: Client thread terminating


TIA


Paul

 

[PollekePik]

Another thing:
Veritas document 270144 says:
"With the firewall *disabled*, an attempt to perform a push install of either the Backup Exec Remote Agent or a Backup Exec Media Server will result in the following error message:
Attempting to connect to server \\server failed with the following error: Access is denied.
At this time, push installs are not possible from Backup Exec for Windows Servers or Backup Exec for NetWare Servers to Windows XP Service Pack 2 systems. Local installations of the Remote Agent can be carried out as described in the following article..."

OK, the above is not about the "OFO Fails to initialize" error, but it is clearly an acknowledgement that even with the Windows firewall DISABLED, something has changed. Let it be a bug in Windows, or in Backup Exec; it is not something *I* can solve.

Paul

 

[stevet3]

What happens if you run the job without OFO?.

I wonder if the OFO is timing out.

Try this technote and run another test with AOFO

http://support.veritas.com/docs/240501

 

[PollekePik]

Hi Steve,

No that's not it. The "OFO Failed to initialize" error comes immediately (within 1 sec)after starting the backup job. Also, on my backup server, those values had already been increased (to 600 secs) a long time ago.

Meanwhile, just out of curiosity, I ran a test an a PC where the Windows Firewall was *enabled* but with all correct program and port exceptions made (according Veritas 244303). Result is exactly the same: OFO does not initialize but backup runs OK.

I am quite convinced that it is a problem with XP-SP1, but not related to the XP firewall.
Last night we ran a backup of 10 PC's. The XP-SP1 machines gave no problem with the OFO. On the 3 XP-SP2 machines the OFO failed...

Paul (getting desperate)

 

[PollekePik]

Hi all,

after two weeks of e-mailing with Veritas and trying about everything possible, Veritas has now escalated the problem.
They will set up a test environment and see if they can reproduce it.
I will keep you informed about the results

Paul

 

[PollekePik]

Hi all,

here's what the Veritas technician said:

"I reproduced the same situation in our lab and found that I was getting the same error after installing SP2. So it seems to be some problem with SP2.

Backup Exec 8.6.3878 has not been tested with SP2 since it was not available at the time of release of V 8.6 3878.

For further troubleshooting I am escalating this case to advance support. "


So, in short, we will have to wait for a fix. Meanwhile I recommend all of you that depend on the Open File Option, and that are using BE 8.6, to wait before upgrading their XP workstations to SP2.

Paul

 

[justin2000]

I reckon you won't get a fix for this - 8.6 is going to be EOL pretty soon - may just end up being that XP SP2 is not supported with 8.6 OFO.

My only other comment is, XP SP2 is not listed on the SCL for 8.6 - they could have told you : sorry not supported