Forum Replies Created

Viewing 5 replies - 1 through 5 (of 5 total)
  • Yes of corse Sed, I was just testing if the backup/restore work before any disaster.

    Hello Sed,

    I understand. So please just add that for restore we need to use another OS. For me I was surprised when I tried to test the restore and was blocked with this.

    For info, you have right, spliting is almost impossible using a direct archiving command line. But you can pipe the archive to the program “split”. Split is provided by coreutils in Linux

    GNU core utilities: This package contains the basic file, shell and text manipulation utilities which are expected to exist on every operating system.

    Without split, it’s possible to do it with rar.

    rar a -ol -m3 -vsizeb -Idp — /tmp/files.rar @/file-list

    I hope that this can be fixed in your next release. It’s normal that some people don’t have other OS.

    Or what about to give other possibility for the compression. (tar, gz, bz, rar, lzma, xz, …) some of them should exist on any company that provide hosting

    The unzip command under linux work fine if the archive is correct. Example:

    % unzip wordpress-3.5.1.zip
    Archive: wordpress-3.5.1.zip
    creating: wordpress/
    inflating: wordpress/license.txt
    inflating: wordpress/wp-activate.php
    inflating: wordpress/wp-login.php
    inflating: wordpress/readme.html
    inflating: wordpress/wp-blog-header.php
    inflating: wordpress/wp-cron.php
    …… and so on
    % ls
    wordpress wordpress-3.5.1.zip
    % du -s wordpress
    15M wordpress

    I’m sorry but I can’t test using Windows or MacOS because I don’t have this 2 OS.

    Unfortunately, I think this bug is still existing on Version 1.4.2

    unzip BackupScheduler_20130120101852_osgimbp3ma.zip
    Archive: BackupScheduler_20130120101852_osgimbp3ma.zip
    Compressed/Splitted by the SL framework (SedLex)
    warning [BackupScheduler_20130120101852_osgimbp3ma.zip]: zipfile claims to be last disk of a multi-part archive;
    attempting to process anyway, assuming all parts have been concatenated
    together in order. Expect “errors” and warnings…true multi-part support
    doesn’t exist yet (coming soon).
    file #1: bad zipfile offset (local header sig): 4
    file #2: bad zipfile offset (local header sig): 50
    file #3: bad zipfile offset (local header sig): 105
    file #4: bad zipfile offset (local header sig): 162
    file #5: bad zipfile offset (local header sig): 220
    file #6: bad zipfile offset (local header sig): 278
    file #7: bad zipfile offset (local header sig): 337
    file #8: bad zipfile offset (local header sig): 397
    file #9: bad zipfile offset (local header sig): 458
    file #10: bad zipfile offset (local header sig): 519
    file #11: bad zipfile offset (local header sig): 581
    file #12: bad zipfile offset (local header sig): 643
    file #13: bad zipfile offset (local header sig): 706
    file #14: bad zipfile offset (local header sig): 769
    …..

    No way to unpack the backups under linux :s

Viewing 5 replies - 1 through 5 (of 5 total)