Has anyone actually got YaST’s “System Restore” to work, where it can read the archive(s) created by YaST “System Backup”? Out of several archives done by the SYSTEM BACKUP program, I think I was able to get the SYSTEM RESTORE to be able to read only one archive file, in openSUSE 12.3 KDE, and this problem occurred to me when I needed it the most. For openSUSE 13.1, the problem still remains (here); for experimental purposes, I did a SYSTEM BACKUP, then immediately attempted to restore it, but it could “not read the archive” and stated that it was probably not created by YaST’s SYSTEM BACKUP.
I am using it. It works fine. It doesn’t restore everything perfectly, but almost 80-90% of settings are restored - even in OS-13.1
Haven’t tested this, but I would be very unhappy with an 80-90% result, horrifying. Backups need to be 100% reliable, a restore should be an exact replica of the original.
On 2013-12-22 16:16, Knurpht wrote:
>
> ganesanrajesh;2610538 Wrote:
>> I am using it. It works fine. It doesn’t restore everything perfectly,
>> but almost 80-90% of settings are restored - even in OS-13.1
>
> Haven’t tested this, but I would be very unhappy with an 80-90% result,
> horrifying. Backups need to be 100% reliable, a restore should be an
> exact replica of the original.
But yast backup has never been an exact replica. I have not tried it recently. I tried it years ago
and did not like it. Then it just saved changed files from the rpm database.
I would have to try it again to see what it does now.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” (Elessar))
I don’t mean the filesystem, the tree or such, I mean an exact replica of what it was told to backup. F.e. extraction of a tar should give an exact replica of what was put in it.
On 2013-12-22 17:06, Knurpht wrote:
>
> robin_listas;2610621 Wrote:
>> But yast backup has never been an exact replica.
>
> I don’t mean the filesystem, the tree or such, I mean an exact replica
> of what it was told to backup. F.e. extraction of a tar should give an
> exact replica of what was put in it.
I think that it does.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” (Elessar))
Hi all,
I gave it a try - using the backup to store a restore tar archive on my NAS via NFS.
It was a horrifying experience - I’m not quite sure what I did wrong (supposing that it was my mistake).
I just created a profile for the backup and configured
- the file name (eg. myserver.tar)
- the target NFS server (e.g. mybox)
- the target NFS directory (e.g. /targetvol/backup) - which is the NFS share I use to backup everything to (so there are a lot of directories and files lying there)
chose “tar with tar-gzip subarchives” and configured it to create CD-sized archive files.
Then I hit start
and everything seemed to be fine - the backup did a lot of inspection of packages and built the list of changed files
then it processed the archive and stored it on the NFS target.
Then it stopped luckily - without errors.
That something went terribly wrong was obvious some seconds later when a dolphin refresh on the NFS mount /targetvol/backup suddenly showed NO MORE FILES AT ALL. :sarcastic:
Everything was gone!
Neither had the backup written any files to the NFS share (so no “myserver.tar”) but also everything else that was located on that share has been deleted.
I know that it had to be the interaction with the backup operation because I stored some files manually there (using rsync -av) , minutes before I tried the system backup. And back then everything was still ok. I still could see anything in dolphin (also the freshly rsynced files).
Of course I immediately logged on to the NAS and inspected the file system “locally” not through the NFS export to see if something was left. But it was empty - completely. 
I still suppose that I did something wrong - but at least it seems that this is an easy mistake to do (no warning anywhere that there be dragons).
So I am kind of cured of this backup solution. For me it has done the exact opposite of backup…
Had anybody else experienced the same?
BTW: I’m using a Synology NAS with NFS v3 shares (I guess the NAS does not support NFS v4) together with SuSE 13.1.
still somewhat shocked greetings
bjo
On 2014-01-19 12:16, bjohanns wrote:
> Had anybody else experienced the same?
Never.
No idea why such a thing would happen.
–
Cheers / Saludos,
Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)