Menu

Sync to a remote (network) disk won't work

Help
2003-06-03
2003-12-16
  • Johan Arvidsson

    Johan Arvidsson - 2003-06-03

    I can't sync to a folder on a network disk. Is mounted with AFP. I've tried to check the Remote Folder checkbox when creating a backup.

    I have also encountered a problem that the files copied were invisible, and thats on my local disk.

    I use 10.2.6

     
    • Anonymous

      Anonymous - 2003-06-09

      I am having the same issue.  I'm running 10.2.6 on the client and server.  It backs up fine to a local drive (external FireWire), but the network drive isn't working properly

      Here is a section of the terminal with the repeating error:
      +f /Users/evangesl/Desktop/Amy/Career Center/crc 6 27 02 Folder/Instructions.txt
      /Users/evangesl/Desktop/Amy/Career Center/crc 6 27 02 Folder/Instructions.txt -> /Volumes/Users/evangesl/Backup/Desktop/Amy/Career Center/crc 6 27 02 Folder/Instructions.txt : err=-43,file=filecopy.c,line=63 at /usr/local/bin/psync line 172.

       
    • Micah Katke

      Micah Katke - 2003-12-14

      Same problem different reason. I am working with 2 OS X 10.3.1 servers (1 Open Directory Server and 1 Open Directory Replica so their authentication info is identical). I mount all the network drives to the replica from the master using an admin account (same account runs psync and admin account is member of ALL network groups). As far as I can tell, network mounts that give at least read access to everybody work great, however any mounts that deny read access to everybody (even though I have read access by group permissions) will not sync. Here's my log (the first sync is a "at least read-only for everybody" mount while the second is a "no permissions for everybody but read and write for an appropriate group" mount.):

      "Backup begun Sat Dec 13 20:02:00 2003
      Scanning Destination Directory /Volumes/CastleShareDrive/Cast         0:...............
      1801 items found.
      Scanning Source Item /Volumes/Public ...

               0:.
      1 items found.
             0 items to delete,
             0 items unchanged,
             0 items to copy.
      deleting items ...
      copying items ...
      fixing directory attributes ...
      00770,admin,cstaff /Volumes/CastleShareDrive/CastleShare
      Using /Volumes/CastleShareDrive/CastleShare/.psync.db to store extra attributes.
      1 items stored.
      Backup completed: Sat Dec 13 20:02:02 2003"

      running the bum mount manually yields the following result:

      "Last login: Sat Dec 13 19:26:18 on ttyp1
      sudo /usr/bin/runpsync 0 -d -r '/Volumes/CastleShaWelcome to Darwin!
      CastleServer02:~ admin$ sudo /usr/bin/runpsync 0 -d -r '/Volumes/CastleShare' '/Volumes/CastleShareDrive/CastleShare'
      Password:
      Backup begun Sat Dec 13 20:02:35 2003
      Scanning Destination Directory /Volumes/CastleShareDrive/CastleShare ...

               0:.
      1 items found.
      Scanning Source Item /Volumes/CastleShare ...

      /Volumes/CastleShare:Permission denied at /usr/bin/psync line 288.
               0:.
      1 items found.
             0 items to delete,
             0 items unchanged,
             0 items to copy.
      deleting items ...
      copying items ...
      fixing directory attributes ...
      00770,admin,cstaff /Volumes/CastleShareDrive/CastleShare
      Using /Volumes/CastleShareDrive/CastleShare/.psync.db to store extra attributes.
      1 items stored.
      Backup completed: Sat Dec 13 20:02:35 2003CastleServer02:~ admin$ "

      I'm at a loss here.

       
    • Micah Katke

      Micah Katke - 2003-12-16

      Alright I think I figured it out. PsyncX throws a "sudo" in from of the psync command so the whole command looks like "sudo psync -d -r /source /destination". That sudo makes psync run like system root, not admin or the current user, so if you are trying to sync to network drives then the system root needs to have permission or more accurately my network psync isn't working because the local system root doesn't have read permissions on the drive in question (this also explains why the psync did work when the drive in question had a least the read only bit set for everybody). What's the solution? Run psync as a user that has at least local read/write and remote read access w/o putting a sudo at the beginning of the command. So now the question is how do you edit the PsyncX to do this and if you did would you need to recompile and reinstall? I will start a new thread on this issue.

       

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.