Topic: SME 9 backup to desktop not mounting

[hawk]

hi

I have setup a new sme 9 server
When i run my backup to desktop it is failing

Here is the emailed error
Seems backup directory is not really mounted. It should not happen.
            Verify availability of your backup volume. Stopping the backup now.
Backup terminated: backup failed - status: 7424

here is the configuration

Backup is Enabled.
Backup is made on LAN workstation 172.16.10.3 via cifs
Destination backup share folder is Linux Backup
Login is admin
Password is ********
Number of rotating backup sets is 1
Number of daily backups contained in each set is 1
Compression level (0-9) of backup is 6
Daily backup occurs at 15:29
Each daily backup session is cleanly timed out after 8 hours.
Full backup session (new backup sets) is allowed only on Tuesday

This is the identical settings from the SME 8 server i have upgraded from. This server is still on the network and the backup works fine.

Any help
thanks
john

[Stefano]

please raise a bug asap. thank you

[CharlieBrady]

It looks to me that your Subject is wrong. You are attempting 'backup to workstation', not 'backup to desktop'.

[hawk]

thank you have opened bug

http://bugs.contribs.org/show_bug.cgi?id=8502

with change from desktop to workstation

thanks

[idp_qbn]

login is admin?
1. Are you sure this is a valid user on the workstation you are trying to back up to?
2. Is the password correct?
3. Is the workstation IP correct?
4. Have you looked in the logs for what happens at the backup time?

Good luck
Ian

[hawk]

ok after doing a bit more digging i have found that this is not a new problem.

after running

[root@sme9server ~]# rpm -q e-smith-backup
e-smith-backup-2.4.0-37.el6.sme.noarch

the bug trackers say that e-smith-backup should be upgraded to
e-smith-backup-2.4.0-4.el6.sme.noarch

One of the bugs says to upgrade e-smith-backup using the SME-server - update testing.

I tried this, just looking for e-smith-backup but couldn't find it.

I found this file on the internet but not on an SME mirror, and am reluctant to download it from a dodgy web site.
Does anyone know of a safe place to download this file.

thanks

[Daniel B.]

No, you're running the latest available, which is e-smith-backup-2.4.0-37

[TerryF]

ok after doing a bit more digging i have found that this is not a new problem.

after running

[root@sme9server ~]# rpm -q e-smith-backup
e-smith-backup-2.4.0-37.el6.sme.noarch

the bug trackers say that e-smith-backup should be upgraded to
e-smith-backup-2.4.0-4.el6.sme.noarch

One of the bugs says to upgrade e-smith-backup using the SME-server - update testing.

I tried this, just looking for e-smith-backup but couldn't find it.

I found this file on the internet but not on an SME mirror, and am reluctant to download it from a dodgy web site.
Does anyone know of a safe place to download this file.

thanks

Don't do this you will be downgrading, where did you get this info from?

What are the answers to the questions posed by idp_qbn

[hawk]

hi

Username, password, workstation & IP address are correct (NAS drive), these are identical settings i use for the SME 8 i have on the network, This backup is working 100%

the log file is as follows

Jul 31 09:34:01 sme9server /sbin/e-smith/do_backupwk[19017]: /home/e-smith/db/backups: OLD 1406792041=(undefined)
Jul 31 09:34:01 sme9server /sbin/e-smith/do_backupwk[19017]: /home/e-smith/db/backups: NEW 1406792041=backup_record
Jul 31 09:34:01 sme9server /sbin/e-smith/do_backupwk[19017]: /home/e-smith/db/backups: OLD 1406792041=backup_record
Jul 31 09:34:01 sme9server /sbin/e-smith/do_backupwk[19017]: /home/e-smith/db/backups: NEW 1406792041=backup_record|StartEpochTime|1406792041
Jul 31 09:34:01 sme9server /sbin/e-smith/do_backupwk[19017]: /home/e-smith/db/backups: OLD 1406792041=backup_record|StartEpochTime|1406792041
Jul 31 09:34:01 sme9server /sbin/e-smith/do_backupwk[19017]: /home/e-smith/db/backups: NEW 1406792041=backup_record|BackupType|workstation|StartEpochTime|1406792041
Jul 31 09:34:01 sme9server esmith::event[19018]: Processing event: pre-backup
Jul 31 09:34:01 sme9server esmith::event[19018]: Running event handler: /etc/e-smith/events/actions/generic_template_expand
Jul 31 09:34:01 sme9server esmith::event[19018]: expanding /etc/dar/DailyBackup.dcf
Jul 31 09:34:01 sme9server esmith::event[19018]: generic_template_expand=action|Event|pre-backup|Action|generic_template_expand|Start|1406792041 277134|End|1406792041 352078|Elapsed|0.074944
Jul 31 09:34:01 sme9server esmith::event[19018]: Running event handler: /etc/e-smith/events/pre-backup/S10mysql-delete-dumped-tables
Jul 31 09:34:01 sme9server esmith::event[19018]: S10mysql-delete-dumped-tables=action|Event|pre-backup|Action|S10mysql-delete-dumped-tables|Start|1406792041 352405|End|1406792041 359830|Elapsed|0.007425
Jul 31 09:34:01 sme9server esmith::event[19018]: Running event handler: /etc/e-smith/events/pre-backup/S20mysql-dump-tables
Jul 31 09:34:02 sme9server esmith::event[19018]: S20mysql-dump-tables=action|Event|pre-backup|Action|S20mysql-dump-tables|Start|1406792041 360237|End|1406792042 845506|Elapsed|1.485269
Jul 31 09:34:02 sme9server esmith::event[19018]: Running event handler: /etc/e-smith/events/pre-backup/S30ldap-dump
Jul 31 09:34:02 sme9server esmith::event[19018]: bdb_monitor_db_open: monitoring disabled; configure monitor database to enable
Jul 31 09:34:02 sme9server esmith::event[19018]: S30ldap-dump=action|Event|pre-backup|Action|S30ldap-dump|Start|1406792042 845929|End|1406792042 996525|Elapsed|0.150596
Jul 31 09:34:02 sme9server esmith::event[19018]: Running event handler: /etc/e-smith/events/pre-backup/S50rewind-tape
Jul 31 09:34:03 sme9server esmith::event[19018]: S50rewind-tape=action|Event|pre-backup|Action|S50rewind-tape|Start|1406792042 996843|End|1406792043 40930|Elapsed|0.044087
Jul 31 09:34:08 sme9server /sbin/e-smith/do_backupwk[19017]: /home/e-smith/db/backups: OLD 1406792041=backup_record|BackupType|workstation|StartEpochTime|1406792041
Jul 31 09:34:08 sme9server /sbin/e-smith/do_backupwk[19017]: /home/e-smith/db/backups: NEW 1406792041=backup_record|BackupType|workstation|EndEpochTime|1406792048|StartEpochTime|1406792041
Jul 31 09:34:08 sme9server /sbin/e-smith/do_backupwk[19017]: /home/e-smith/db/backups: OLD 1406792041=backup_record|BackupType|workstation|EndEpochTime|1406792048|StartEpochTime|1406792041
Jul 31 09:34:08 sme9server /sbin/e-smith/do_backupwk[19017]: /home/e-smith/db/backups: NEW 1406792041=backup_record|BackupType|workstation|EndEpochTime|1406792048|Result|backup:7424|StartEpochTime|1406792041

the reference to upgrading e-smith-backup has several references on bugzille to a similar problem.

thanks

thanks

[TerryF]

Has the backup ever worked on the SME9 install?

Have you tried creating a completely new backup job on SME9, using different settings and in particular a different directory?

[hawk]

hi Terry

No the backup has never worked, this is a completely new installation of the latest download of sme 9 with very few contribs.
I have tried to backup to other computers and a different NAS drive on the network but keep getting the same error.

thanks

[janet]

hawk

Try doing a backup to a locally connected USB drive that has been formatted ext3 or ext4

[janet]

hawk

Also did you run
yum update
on the sme9 server ?

[hawk]

hi
thanks for all this info
i have never done a backup to usb, will try figure it out and get back to you

yes the sme 9 is fully updated

thanks

[janet]

hawk

i have never done a backup to usb, will try figure it out and get back to you

It should be very easy to do.
Just make sure your USB drive is formatted ext3/4.
It would be good to use a standard type of drive eg Western Digital Book style etc rather than a special drive in a USB case etc.
It would also be good to know that it works with sme server OK.

Connect the drive & check with
fdisk -l

Then just run Backup to workstation & select the local USB disk option, the drive name should be displayed & be selectable.
All the rest should be straightforward to understand, nothing tricky.

Note, the first run of a full backup will take a long time (many many hours) if you have a lot if data eg 500Mb or more, also depending on other factors eg USB port speed, drive speed, compression settings (higher compression settings are usually slower), type of data files being backed up (ie already compressed format or not) etc