Jump to content

lazers

Members
  • Posts

    7
  • Joined

  • Last visited

Reputation Activity

  1. Like
    lazers got a reaction from Ginoliggime in Cloud Drive in pool turned RAW   
    Yesterday I realized one of my folders on my DrivePool wasn't working, and when I opened the GUI I saw it said that one disk was missing. The missing disk is a Cloud Drive (Google Drive).
    I've tried rebooting, and detaching the drive, it re-attaches fine, but DrivePool still says the disk is missing. Disk Managment shows the Cloud Drive as RAW.
    Soo..
     
    Is there any way I can fix this? Logging in to Google Drive it seems that all data is still there. Could I for example make a new Cloud Drive, move the data to the new disk (on Google Drive web interface), add that new disk to the pool and cross my fingers for it to work? The cloud drive is encrypted, so maybe use the same encryption key on the new drive as on the old one?
     
    Most of what's on the cloud is not duplicated, so any suggestion is welcome..
  2. Like
    lazers reacted to steffenmand in Cloud Drive in pool turned RAW   
    They have a bug currently causing this. Just be patient and it will get fixed!
  3. Like
    lazers got a reaction from Ginoliggime in Keep new data on local drives and move old data to cloud   
    Hello!
     
    I'm trying to figure out how to best set up my DrivePool. My pool consists of:
    Two local drives A and B (2 TB each) Two cloud drives C and D What I would like is for new data to be stored on A and B, and when they start to be full I'd like _old_ data to be moved from A and B to C. That way I have the newest data on my local drives, and older data is stored in the cloud.

    Is this possible, and if so how?

    What I have done:
    I've played with the SSD optimizer, and marked the two local drives as SSD. I've tried to play with the balancing triggers, but I'm unsure as to how I should adjust the balancing triggers to achieve my goal and I still have data being moved from local drives to cloud drive. I reckon I could set the balancing trigger to start if for example at least 1,5 TB needs to be moved, but then it would move _all_ off the data, correct? I just want some of the oldest data moved.
×
×
  • Create New...