Forum Replies Created

Page 2 of 18
  • John Kaley

    February 24, 2015 at 8:23 pm in reply to: Bru W042 error

    Thanks Tim,

    smb2:// is not supported. Using OS 10.9 Mavericks on both machines. Maybe I can enable this?

    Some time tests for restoring a 1.5GB project:
    Using afp: 36 seconds (with error messages)
    Using smb: 5mins 58sec. (no error messages)

    Major time difference!

  • John Kaley

    February 24, 2015 at 4:53 pm in reply to: Bru W042 error

    I found a solution, so I’m posting it.

    Using smb:// instead of afp:// to sign on to the network eliminates the BRU error messages. The trade-off is that the restore is MUCH slower. I’m looking into why that would be.

    BTW, the two Mac are direct-connected using using the second ethernet port on each Mac.

  • John Kaley

    February 23, 2015 at 9:02 pm in reply to: Bru W042 error

    Thanks Tim.

    Yes, BRU is authenticated when started. I’m going to pursue my permissions issue first and try and solve the problem at the root.

  • John Kaley

    February 20, 2015 at 10:41 pm in reply to: Bru W042 error

    Thanks Tim.

    Regardless if “Ignore Ownership on this Volume” is checked or unchecked, BRU still returns the error message. The volume privileges are set to Read&Write.

    My main restore problem comes when I have to restore image sequences with over 1000 files; BRU aborts the restore because of the error messages. My workaround is to restore to the local computer and then transfer the files. I’d rather just transfer directly.

    I’ll have to brush up on my UNIX permissions and see if I can get it to work.

  • John Kaley

    January 23, 2015 at 4:49 pm in reply to: Huge favour to ask

    Tom,
    Just a quick note about the Adobe Media Encoder export times. Make sure you send the sequence through the Queue. At the bottom of the main tab there is an option under “Renderer.” Make sure this is set to “Mercury Playback Engine GPU Acceleration (OpenCL)”

    Those 700’s will kick in and that thing should output like bananas through a monkey.

  • John Kaley

    September 18, 2014 at 6:23 pm in reply to: BRU restore bails after 1000 error messages

    Tim,
    Thanks for the follow-up. I was able to restore all files without any more trouble.

    I’ll look into the permissions issue, however, the target drive for the restored files is set to “ignore permissions on this volume.”

    So I’m not sure why BRU was generating permission errors.

  • John Kaley

    May 15, 2014 at 2:21 pm in reply to: BRU PE 3.1 does not see my tape drive

    Todd,
    Launch BRU PE and go to Preferences/Devices and select your drive there. (Obviously, the drive must be on before you open BRU PE)

  • John Kaley

    May 8, 2014 at 7:22 pm in reply to: BRU PE will not restore

    Tim,
    The issue was resolved with flashing my Atto H680 and installing the new BRU PE vers. 3.1 which was released yesterday.

  • John Kaley

    May 8, 2014 at 12:48 am in reply to: BRU PE will not restore

    Actually tried the commands again and got this:

    [Mavericks:~] johnkaley% tapectl rewind
    [Mavericks:~] johnkaley% tapectl header | bru -gf-
    label: Archive of 2006
    created: Sat Sep 29 13:09:36 2012
    artime: 1348938576
    archive_id: 50672b5028ae
    volume: 1
    writes: 0
    release: 18.0
    variant: 0
    bufsize: 2097152
    msize: 0
    msize_blks: 0
    serial_number: 4000-5435
    device: ntape0
    user: root
    group: wheel
    system: Darwin IntelDua 9.8.0 Darwin K i386
    bru: mac-osx
    command_line: /bin/bru -c -m -vvvvvvvvv -j -O -A -QB -f ntape0 -L Archive of 2006 -QX –

  • John Kaley

    May 8, 2014 at 12:36 am in reply to: BRU PE will not restore

    Thanks Tim
    I’ll open a ticket.

    I get 11.3 for the first command and for the second command:
    bru: [W039] warning – info block checksum error
    bru: [W069] warning – may have to use -F option to read archive

    All of this works fine with vers 3.0.0. under OS 10.5.8

Page 2 of 18

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy