Running with .dat files on different drives

[ConvertFromOldNGs]

by Anonymous >> Thu, 11 Mar 2004 2:08:13 GMT

I queried this via Parsys but wasn't convinced by the reply so a "world wide" request. I have an existing system where disk is getting tight (like I can't upgrade to Jade 6 because not enough workspace) and I have heaps of disk on another set of Raid drives. I don't want to "stripe" them. I want to move an 18gig .dat file to another drive. I don't want to use the map "hard coded drive" option because that applies to all environments and might be difficult to migrate. I thought "remap" might work but don't know how to achieve a tidy change to the production environment. I thought this ability to spread the database around was an inherent feature, am I wrong? Any clues other than go buy more disk? Thanks.

[ConvertFromOldNGs]

by Davey >> Thu, 11 Mar 2004 6:59:37 GMT

Disk is cheap. Personally I'd go with putting more disk into your raid array and move the whole system over rather than just the 1 mapfile.

It's far easier to manage from an operational perspective if all your mapfiles are in the same directory and with an appropriately populated raid array you're getting the benefit of multiple heads/spindles for your reads and writes anyway - not to mention the benefits of redundancy should you lose a drive from your array. Much easier to just replace a single disk than forcing a test of your recovery procedures. Not that I'm advocating anything other than regular testing of your recovery procedures of course...

[ConvertFromOldNGs]

by Davey >> Thu, 11 Mar 2004 7:09:32 GMT

I forgot to say that if you really don't mind the operational overheads of having mapfiles on different drives, then remapping would probably be better than using "hard coded drive option" as you said. A quick read of the doco on this feature suggests it would be easy enough to implement in the way you want without any problems achieving this in a "tidy change to the production environment" as you said.