• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: [OT] FrontBase problem when copying databases
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [OT] FrontBase problem when copying databases


  • Subject: Re: [OT] FrontBase problem when copying databases
  • From: Hugi Thordarson <email@hidden>
  • Date: Sat, 9 Aug 2008 20:28:14 +0000

Just a note: If you like your backups to be permanent, you might want to consider using "write all output" for all your FB backups rather than "write data". As Dave, in his widely acknowledged infinite wisdom, points out, write data has endian issues - and it also has version issues. For example, I recently had to dig out a G4 machine and install FrontBase 3 to restore an old backup created using "write data" (and even though using legacy hardware to restore old backups is fun in a nerdish kind of way, I'm too lazy to do it again, so I switched :-).

- hugi




On 9.8.2008, at 15:13, Florijan Stamenkovic wrote:

Yup, testing seems to confirm it, it is an endian issue.

Thanks David for the pointer,

F

On Aug 09, 2008, at 09:58, David Holt wrote:

Hi Flor,

This may be too obvious, but are you copying from PowerPC to Intel by any chance? If so, you need to do the backup as a "WRITE ALL OUTPUT ..." and restore on the other machine by running the script. Because of endian issues you cannot go between architectures using backup.

David

On 9-Aug-08, at 6:46 AM, Florijan Stamenkovic wrote:

Hi all,


I apologize for the off topic post, but neither google nor the FrontBase mailing list helped with this, so I figured I'd ask here, maybe somebody will be able to advise.


I am trying to port database from one computer to another. I am trying to do that by exporting backups, copying the backup to another computer, and restoring from that computer. However, I get a message:

Wrong magic number - not a backup file
Failed to restore...

Could someone point out to what "magic number" refers to, and how to work around this?

Or, if there is a better way to copy databases to and fro? An ASCII SQL dump is a pain, for multiple reasons.

Thanks,
Flor
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden

_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
  • Follow-Ups:
    • Re: [OT] FrontBase problem when copying databases
      • From: Florijan Stamenkovic <email@hidden>
References: 
 >[OT] FrontBase problem when copying databases (From: Florijan Stamenkovic <email@hidden>)
 >Re: [OT] FrontBase problem when copying databases (From: Florijan Stamenkovic <email@hidden>)

  • Prev by Date: Re: Inheritance and relationships
  • Next by Date: ajax and webobjects
  • Previous by thread: Re: [OT] FrontBase problem when copying databases
  • Next by thread: Re: [OT] FrontBase problem when copying databases
  • Index(es):
    • Date
    • Thread