On Wed, 26 May 2010, John Stoffel wrote: > Unless your backup software and your NAS box talk very well together, > you're going to be hosed on restores.
Thanks, John. That's a concern of mine as well. > Now, I will admit this was all a couple of years ago, and it may have > been fixed or improved since then, but think of this situation and ask > Acopia how it is handled. Their answer will be illuminating (and I'd > love to hear it if you'll share it!). We will have them coming in shortly, so hopefully I can get some current answers. It may depend on which features and what architecture we go with. If it's possible to use the box as simply a virtualizer, where the data is still stored and controlled by the filers (NetApps in our case as well), then we can just restore to the original location. If the Acopia owns the filesystem and is moving files around on its own (like some policy-based DLM systems do), then we have bigger worries about the restores. If we have the option, then at least we get to decide for ourselves whether to complicate our backups. :) At the moment what we really want is simply a box that sits between the filers and the users and when the user wants to connect to a share, the box in the middle directs them to the right filer. As long as we can define where to point the user, we can migrate the data around without disrupting the users. Once you move to a true global namespace, the backup/restore issues mount up quickly. -Adam _______________________________________________ Discuss mailing list Discuss@lopsa.org http://lopsa.org/cgi-bin/mailman/listinfo/discuss This list provided by the League of Professional System Administrators http://lopsa.org/