problems using new sbackupd package in fedora 13, 14
FedoraForum.org - Fedora Support Forums and Community
Results 1 to 7 of 7
  1. #1
    Join Date
    Dec 2010
    Posts
    3

    problems using new sbackupd package in fedora 13, 14

    Hello Don!
    I opened a new thread here where we can have general discussion on how to use the sbackupd software, if you like. When we find a bug, we can go back to bugzilla and file a bug request. This will help the review request to stay focused on packaging problems.

    You are right, the restore command is:

    # sbackup-restore-gtk

    When I use it, I go to the day and month of the backup (which will appear in bold in the calendar), select it and then a list of snapshots will appear in the lower left part of the window. If I select one, then, in the right part of the window, all the files that you can restore will appear.

    Instead I saw no bold days in your screen-shots. Can you please check that the day you are selecting really has a saved backup?

    Thanks and regards,

    Mario

  2. #2
    Join Date
    Feb 2010
    Posts
    12

    Re: problems using new sbackupd package in fedora 13, 14

    Hey Mario,

    Ya, after I sent my last Post, I noticed the info in the window about the Bold Dates. I noticed that you could change the date and year to select different backups to restore. But none showed up through any months or years. I think this is because this is a new install and the Backups have Been Moved from Several Other Drives and Computers to this New Larger Backup Drive. So, the App has nothing in it's setup logs or how ever it remembers locations... on these Backup Files. I wonder if there is a way to add them to it? I thought there also was a way to select any Backup file you want. Even if it was not created by SBackup. Do I remember that wrong?

    Don

  3. #3
    Join Date
    Dec 2010
    Posts
    3

    Re: problems using new sbackupd package in fedora 13, 14

    Don, you were right: the simple-restore-gnome gives and exec() failed call when used. I probably got the linking wrong in the packaging. I'll try to fix this week.

    BTW I think sbackup should be able to find a snapshot even if it has been moved. It might be that you have to "upgrade" the snapshot to the new format. As this can be a risky operation, I suggest you to do the following:

    1) make a test backup and try to restore a file/dir. If this work than we can be sure that the installation of sbackup works.
    2) Attach a screenshot of the content of the dir of your newest backup and of one of the content of the old. This is in order to understand if your backups are in the old format and need conversion before being read.
    3) If your snapshot are in the old format they can be converted by the sbackup-restore-gtk utility

    Hope this helps

    Mario

  4. #4
    Join Date
    Feb 2010
    Posts
    12

    Re: problems using new sbackupd package in fedora 13, 14

    Ok, thanks Mario,

    Sorry it has taken so long to get back with you. This info is from several different days and times of messing with it...

    I'm running the first Backup with the new install of SBackup. I was already thinking of trying that to see it would set the Backup Dir in SBackup and make it find the older ones. So, thanks for the confirmation on that. First thing though... I got an error during the Backup process. I'm attaching a Screen Shot of the Screen at the time. The backup process kept running though. So, I'll see what it Saved... The old Backups were saved as .tgz and the new backup was saved as a .tar file.

    Now here's something very odd. I was looking through my Backups just before I ran the first backup with the new install of SBackup and I Swear none of them had this .corrupt extension. They all had either .ful or .inc. Hmmmm???

    I ran the Restore Command "sbackup-restore-gtk" after making the new Backup and No Dates are in Bold and No Backups are Listed in the Available Backups to Restore. I'm wondering if the first Backup isn't finished yet. So, I'll wait and look again later to see for sure. I watched the file .tar in Krusader and it was not growing in size like the usually do until they are done being written. So, I thought the backup process was done. I looked again, just now and it has grown allot. So, it's wasn't done yet. I'll look again later... My New Backup Does Not Show Up yet.

    My Older Backups Do Show Up. But, I cant Restore them. Because this version Can't Handel Them, Just like you Suspected...

    Error Message says Only Version 1.6 is Supported and you have 1.4. You Should Upgrade it...

    I Deleted the Corrupt Backups and and Copying them again from the original drive to see if they will still be changed to Corrupt Status by SBackup. Taking all day!:O

    Mario, would you mind if I also sent these conversations to my Blog? I like to Blog about things I learn and discover about Linux OS's...

    Don
    Attached Thumbnails Attached Thumbnails Click image for larger version. 

Name:	Selection_048-resized-800x.png 
Views:	69 
Size:	188.3 KB 
ID:	20481   Click image for larger version. 

Name:	Simple Backup Suite_047.png 
Views:	67 
Size:	53.7 KB 
ID:	20482   Click image for larger version. 

Name:	Krusader_044-800x.png 
Views:	78 
Size:	207.4 KB 
ID:	20483   Click image for larger version. 

Name:	Krusader_043-800x.png 
Views:	72 
Size:	181.4 KB 
ID:	20484   Click image for larger version. 

Name:	Selection_041-800x.png 
Views:	75 
Size:	203.6 KB 
ID:	20485  

    Last edited by dweb98; 22nd December 2010 at 04:09 AM. Reason: Add Images

  5. #5
    Join Date
    Dec 2010
    Posts
    3

    Re: problems using new sbackupd package in fedora 13, 14

    Hello Don!
    I'm happy to see you haven't given up. Thanks for the excellent material you provided as a feedback.

    I suggest to go in order:
    - The error in your last screenshot is probably due to dbus communication. This will be fixed in the final release of the package.
    - The option to compress the backup file is given in the first page of the sbackup-config-gtk app. You could choose between gzip and bzip2.
    - .ful -> full backup snapshot - .inc -> incremental. You can set the time period for a full backup in the config app
    - for the corruption of the snapshots: it usually happens if some file are not present when sbakcupd reads the directories. Did the transfer completed fine? If you are absolutely sure that they were correct, maybe it's time to file a bug at https://bugs.launchpad.net/sbackup/+filebug
    - The backups can take long time. Especially if they are full. I usually leave them for the night.

    No problem if you want to blog this! But please remember that sbackup still isn't a proper package right now and that I can't represent fedora in any way: I'm just a person who likes this os and tries to get new software working with it

    Best regards,

    Mario

  6. #6
    Join Date
    Feb 2010
    Posts
    12

    Re: problems using new sbackupd package in fedora 13, 14

    Thanks Mario,

    I'm going to just do my reply below your statements and question below. I think it will make more sense in context...

    Don

    On 12/22/2010 02:58 AM, FedoraForum.org wrote:
    > Dear dweb98,
    >
    > mrceresa has just replied to a thread you have subscribed to entitled - problems using new sbackupd package in fedora 13, 14 - in the Software forum of FedoraForum.org.
    >
    > This thread is located at:
    > http://forums.fedoraforum.org/showth...1&goto=newpost
    >
    > Here is the message that has just been posted:
    > ***************
    > Hello Don!
    > I'm happy to see you haven't given up. Thanks for the excellent material you provided as a feedback.
    >
    > I suggest to go in order:
    > - The error in your last screenshot is probably due to dbus communication. This will be fixed in the final release of the package.
    Ok, I was a little puzzled with this error. Glad you cleared it up for me.

    > - The option to compress the backup file is given in the first page of the sbackup-config-gtk app. You could choose between gzip and bzip2.
    > - .ful -> full backup snapshot - .inc -> incremental. You can set the time period for a full backup in the config app
    Yes, I remember setting all of that up on my first few runs with the old install. I just used the defaults with this new one.
    > - for the corruption of the snapshots: it usually happens if some file are not present when sbakcupd reads the directories.
    Yes, I noticed that in the Command line Output. I didn't paste it in the last Post since it was so long. There were missing files mentioned there. I'm sure that this is because of the Changes to my Drive Configurations. Since the Original Backups were made. I have moved one drive to another Computer and these were made with Fedora 12 on Different Drive than this Fedora 13 Install is running on. So, I can confirm that you are right here.
    > Did the transfer completed fine? If you are absolutely sure that they were correct, maybe it's time to file a bug at https://bugs.launchpad.net/sbackup/+filebug
    > - The backups can take long time. Especially if they are full. I usually leave them for the night.
    My memory is not so good here. If you are referring to the first backup that I ran with the new install of SBackup. I'm really not sure that it actually finished. My home directory is only 32GB on this Partition, but I don't know what the other included folders add up to. But, I can't leave my Computer running at night, since it is in my Bedroom and it has these really cool lights (I like em. But, the lights and the noise would keep me awake at night though, I've tried it:o Not to mention the added heat. I already have another Computer running all the time. It is an old 400mhz (not too loud and not much heat) Running my Web Site and File Server on Caos Linux. As far as the older backups. It's been so long since I ran them, that I couldn't say either way, if they all finished or not. I do believe that back then, I had SBackup Set to Startup with the Machine and run it's backups automatically. I do wish SBackup had a feature to notify you when a Backup Run has finished and about any errors too, in the GUI. I run Lucky Backup on this machine now and it does give this feed back in the GUI with Manual Backups. But it runs Silently in the Background normally. It does work well though. I went ahead and deleted the corrupt sbackups and copied them back from my old Fedora 12 Drive to my New Backup Drive. I ran sbackup-restore-gtk again. But this time they Don't Show Up at all in the SBackup Restore Window. They are the ones in my Krusader Snap Shot dated 03-15 and 03-19 2010. Also my new Backup Dated 12-16-2010 Does Not Show Up either. I'm thinking that even though it shows a .ful extension and is 17.4GB... Perhaps it never did finish it's initial Backup. Since my home dir alone, is 32GB today. But I'm sure I have added say... 5-10GB to is since my original run of SBackup on Fedora 13. Hard to tell here... I'm pasting the Command line output below. It shows that pretty much all Archive files on the Drive were scanned by SBackup and that the non SBackup Archives are shown as not valid. Guess that's how it works... I don't have time to run SBackup again today. I'm getting ready to Reformat that old Fedora 12 Drive with Fedora 14 today. So, I'll have to get back to SBackup Later on... I'll add some Snap Shots here too...

    > No problem if you want to blog this! But please remember that sbackup still isn't a proper package right now and that I can't represent fedora in any way: I'm just a person who likes this os and tries to get new software working with it
    Ok, thanks Mario I'll do my answering in Thunderbird and then just save them as Drafts. So, I'll just try to send them out (I can post by e-mail) to my Blog in order or just put them together in one post.

    Have a Merry Christmas, Mario!

    Don
    Attached Thumbnails Attached Thumbnails Click image for larger version. 

Name:	Simple Backup Suite_063.png 
Views:	65 
Size:	54.3 KB 
ID:	20495   Click image for larger version. 

Name:	Krusader_064-800x.png 
Views:	68 
Size:	203.2 KB 
ID:	20496   Click image for larger version. 

Name:	Simple Backup Suite_065.png 
Views:	69 
Size:	53.5 KB 
ID:	20497   Click image for larger version. 

Name:	Simple Backup Suite_066.png 
Views:	68 
Size:	52.7 KB 
ID:	20498   Click image for larger version. 

Name:	Krusader_067-800x.png 
Views:	71 
Size:	110.9 KB 
ID:	20499  


  7. #7
    Join Date
    Feb 2010
    Posts
    12

    Re: problems using new sbackupd package in fedora 13, 14

    Some of the Command Line output from running "sbackup-restore-gtk" command (the last part, it was too long for window to hold and the first part was auto deleted)...
    ot valid.
    2010-12-23 14:08:02,049 - INFO: Invalid snapshot `.lat` found: Name of snapshot not valid.
    2010-12-23 14:08:02,049 - INFO: Invalid snapshot `Bk-Blag-Thunderbird-files` found: Name of snapshot not valid.
    2010-12-23 14:08:02,050 - INFO: Invalid snapshot `.cinepaint` found: Name of snapshot not valid.
    2010-12-23 14:08:02,051 - INFO: Invalid snapshot `.thunderbird` found: Name of snapshot not valid.
    2010-12-23 14:08:02,052 - INFO: Invalid snapshot `Bk-Registry-files-windows-wine` found: Name of snapshot not valid.
    2010-12-23 14:08:02,052 - INFO: Invalid snapshot `.sane` found: Name of snapshot not valid.
    2010-12-23 14:08:02,053 - INFO: Invalid snapshot `.w3m` found: Name of snapshot not valid.
    2010-12-23 14:08:02,054 - INFO: Invalid snapshot `Bk-Thunderbird-DellGX1-admin` found: Name of snapshot not valid.
    2010-12-23 14:08:02,055 - INFO: Invalid snapshot `.filezilla` found: Name of snapshot not valid.
    2010-12-23 14:08:02,056 - INFO: Invalid snapshot `Bk-BishopCo.com` found: Name of snapshot not valid.
    2010-12-23 14:08:02,056 - INFO: Invalid snapshot `Bk-U3-System-SnaDisk-USB` found: Name of snapshot not valid.
    2010-12-23 14:08:02,057 - INFO: Invalid snapshot `.audacity-data` found: Name of snapshot not valid.
    2010-12-23 14:08:02,058 - INFO: Invalid snapshot `.kino-history` found: Name of snapshot not valid.
    2010-12-23 14:08:02,059 - INFO: Invalid snapshot `.evolution` found: Name of snapshot not valid.
    2010-12-23 14:08:02,059 - INFO: Invalid snapshot `.xine` found: Name of snapshot not valid.
    2010-12-23 14:08:02,060 - INFO: Invalid snapshot `Bk-Don's e-mail address books` found: Name of snapshot not valid.
    2010-12-23 14:08:02,061 - INFO: Invalid snapshot `2010-03-15_17.05.08.681976.gatewaygt5408.localdomain.ful` found: Unable to read mandatory file `ver`.
    2010-12-23 14:08:03,463 - DEBUG in restoregui.load_snapshotslist(588): Selected day : 2010-12-12
    2010-12-23 14:08:03,471 - INFO: Invalid snapshot `lost+found` found: Name of snapshot not valid.
    2010-12-23 14:08:03,472 - INFO: Invalid snapshot `.DCOPserver_gatewaygt5408.localdomain_:0` found: Name of snapshot not valid.
    2010-12-23 14:08:03,472 - INFO: Invalid snapshot `.xinputrc` found: Name of snapshot not valid.
    2010-12-23 14:08:03,473 - INFO: Invalid snapshot `.DCOPserver_gatewaygt5408.localdomain__0` found: Name of snapshot not valid.
    2010-12-23 14:08:03,475 - INFO: Invalid snapshot `.bash_history` found: Name of snapshot not valid.
    2010-12-23 14:08:03,476 - INFO: Invalid snapshot `.bash_logout` found: Name of snapshot not valid.
    2010-12-23 14:08:03,476 - INFO: Invalid snapshot `.bash_profile` found: Name of snapshot not valid.
    2010-12-23 14:08:03,477 - INFO: Invalid snapshot `.bashrc` found: Name of snapshot not valid.
    2010-12-23 14:08:03,478 - INFO: Invalid snapshot `.camstream` found: Name of snapshot not valid.
    2010-12-23 14:08:03,479 - INFO: Invalid snapshot `.bugzillacookies` found: Name of snapshot not valid.
    2010-12-23 14:08:03,480 - INFO: Invalid snapshot `.dvdstyler` found: Name of snapshot not valid.
    2010-12-23 14:08:03,481 - INFO: Invalid snapshot `.emacs` found: Name of snapshot not valid.
    2010-12-23 14:08:03,481 - INFO: Invalid snapshot `.gnofract4d` found: Name of snapshot not valid.
    2010-12-23 14:08:03,482 - INFO: Invalid snapshot `.gpg-agent-info` found: Name of snapshot not valid.
    2010-12-23 14:08:03,483 - INFO: Invalid snapshot `.isomaster` found: Name of snapshot not valid.
    2010-12-23 14:08:03,484 - INFO: Invalid snapshot `.gtktermrc` found: Name of snapshot not valid.
    2010-12-23 14:08:03,484 - INFO: Invalid snapshot `.hugin` found: Name of snapshot not valid.
    2010-12-23 14:08:03,485 - INFO: Invalid snapshot `.mcoprc` found: Name of snapshot not valid.
    2010-12-23 14:08:03,486 - INFO: Invalid snapshot `.recently-used.xbel` found: Name of snapshot not valid.
    2010-12-23 14:08:03,487 - INFO: Invalid snapshot `.ptbt1` found: Name of snapshot not valid.
    2010-12-23 14:08:03,487 - INFO: Invalid snapshot `.qt-recordmydesktop` found: Name of snapshot not valid.
    2010-12-23 14:08:03,488 - INFO: Invalid snapshot `.xsession-errors` found: Name of snapshot not valid.
    2010-12-23 14:08:03,489 - INFO: Invalid snapshot `.shalVideorc` found: Name of snapshot not valid.
    2010-12-23 14:08:03,490 - INFO: Invalid snapshot `flash-gordon-season1-2007-epi1-11.m2v` found: Name of snapshot not valid.
    2010-12-23 14:08:03,491 - INFO: Invalid snapshot `.yumex.conf` found: Name of snapshot not valid.
    2010-12-23 14:08:03,491 - INFO: Invalid snapshot `testdisk.log` found: Name of snapshot not valid.
    2010-12-23 14:08:03,492 - INFO: Invalid snapshot `.ICEauthority` found: Name of snapshot not valid.
    2010-12-23 14:08:03,493 - INFO: Invalid snapshot `.DivFix++` found: Name of snapshot not valid.
    2010-12-23 14:08:03,494 - INFO: Invalid snapshot `.banter.log` found: Name of snapshot not valid.
    2010-12-23 14:08:03,495 - INFO: Invalid snapshot `.dmrc` found: Name of snapshot not valid.
    2010-12-23 14:08:03,496 - INFO: Invalid snapshot `.devede` found: Name of snapshot not valid.
    2010-12-23 14:08:03,496 - INFO: Invalid snapshot `.esd_auth` found: Name of snapshot not valid.
    2010-12-23 14:08:03,497 - INFO: Invalid snapshot `.gtk-bookmarks` found: Name of snapshot not valid.
    2010-12-23 14:08:03,498 - INFO: Invalid snapshot `.gnome-rdp.db` found: Name of snapshot not valid.
    2010-12-23 14:08:03,499 - INFO: Invalid snapshot `.imsettings.log` found: Name of snapshot not valid.
    2010-12-23 14:08:03,500 - INFO: Invalid snapshot `.jackdrc` found: Name of snapshot not valid.
    2010-12-23 14:08:03,500 - INFO: Invalid snapshot `.kinorc` found: Name of snapshot not valid.
    2010-12-23 14:08:03,501 - INFO: Invalid snapshot `.libquicktime_codecs` found: Name of snapshot not valid.
    2010-12-23 14:08:03,502 - INFO: Invalid snapshot `.linphonerc` found: Name of snapshot not valid.
    2010-12-23 14:08:03,503 - INFO: Invalid snapshot `.printer-groups.xml` found: Name of snapshot not valid.
    2010-12-23 14:08:03,503 - INFO: Invalid snapshot `.netactview` found: Name of snapshot not valid.
    2010-12-23 14:08:03,504 - INFO: Invalid snapshot `.netxrc` found: Name of snapshot not valid.
    2010-12-23 14:08:03,505 - INFO: Invalid snapshot `.pulse-cookie` found: Name of snapshot not valid.
    2010-12-23 14:08:03,506 - INFO: Invalid snapshot `.setroubleshoot` found: Name of snapshot not valid.
    2010-12-23 14:08:03,507 - INFO: Invalid snapshot `.xmoverc` found: Name of snapshot not valid.
    2010-12-23 14:08:03,507 - INFO: Invalid snapshot `.xnightviewrc` found: Name of snapshot not valid.
    2010-12-23 14:08:03,508 - INFO: Invalid snapshot `.xscreensaver` found: Name of snapshot not valid.
    2010-12-23 14:08:03,509 - INFO: Invalid snapshot `.xsession-errors.old` found: Name of snapshot not valid.
    2010-12-23 14:08:03,510 - INFO: Invalid snapshot `unison.log` found: Name of snapshot not valid.
    2010-12-23 14:08:03,510 - INFO: Invalid snapshot `.conduit` found: Name of snapshot not valid.
    2010-12-23 14:08:03,511 - INFO: Invalid snapshot `Snow-Azle-TX-Don-front-back-yard-02-11-10.zip` found: Name of snapshot not valid.
    2010-12-23 14:08:03,512 - INFO: Invalid snapshot `Snow-Azle-TX-Don-Parks-Lake-Driving-02-11-10.zip` found: Name of snapshot not valid.
    2010-12-23 14:08:03,513 - INFO: Invalid snapshot `Snow-Azle-TX-02-11-20-Video-Dons-back-yard-800x600-no-fade-end.mp4.zip` found: Name of snapshot not valid.
    2010-12-23 14:08:03,514 - INFO: Invalid snapshot `thunderbird-gateway-gt5408-fedora-12-on-02-02-10.zip` found: Name of snapshot not valid.
    2010-12-23 14:08:03,514 - INFO: Invalid snapshot `Snow-Azle-TX-all-sets-02-11-10.zip` found: Name of snapshot not valid.
    2010-12-23 14:08:03,515 - INFO: Invalid snapshot `Thunderbird-DellGX1-02-03-10.tar.gz` found: Name of snapshot not valid.
    2010-12-23 14:08:03,516 - INFO: Invalid snapshot `.opera` found: Name of snapshot not valid.
    2010-12-23 14:08:03,517 - INFO: Invalid snapshot `.AbiSuite` found: Name of snapshot not valid.
    2010-12-23 14:08:03,517 - INFO: Invalid snapshot `.adobe` found: Name of snapshot not valid.
    2010-12-23 14:08:03,518 - INFO: Invalid snapshot `.shutter` found: Name of snapshot not valid.
    2010-12-23 14:08:03,519 - INFO: Invalid snapshot `.gnote` found: Name of snapshot not valid.
    2010-12-23 14:08:03,520 - INFO: Invalid snapshot `.vnc` found: Name of snapshot not valid.
    2010-12-23 14:08:03,521 - INFO: Invalid snapshot `.gvfs` found: Name of snapshot not valid.
    2010-12-23 14:08:03,521 - INFO: Invalid snapshot `.pinot` found: Name of snapshot not valid.
    2010-12-23 14:08:03,522 - INFO: Invalid snapshot `.mozilla` found: Name of snapshot not valid.
    2010-12-23 14:08:03,523 - INFO: Invalid snapshot `Bk-Dell-GX240-Win98-MyDocuments` found: Name of snapshot not valid.
    2010-12-23 14:08:03,524 - INFO: Invalid snapshot `.sweep` found: Name of snapshot not valid.

Similar Threads

  1. Problems with package manager of fedora 7
    By Ndikum in forum EOL (End Of Life) Versions
    Replies: 5
    Last Post: 27th March 2010, 03:18 PM
  2. Replies: 13
    Last Post: 21st October 2009, 11:51 AM
  3. Fedora 11 - problems with package manager and system-config-services
    By popodee in forum Installation, Upgrades and Live Media
    Replies: 2
    Last Post: 19th June 2009, 03:16 AM
  4. package-kit- Problems!
    By siscod2005 in forum Using Fedora
    Replies: 22
    Last Post: 11th March 2009, 02:09 AM
  5. FC8 yum/package update problems
    By Upaut in forum Using Fedora
    Replies: 5
    Last Post: 12th June 2008, 07:46 AM

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •