I am testing Drivepool before purchase and having questions:
1. I wonder if there is an issue with sub pool. I had created a sub pool in a master pool. When I added a disk to the sub pool the poolpart folder for the sub pool was immediately created. However not the poolpart folder for the master pool. So from that disk I had no option to move files directly into the master pool. I had to move files into the subpool first and then from there in to the master pool poolpart folder. Only after then the correct nested poolpart folder got created on the disk. This was contrary to when I added the sub pool to the parent pool initially. Then all required nested poolpart folders got immediately created. I think when I add a disk, all correct nested structures should be creaded immediately.
2. Could someone confirm how Drivepool acts with big files. Let's say I have dynamic virtual disks in the pool that expand over size. Now when the capacity of an underlying disk is reached and a virtual disk file keeps expanding, what will Drivepool do? Will the virtual disk file be able to expand further and Drivepool will span the file over additional disks that are in the pool? Or will the complete file be moved to another disk within the pool that has enough capacity?
Question
Ant
Hi guys!
I am testing Drivepool before purchase and having questions:
1. I wonder if there is an issue with sub pool. I had created a sub pool in a master pool. When I added a disk to the sub pool the poolpart folder for the sub pool was immediately created. However not the poolpart folder for the master pool. So from that disk I had no option to move files directly into the master pool. I had to move files into the subpool first and then from there in to the master pool poolpart folder. Only after then the correct nested poolpart folder got created on the disk. This was contrary to when I added the sub pool to the parent pool initially. Then all required nested poolpart folders got immediately created. I think when I add a disk, all correct nested structures should be creaded immediately.
2. Could someone confirm how Drivepool acts with big files. Let's say I have dynamic virtual disks in the pool that expand over size. Now when the capacity of an underlying disk is reached and a virtual disk file keeps expanding, what will Drivepool do? Will the virtual disk file be able to expand further and Drivepool will span the file over additional disks that are in the pool? Or will the complete file be moved to another disk within the pool that has enough capacity?
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.