Jump to content
Division-M Community


  • Content Count

  • Joined

  • Last visited

  • Days Won

  1. If Division-M support reads this please note that I have also raised this as support request #8829. I am posting here as well in case I get a quicker response. I had to restore my server from an old backup which had a different drive and pool state than the 'current' config. Thus although the restore seems to have got the OS working again (the problem was nothing to do with DB), I am left with my pool in a bad state and need advice on the best way to get it back to what it should be. I later deleted pool 2 and mount T:\ and added 3 more drives, so a total of 4 new drives were added to pool 1 with mount S:\. So the file duplication has spread over 7 drives. However whilst doing this upgrade I found that one of the original drives had early signs of failure so I swapped it with my backup drive which is in an external dock and currently offline. Now that I have had to restore from the previous configuration, DB is reporting my system across the 8 drives as follows: Backup drive: In pool 1 but offline. This is the backup drive and doesn't contain pool data so I don't want it in the pool 1: Not in either pool but needs to be in pool 1 2: In pool 1 and accessible to mount S 3: In pool 1 and accessible to mount S 4: Not in either pool but needs to be in pool 1 5: Not in either pool but needs to be in pool 1 6: Not in either pool but needs to be in pool 1 7: In pool 2 but needs to be in pool 1 (I don't need pool 2 any more) As expected pool 1 is in fault tolerant mode and data is missing from S:\ Pool 2 is OK but T:\ has no data, although there is valid data on drive 7. I guess this must be because it is not the same drive that I had been using before. I am unsure if I should do a repair operation on pool 1, or do a restore pool instead. Or can I simply merge the drives into pool 1 (after assigning drive letters)? The key point is that all 7 drives still contain the correct data that allow them to act together in the same pool with mount point S:\. So if I could achieve this without first having to do any repair or restore operation, then in theory the pool could just start working again as before. Is this possible?
  2. I have been happily using DB for quite a while now but have not had to do anything with it since I first configured it. So unfortunately I can't remember anything about it! Well now I need to because I want to add some more drives to my server. Since this will be one level above totally simple I thought I'd ask for some advice. The server has 8 sata ports and I'm using 5. But 4 are sata2 and 4 are sata3. I used the sata3 ports for the system drive and the 3 2TB drives which are in the single pool in DB. So my new 3 drives will have to be connected to sata2 ports. Rather than just add these drives to the existing pool, I thought it might make sense to have 2 pools, one using the drives connected to sata2 ports and the other with the ones connected to sata3 ports. To further complicate this, it appears that the sata3 drives available now are faster (on paper?) that the sata3 drives I already have. So my requirement is: Move the existing 3 drives from the sata3 ports to the sata2 ports Add 3 new drives connected to the now vacant sata3 ports Create a new pool with the 3 new drives Move certain data (e.g. media files which will be streamed) from the existing pool to the new pool How should I go about this?
  3. Please can I confirm, this feature will fix the problem I am having, getting "The volume shadow copy operation failed with error 0x80042306" when I try to back up from the pool (as per beta forum post http://www.drivebender.com/forum/post/1530195)?
  • Create New...