Further to our server woes (see other thread) last week we were experiencing some painfully erratic behaviour with our NAS - with intermittent (sometimes non-existent) access making it impossible to get to our libraries.
We ARE (not were) migrating the data on (one) NAS to (two) SAN arrays, but that's a "size&speed" upgrade - although (despite my protests) we're doing the stupid thing of moving it all - rather than sorting it all out then moving it... so we'll be replicating all the years of accumalted disorder and clutter.... but that's not the problem.
The problem is, with Revit (and a lot of other applications) setup to "look" at folder locations - when the locations become inaccesbible, we've found Revit is brought to a grinding halt - to the point where even working locally still is practically impossible.
Now I know if something is not there, it's always difficult for a computer to know that until you ask to look for it... the lag (say through Windows) is never much more than a few seconds before you get the "Connection can not be established" or some similar warning dialog. Revit doesn't tell us this though - and seems to get caught in a never-ending loop.
But clearly, it's very convenient to have library locations defined (in a program like Revit). The re-pathing to new volumes when data gets moved (as we are doing) is a necessary evil - and takes less than a minute per computer. But how can we keep Revit from "looking" to somewhere that isn't there (when things do go bad?).
Is there a "safe mode" ? Are there ways to "fake" the path so that Revit always see's something - even if it's not the right thing?
We ARE (not were) migrating the data on (one) NAS to (two) SAN arrays, but that's a "size&speed" upgrade - although (despite my protests) we're doing the stupid thing of moving it all - rather than sorting it all out then moving it... so we'll be replicating all the years of accumalted disorder and clutter.... but that's not the problem.
The problem is, with Revit (and a lot of other applications) setup to "look" at folder locations - when the locations become inaccesbible, we've found Revit is brought to a grinding halt - to the point where even working locally still is practically impossible.
Now I know if something is not there, it's always difficult for a computer to know that until you ask to look for it... the lag (say through Windows) is never much more than a few seconds before you get the "Connection can not be established" or some similar warning dialog. Revit doesn't tell us this though - and seems to get caught in a never-ending loop.
But clearly, it's very convenient to have library locations defined (in a program like Revit). The re-pathing to new volumes when data gets moved (as we are doing) is a necessary evil - and takes less than a minute per computer. But how can we keep Revit from "looking" to somewhere that isn't there (when things do go bad?).
Is there a "safe mode" ? Are there ways to "fake" the path so that Revit always see's something - even if it's not the right thing?
Comment