> > A plain copy may fail.   Actually a cross platform migration can be 
safer
> > than a mere copy of files if the media db is exported/imported using 
the
> > right tools.  However that procedure is not officially supported 
(although
> > that wouldn't matter here).
> 
> A plain copy will fail if the source and the target have different 
> byteordering. Otherwise it will work.
> 
> > > Just follow the procedure outlined in a previous answer. Except from 
the
> > > fact that you can copy mm and index too and save the trouble of
> > > recovering the indexes from tape. And don't forget to bring down
> > > networker on the source before you copy :-)
> > 
> > The best method is the DR. It is clean and well organized. It is there 
for
> > a good reason. running mmrecover+ nsrck  following the right procedure 
is
> > not trouble. It avoids getting into it.
> 
> Yes. This is the ONLY method that takes care of byte ordering. But very 
often 
> we are talking x86 to x86 migration.

So .. a migration from x86 to x64 would be a different byte-ordering? 
(specific example, from my environment: migrating from Win2003 32bit to 
Win2008 64bit, keeping same hostname and same IP)

So, in the case above, a copy will (might?) fail, but a mmrecov and nsrck 
-L7 should work, to retain history?

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER