fbackup problem

[Cheng Wee]

Hi

I experienced another fbackup problem, the attached file shows the br_log file. The fbackup schedule on jan 28 was recorded because we did a partial backup to test it out.

any suggeston on what steps can be taken to solve it?

[Steven E. Protter]

I don't see any error codes in the file you attached.

Can you please explain what happened?

SEP

[T G Manikandan]

Exit code 0 is successful backup.No problem

[Cheng Wee]

hi

Sorry for not explain clearly, we suppose to backup everyday and from the br_log, the backup stop after 20 jan. the entry which u see on 28 jan is the manual backup we use to try out the fbackup. And, in that br_log, there is also incomplete br_log entry in between the 20 jan entry and 28 jan entry.
incomplete in this case means, the entry is different compare to usual entry.

sorry for my bad english

rgs

cheng wee

[Darren Prior]

Hi,

It certainly looks like something went wrong on Jan 21, though the backup shows an exit code of 0. Were any changes made to the filesystem structures between the Jan 20 backup running and Jan 21?

I'd check if:

1) crontab shows any br_backup jobs set to run.
2) cronlog shows any automated backups running after Jan 21, also the stop time for the Jan 21 backup.
3) SAM still shows that an automated backup is set to run.

regards,

Darren.

[Cheng Wee]

Hi

Strange enough, scheduled fbackup is back to normal again. We actualli didn't change any setting but just run a manual fbackup yesterday. Any possible explain on this matter?

rgs

cheng wee

[Darren Prior]

Hi,

There's not very much info to go on. The facts we know so far are that a backup stopped mysteriously and didn't run until after the manual one.

You need to check the items I mentioned previously to see if cron even attempted to run the backups or not. Did anyone make any changes to the system? Is your system patched with regards to cron, fbackup and SAM?

regards,

Darren.

[Cheng Wee]

Hi

It seems like we got the culprit. form the cron log and syslog, we found that the /var directory is out of space during the time the fbackup was executed. Hopefully by trimming the logfile can solve the problem.
Thks for ur reply again

Rgs

Cheng Wee