flylowlikerylo
-
Posts
4 -
Joined
-
Last visited
Posts posted by flylowlikerylo
-
-
I reinstalled .441 on Saturday and created a cloud drive using Google Drive. I added the cloud drive to my drive pool and used file placement and duplication rules to put a fourth copy of data that is stored locally on three separate drives on to the cloud drive. Configured this way, about 60 GB of data uploaded to the cloud that night. However, ever since the data was uploaded CloudDrive indicates that it is downloading from the cloud at a constant rate of about 6-15 Mbits/s using one thread. It never stops and has been constant for the past 36 hours or so. Beyond the issue of perpetual bandwidth use, this situation appears to be preventing my local drives that hold copies of the same data duplicated on the cloud drive from spinning down (confirmed via scanner). The local drives just keep getting pulses of activity every few seconds.
My question is whether this is a (somewhat) temporary situation involving verification of the integrity of the data on the cloud drive and will stop once all of the data has been verified. If not, what do I need to do to stop the continuous downloads so that my local drives can spin down?
-
As Drashna stated earlier, this is an option but depending on your configuration it may cause the pool condition to be "unhealthy" as it's violating the rules/balancing options for the other drives.
So, as a workaround, I kicked around the idea of doing differential backups to the cloud, using CloudDrive. Unfortunately, the latest version is on shaky 'experimental' ground with Amazon. Hopefully this gets sorted out soon.
Oh, and FYI; I was thinking about using my license of Acronis for differentials (since I already had a license). For some reason, it'll only let me get a sector-level backup of my DrivePool, NOT differential. Nuts! :/
So that means using Acronis for diff backups is out.... and so is Amazon.... Double Nuts.... this is turning into a pair of fat nuts.
Ah well, it's still BETA. All in due time.
Yeah, I guess I'm not clear on what would cause the pool condition to be "unhealthy" or why doing this would violate balancing rules if you configured them correctly. The only balancers I use are StableBit Scanner, Prevent Drive Overfill, and Duplication Space Optimizer in that priority. I find it pretty straight forward to just set the folder duplication and then direct the pool to place folders only on the drives I want. I realize my pool may be relatively simple as it consists of only 4 local drives (single volume on each) and one cloud drive - but this has been a straightforward way to accomplish a 4,3,1 setup (or so I thought).
In any case I had to uninstall CloudDrive for now as it has caused my server to become unstable (cloud drive keeps dropping out of the drive pool and causing issues with the server being unable to restart and preventing access to the server remotely). I couldn't even remove the cloud drive from the drive pool without crashing the DrivePool UI. After uninstalling CloudDrive the server is stable again. At no point did DrivePool indicate the pool was "unhealthy" (other than the cloud drive dropping out).
I was using Dropbox as the provider and CloudDrive would perpetually say that it needed to be reauthorized so that might have been at the root of the issue. There definitely appeared to be non-network related communication issues at play.
I also Attempted using Amazon as the provider but that was a nonstarter. If Google Drive becomes an option at some point I will reinstall and give that a try.
-
My apologies if this has been discussed before...
I want to implement the 3,2,1 rule (3 copies, 2 local, one remote/cloud) using DrivePool and CloudDrive. For important files, I would like 2 copies of files stored locally (spanned at least two disks, which I'm already doing) with a third copy stored in the cloud via a CloudDrive disk added to the pool. How can I use the balancers to enforce that a (third) copy is always made specifically to the CloudDrive disk, and not just spanned to a random third disk in the local pool?Beyond that, for less important data where a single local copy is made, how can I enforce that a (second) copy is always made specifically to the CloudDrive disk, and not just spanned to a random second disk in the local pool?Might be a nice optimizer option to add to enhance tiered storage, like the SSD optimizer. Maybe SSD, HDD, Archive, Cloud, etc.So, I might be misunderstanding what you are attempting to do but from what it sounds like, I was under the impression I had done this exact thing (except 4,3,1 if you will). In drivepool, I selected the desired folders to be duplicated 4 times under file protection. Then under Balancing > File Placement I selected those folders to be placed on 3 local drives and 1 cloud drive by selecting the drives in the "file placement options" section. Now I was under the impression that this would result in one copy of the folders being placed on each of the four designated drives. After balancing, when I look at the folders it shows them being duplicated across the four drives (4,3,1) but from reading your question and the subsequent responses am I to understand that the 4 copies of the folder are not duplicated across the 4 drives? Or was it that you were attempting to specifically use a balancer to accomplish this?
Continuously Downloading from Cloud
in General
Posted
I am using Scanner (2.5.1.3062), so that may be part of the problem. The cloud drive doesn't appear in the list of drives in Scanner, but am I to understand it scans it anyways? The network activity on cloud drive was constant for 48 hours - it just kept streaming a download thread at approx. 10 Mb/s and never allowed my local drives to spin down. I had a previous build of Cloud Drive installed about a month and a half ago and didn't experience this issue. In any case I "destroyed" the drive this morning and am rebuilding it from scratch. If I experience the same issue again I will update Scanner to the beta build. Thanks.