Topic: Backup / restore problems 6.0.1-1

[LeoM]

Hey all,

Don't know this is a bug, so no bugreport so far, also couldn't find anything on the forum relating to my problem.

Still having problems with backup / restore.
The solution I was thinking I had as described in my question "backup to tape not complete" could not be duplicated, or I made a mistake the first time.

Here's the set-up:

SME 6.0.1-1 cleanly installed, and then the smeplus package.
Added some users, and put some things in the ibays.
Send some mail to all the users, all working fine.
Checked and configured webmail, all fine.

Made backup to tape on a HP SureStore DAT24 streamer using an "out of the box" tape.

Received email to admin that the backup was succesfull.

Made a "clean install" again.

Restored the system from tape.

Received an email to admin that the restore was successfull, see logfile in
/var/log/messages/flexbackup.extract.log

First of all, the file wasn't there but found it at "/"

Logfile says:

| Logging output to "flexbackup.extract.200602021111.log
| Reading from CURRENT TAPE POSITION
|-------------------------------------------------------------------------
At block 1.
|-------------------------------------------------------------------------
| Extracting files listed in /tmp/restore.3292
| buffer -m 3m -s 10k -u 100 -t -p 75 -B -i "/dev/nst)" | gzip -dq | tar
|      --extract --files-from /tmp/extract.3310 --totals --same-permissions
|      --sparse -b 20 -B --file -
|-------------------------------------------------------------------------
Kilobytes Out 250670
tar: ./etc/smbpasswd: Not founf in archive
tar: Error exit delayed from previous errors
|-------------------------------------------------------------------------
At block 25068.
|-------------------------------------------------------------------------

After a reboot, there are every 15 minute mails to admin from /etc/startmail stating " fetchmail:-:7:parse error at protocol "

Webmail settings, and folders in the webmail that were set for test are gone.

Any suggestions out there?


Regards,

Leo.

[LeoM]

Additional information to the above:

When I do a fresh install (without SMEPLUS), and thereafter a backup and restore, I get the same error message (about the SMB password not found in archive) as above.

Obviously the fault is not caused by SMEPLUS or ........


Greetz,

Leo.

[CharlieBrady]

Obviously the fault is not caused by SMEPLUS or ........

Bug tracker link is to the left.

[mrjhb3]

Additional information to the above:

When I do a fresh install (without SMEPLUS), and thereafter a backup and restore, I get the same error message (about the SMB password not found in archive) as above.

Obviously the fault is not caused by SMEPLUS or ........


Greetz,

Leo.

This may be a pain, but could you try your fresh install, install yum, yum update, signal-event post-upgrade, signal-event reboot.  Create some test users, ibays, etc.  Backup.  Reload a fresh system, then go through the yum process again, then restore and see if you have better results?

[LeoM]

OK will do tomorrow, and report results.
Might take a while...

Regards, and thanks for thinking with me.

Leo.

[CharlieBrady]

OK will do tomorrow, and report results.

Please report back via the bug tracker. That's the place to track issues, this isn't.

[LeoM]

OK Charlie,

But as I said in the start of this topic, I wasn't sure this was a bug to begin with.
Could have been a hardware fault, or just lack of knowledge on my side.

I'm now getting the feeling it probably is a bug, and will report as soon as I have further details.

Regards,

Leo

[CharlieBrady]

But as I said in the start of this topic, I wasn't sure this was a bug to begin with.

And as I have said many times, anything which *might* be a bug should be reported in the Bug Tracker.

[LeoM]

Hi all,

For those who run into the same problems, here's the solution.

1. Fresh install V6.01-01
2. Update the whole lot with yum
3. install SMEPLUS (if you want, or need it)
4. restore from desktop (or tape in my case, but desktop also works).

After this, backup and restore from tape runs smooth.

So, in short; backup was working fine all the time, it was just the restore
that gave the problems.

With the updated version, this problem was gone.
So no bug to report.

Thanks everybody for thinking with me and helping me out.

mrjb3 It really was a pain, and took very long, but extensive testing
gave me the above results, and the confidence that my everyday backup
really can be used. So it was worth it.....

Regards,

Leo