Jump to content
Division-M Community

KaySee

Members
  • Content Count

    4
  • Joined

  • Last visited

  1. Hi Obsidience, Thanks for the reply, I missed the thing about needing 2 parity disks for 5 data disks. I couldn't run to another disk right now, I suppose I could remove a disk from the pooled drive for now but the pool is quite full, or chance single parity until I can run to an additional drive, the facts do say its a rule of thumb. I note that you put content files on the parity drives is this normal? Does the SSD cache make a lot of difference to performance? KaySee.
  2. Hi, Is anyone using SnapRaid with Drive Bender? What is the recommended way to configure a drive pool to use SnapRaid? I have never used SnapRaid but it looks like it needs direct access to a the files on each disk, is this correct? If the above is true, should all the pooled drives be assigned a drive letter? If so what are the issues relating to Drive Bender? Would it be better to assign a mount point on the C: drive for each pooled drive? e.g. c:\Mount\DB1, C:\Mount\DB2 etc What about the 'snapraid.content' files, can they be put in the root of the pool drives, e.g. c:\Mount\DB1\snapraid.content, c:\Mount\DB2\snapraid.content etc, or should it go on the pooled drive itself? e.g. if your pool is mounted to D:, d:\snapraid.content. Would having a content file on the pool itself cause some kind of loop condition? This is the configuration I am thinking of using, My parity volume is assigned the drive letter Z:, My drive pool is assigned the drive letter D:, each drive in the pool is mounted to an empty folder in C:\Mount. parity Z:\snapraid.parity content C:\SnapRaid\snapraid.content content D:\SnapRaid\snapraid.content disk d1 C:\Mount\DB1\{3C023BA8-FEB5-49A9-9795-EF8A62107750} disk d2 C:\Mount\DB2\{3C023BA8-FEB5-49A9-9795-EF8A62107750} disk d3 C:\Mount\DB3\{3C023BA8-FEB5-49A9-9795-EF8A62107750} disk d4 C:\Mount\DB4\{3C023BA8-FEB5-49A9-9795-EF8A62107750} disk d5 C:\Mount\DB5\{3C023BA8-FEB5-49A9-9795-EF8A62107750} exclude Thumbs.db exclude \$RECYCLE.BIN exclude \System Volume Information Examples of other setups would be nice.
  3. Hi, Is anyone using SnapRaid with Drive Bender? What is the recommended way to configure a drive pool to use SnapRaid? I have never used SnapRaid but it looks like it needs direct access to a the files on each disk, is this correct? If the above is true, should all the pooled drives be assigned a drive letter? If so what are the issues relating to Drive Bender? Would it be better to assign a mount point on the C: drive for each pooled drive? e.g. c:\Mount\DB1, C:\Mount\DB2 etc What about the 'snapraid.content' files, can they be put in the root of the pool drives, e.g. c:\Mount\DB1\snapraid.content, c:\Mount\DB2\snapraid.content etc, or should it go on the pooled drive itself? e.g. if your pool is mounted to D:, d:\snapraid.content. Would having a content file on the pool itself cause some kind of loop condition? This is the configuration I am thinking of using, My parity volume is assigned the drive letter Z:, My drive pool is assigned the drive letter D:, each drive in the pool is mounted to an empty folder in C:\Mount. parity Z:\snapraid.parity content C:\SnapRaid\snapraid.content content D:\SnapRaid\snapraid.content disk d1 C:\Mount\DB1\{3C023BA8-FEB5-49A9-9795-EF8A62107750} disk d2 C:\Mount\DB2\{3C023BA8-FEB5-49A9-9795-EF8A62107750} disk d3 C:\Mount\DB3\{3C023BA8-FEB5-49A9-9795-EF8A62107750} disk d4 C:\Mount\DB4\{3C023BA8-FEB5-49A9-9795-EF8A62107750} disk d5 C:\Mount\DB5\{3C023BA8-FEB5-49A9-9795-EF8A62107750} exclude Thumbs.db exclude \$RECYCLE.BIN exclude \System Volume Information Examples of other setups would be nice.
×
×
  • Create New...