I'm testing out my offside backup completness. So in case I lose my original unraid server (fire?) can I create a new server with the same setup (accounts, Dockers, VM's user scripts) and data. 

 

I'v a old server I'm repurposing for this test. With some old HDD of various sizes that could stand in for the Array and other pool drives of the original setup.

 

I've got unraid working on the old server using the unraid usb creator and a flash backup from the original server. I did have to purchace a new key for the new USB drive.

 

Where I get stuck is at the point where I want to "restore" the array and pool setup. All drives are "wrong" according to unraid and the parity drive is to small. In the original server I've a 10 TB parity drive but all array drives are only 8TB. In the old server all drives are 8TB so the replacement parity drive can only be 8TB. 

 

Is there a way to recreate the array and pool setup with these new drives? Or is there a way to remove the old setup and create a new Array and Pools with the available drives but keep their name, mount locations such that al my Docker and VM configurations will map correctly to the array and pools when I copy their data from my offside backup to this old server?

You can do a new config (Tools - New config)

 

If you are using /mnt/user for the paths (default) no need to change anything, if you are using a pool for example, like /mnt/cache, create one with the same name.

That seems to work, I selected Keep Pool assignment, that seems to not require me to recreate the pools with those exact names but does allow me to assign new hdd's to them.

 

System is formating all drives and creating the parity disk.

Is there a way to skip the partity disk rebuild or speed it up. If all HDD's are empty? Or is it just like normal formating and every sector on the HDD needs to be hit?

2 minutes ago, NielsterHeijden said:

If all HDD's are empty?

Only if all HDDs are cleared (wiped with all zeroes), just empty won't do.

I ran into a problem where rsync couldn't sync the data from the backup onto the Unraid server. Unraid was able to sync some directories and files but often gave a "readonly filesystem (30)" error while syncing data to sub directory on /mnt/user/. in the end I had to run the rsync command to sync onto /mnt/disk1/ that didn't give me these errors. 

 

The reason why I want to use rsync is because all the file rights need to be copied to. That way the docker containers using the files could read and write to them.

 

Is there a better way in the future to do this? 

rsync should work fine with /mnt/user, anything logged on the syslog when that happens?

Sadly I don't have the logs anymore. When googling I found that the error was associated with the rsync version of the synology used as the backup source. In the end I also got the error when trying to rsync from the array too a different part of the array. Just to try I synced to /mnt/disk1/ and it worked miracously. But thanks for the comfirmation that is should have worked, now I know I have to dig deeper or ask sooner the next time.

 

Thanks for all the quick support. 

 

btw this was what i found:

 

https://askubuntu.com/questions/1366414/error-while-coping-from-read-only-source-using-rsync