drparton21

On Backblaze_Personal_Backup, I do not see a D drive. I only see a C and a Z. Also, when I try to point the temp folder for it at z:\anything (or z:\d_drive\temp, even), I get a message telling me that backblaze doesn't have read/write access to that folder. However, it's a folder that I applied chmod777 to, even. Not sure where to go from here--- has anyone else ran into this?

I was able to get past this by making my repository: tessypowder/backblaze-personal-wine:v1.5 However, I'm running into issues with read/write on the D drive.

I see some things dealing with this, but the dates and processes are all so different that I'm not sure what the direction I should go here is. Basically, I'm currently running a Windows 10 "fileserver". It hosts plex, qbittorrent, FTP server, and a few other things that I need. I'm currently transferring all the data to unraid. I originally planned to clone this Win10 install over to a VM in Unraid. However, since starting the file copy process in unraid, I've kind of fallen in love with it. I can easily just spin up containers for most of the services I need, but the big roadblock is Plex. Is there a way that I can copy the entire plex database from Windows into a docker container, and make a few changes for it to see the new locations of the libraries (which are all structured the same, they just exist in \\[unraidshare]\video\[LibraryName] instead of d:\video\[LibraryName] ? It's about 80tb of data in all. I ask this because I've got quite a few custom posters set up, corrections to different titles, and I've got several family members who live states away (a couple of them dealing with the onset of dementia) who I'd like to be able to keep serving this to without having to make any changes on their end or confusing them at all. Thanks in advance!

The discord was super helpful for this. Updating with answers I receive there in case other people have similar questions. Robocopy idea is perfectly reasonable. Bare metal NVME is doable and the Macrium clone *should* work. General structure of the plan is sound, adding in the parity drives after the initial data copy will be faster. VIRTIOFS sounds like the ticket to get what I want out of the filesystem in windows. Basically, it allows the OS to see the array/share as a local NTFS drive. Huge thank you to both DiscoverIt and smdion over on the discord!

Hey guys, So I'm about to spin up my very first UNRAID server. I'm migrating the data from my current fileserver (just running windows). That has a mix of 8-16tb drives that total up to around 150tb or so (with 85tb being used). I have 8 new 18tb drives to start my Unraid server with, and then I'm going to move the other drives over after I've got the data copied, parity built, and I feel good about where things are. Because I do still need to run Windows on my fileserver (for various services, some of which I can offload/replace with containers later) --- I plan to clone the OS drive in that. So, in my head, these are the steps I should take: Build new server, put in six of my eight 18tb drives. Boot up unraid, and create a pool with them. Robocopy the data from one share to the other. After the data finally finishes copying, do a second robocopy to pick up any files that changed in the meantime (I'm sure there will be some). Then, add my two other drives in to build parity. After parity is built and things have ran for a while, start adding the other drives (should I do several at once, one at a time, etc.?). These will get added to the same array. For the windows VM, I have Macrium Reflect that I believe I could use to clone the OS from the old server to the new VM. I suppose I'd create the pool (NVME drive, solo), and set the VM to have a drive with no OS, then boot the VM to my USB with Macrium on it? Or, would it be beneficial/possible for me to do this directly to the NVME drive, without making a pool for it? Windows will be the only thing running on that NVME. Pros/cons of doing it that way, if it's even possible? Also, for the Windows instance, are there drivers that I should install before I clone it? Afterwards, I suppose I'll map the share pool to the Windows VM. Since it'll be handling a lot of read/write to that, is there a better way to do that than traditional windows mapping? Thanks in advance!