Page 1 of 1

Backup error: /SBC logging without final state message

Posted: October 23rd, 2009, 12:12 pm
by hansatuofd
I am getting the following error on one of my backups: "X/0001216440/SI20091022223014/SBC logging without final state message". Please provide some insight on the meaning of the error message and possible solutions.

Re: Backup error: /SBC logging without final state message

Posted: November 5th, 2009, 1:27 pm
by hansatuofd
Here is some additional information.

The failure is always on the same client, and the sep sesam client errors, but only on a second backup without a restart (I.E. as long as I restart the sep sesam service each day between backups I get a good backup, if I don't restart the client the second backup fails with this error.)

In eventvwr I see the following error report:

Faulting application sbc.exe, version 3.2.0.19, faulting module vssapi.dll, version 5.2.3790.3959, fault address 0x0001ffd1.

Re: Backup error: /SBC logging without final state message

Posted: November 30th, 2009, 4:15 pm
by hansatuofd
Is there anyone from Sep monitoring here who can provide some suggestions?

Re: Backup error: /SBC logging without final state message

Posted: December 15th, 2009, 3:50 pm
by ossi1001
Hy,

which OS and Sesam Klient are you using? Which backup source did you try?
It seems, you want to execute a VSS backup due to the vssapi.dll, which is visible in your second post.


BR, ossi1001

Re: Backup error: /SBC logging without final state message

Posted: December 15th, 2009, 6:22 pm
by hansatuofd
Thanks for the response.

The server where the error is occurring is running Windows Server2003 Service Pack 2. The installed Sesam client is version 1.2.347. We do have the '-o vss' option set for this backup. We are running other servers with the -o vss and are not seeing this same error message on them. It is a path backup as source with a partial list of the systems files

FYI, if it matters our backup server runs RHEL5 and has Sesam server version 3.4.1.67 20090918133504

Please let me know if you need any additional information.

Re: Backup error: /SBC logging without final state message

Posted: December 21st, 2009, 10:28 am
by ossi1001
Hy again,

the version 1.2.347 is not useful. Please open the file <sesam-root>\var\ini\sm.ini on this client and post the version, which is visible aside version. If you created a backup task, which includes partitions and system_state, this won't work (i.e. backup source = C:, D:, system_state).
In this case you have to create two seperate backup tasks. One task with the partitions and one task with system_state.

Greetings, ossi1001

Re: Backup error: /SBC logging without final state message

Posted: December 21st, 2009, 1:20 pm
by hansatuofd
The client version is:
version=client,3.4.1.88,20091008091357

With all of my backups I run the system_state backup as a separate task from the path_backups

thanks for you help,

John

Re: Backup error: /SBC logging without final state message

Posted: January 18th, 2010, 12:01 pm
by ossi1001
Does the backup work now or do you still have problems?

Greetings, ossi1001

Re: Backup error: /SBC logging without final state message

Posted: January 18th, 2010, 2:40 pm
by hansatuofd
I still get the same error. It is intermittent, a restart of the sesam service and then run the backup a second time usually gets a good one. So, for now I have switched the daily back-ups to drop using -o vss (on this server it is not critical for the incremental backups), and then if the weekly fails once I just re-run it <frown>

One thing I didn't do ( and should) is to check the status of patches on the backup server and on the server I am backing up. Neither of them is way out of date, but both of them are likely to have at least a small block of patches from Microsoft to install. I will post again after I get those patches load and test for a couple of weeks.

Re: Backup error: /SBC logging without final state message

Posted: January 16th, 2013, 8:10 am
by anjana
Does anyone over here know about the requirements in hardware and software needed to operate a SEP sesam server? And one more thing does the SEP sesam server use a lot of disk space on the local hard disk? If it does what can, I do to reduce it. Can anyone help?