Hey Guys Previously I had set my Cloud Drive to 16TB and CHKDSK took days to complete. My current drive, is the max "default" (not manually entered) value in the GUI of 10TB. I want to prevent a repeat of losing all my data, so I'm being extra careful this time. I have upload verification turned on, and have the drive set to 10TB in-case I have to scan it one day.
My question is going forward, what practices would you guys recommend for expansion and redundancy? I have a license to DrivePool also, but was wondering how I would go about optimizing my library?
For example, once this drive fills up, should I "Resize" the drive to a larger value, or simply create another Virtual Drive and Pool them together under Drive-Pool?
If pooling together Cloud Drives is possible, then how does the distribution of chunks work?
Are some chunks written to VHDD 1, and VHDD2, and if so how does that maintain data integrity if some chunks are in one Drive, and some are in another?
If the above is not the case, are files assigned chunks and then a drive and balanced in the CloudDrive DrivePool, for example File1.AVI 6GBs, File2.AVI 3GBs, is File 1 broken into chunks then assigned to VHDD1, and FIle2 broken into chunks and assigned to VHDD2, or is it FIle 1 has 50% of its chunks in VHDD1 and 50% of its chunks in VHDD2?
Does pooling together CloudDrives Increase/Decrease ---> Download/Upload/IO performance?
Do they all contribute to the same upload cap?
After all these questions, is there a practical way of creating a virtual pool/raid, that serves as an instant "backup" to your main CloudDrive/CloudDrivePool?
Question
Bowsa
Hey Guys Previously I had set my Cloud Drive to 16TB and CHKDSK took days to complete. My current drive, is the max "default" (not manually entered) value in the GUI of 10TB. I want to prevent a repeat of losing all my data, so I'm being extra careful this time. I have upload verification turned on, and have the drive set to 10TB in-case I have to scan it one day.
My question is going forward, what practices would you guys recommend for expansion and redundancy? I have a license to DrivePool also, but was wondering how I would go about optimizing my library?
For example, once this drive fills up, should I "Resize" the drive to a larger value, or simply create another Virtual Drive and Pool them together under Drive-Pool?
If pooling together Cloud Drives is possible, then how does the distribution of chunks work?
Are some chunks written to VHDD 1, and VHDD2, and if so how does that maintain data integrity if some chunks are in one Drive, and some are in another?
If the above is not the case, are files assigned chunks and then a drive and balanced in the CloudDrive DrivePool, for example File1.AVI 6GBs, File2.AVI 3GBs, is File 1 broken into chunks then assigned to VHDD1, and FIle2 broken into chunks and assigned to VHDD2, or is it FIle 1 has 50% of its chunks in VHDD1 and 50% of its chunks in VHDD2?
Does pooling together CloudDrives Increase/Decrease ---> Download/Upload/IO performance?
Do they all contribute to the same upload cap?
After all these questions, is there a practical way of creating a virtual pool/raid, that serves as an instant "backup" to your main CloudDrive/CloudDrivePool?
Link to comment
Share on other sites
4 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.