Bacula-users

Re: [Bacula-users] Cross-architecture tape backward compatabiltiy

2008-06-23 07:00:23
Subject: Re: [Bacula-users] Cross-architecture tape backward compatabiltiy
From: Frank Sweetser <fs AT WPI DOT EDU>
To: James Cort <james.cort AT u4eatech DOT com>
Date: Mon, 23 Jun 2008 07:00:01 -0400
James Cort wrote:
> Dear All,
> 
> I'm looking at rebuilding the server that (amongst other things) is my 
> SD/Director using an amd64 version of Linux (it's currently running an 
> x86 version).
> 
> Will the minor architecture change affect my ability to read tapes 
> created prior to rebuilding the server?  I know the goal is to maintain 
> compatability of the on-tape format between versions, but I don't know 
> if that includes endian-ness and C data type independence.

According to the bacula developer's manual at

http://bacula.org/en/developers/Storage_Media_Output_Format.html#SECTION000115000000000000000

"All Block Headers, Record Headers, and Label Records are written using
Bacula's serialization routines. These routines guarantee that the data is
written to the output volume in a machine independent format."

So you should be pretty safe.  Odds are, if you do find any problems due to
the 32 to 64 change, it's something that should be filed as a bug report.

-- 
Frank Sweetser fs at wpi.edu  |  For every problem, there is a solution that
WPI Senior Network Engineer   |  is simple, elegant, and wrong. - HL Mencken
    GPG fingerprint = 6174 1257 129E 0D21 D8D4  E8A3 8E39 29E3 E2E8 8CEC

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users

<Prev in Thread] Current Thread [Next in Thread>