INTERNET Internet BACKUP (FTP) error 225 (FTP: no write privileges, bad name, or disk full)

[warwickT]

All, like many I have been unable to get RETROSPECT V5.02 to backup to an FTP site because I get the usual ERROR 225 as follows:

 

- 13/07/2003 9:37:12: Copying Virtual PC List on Macintosh HD…

Device trouble: “my.daily.backup”, error 225 (FTP: no write privileges, bad name, or disk full).

13/07/2003 9:37:19: Execution incomplete.

 

Well. the target disk is NOT FULL, I have RIGHT READ and every priv, the name I usd is OK.. so what could it be????

 

I have found a work around but first let me tell you my scenario.

 

OSX10.2.6:

 

- Backing up to office G4 on local LAN via 100Baset or AIRPORT or GbE networks (yes access to all three networks) using a script called “my.daily.backup”.

- the remote G4 has many disk file systems

- target for BACKUP is a DDM (volume) mounted on the remote G4 Dual system with a volume serial (label name) of "storage_backup". Volume is also available to all via AFP

- want to use FTP so backup/restore can be done when travelling (say from hotel broadband or another LAN) via VPN and usual firewall.

- the file path for the FTP INTERNET directory is this /volumes/storage_backup.

- the user I am using has ADMIN account status on the remote machine. And YES it has full read right update privileges. I test this with a usual FTP access and a MKDIR and put and an rm etc.. so the account I am using is fine.

- the target VOLUME ("storage_backup") I will use has 90GB left on it from the 120GB. So it has plenty of space for a 1GB backup.

- I have contained the backups in a folder called "TiPB-daily-backups-folder" thus the full path names is /volumes/storage_backup/TiPB-daily-backups-folder. This is the final directory (the target) of the backups.

- ip address for the subnet on the GbE is 10.20.1.9. (accessed from outside our office as something different ofcourse).

- ONLY this network connection is used for RETROSPECT backups. YEs there is a problem for RETROSPECT where you will get the 225 error when MORE than one network path is enabled..... silly eh?. In this case I will use ONLY ETHERNET (it is GbE for a test).

- so the set up for the INTERNET backup set "TiPB-daily-backups" I want to use with retrospect settings as:

 

account: me

pwd: mypwd

ftp address: 10.20.1.9

directory: /volumes/storage_backup/TiPB-daily-backups-folder

 

WHAT HAPPENS when I get the ERROR 225:

 

- I start the backup and it connects instantly.

- a folder (directory) called "TiPB-daily-backups/DATA 0" is created in the directory "/volumes/storage_backup/TiPB-daily-backups-folder".

- retrospect starts scanning the first SOURCE folder and then after 2-3 seconds I get the error 225 msg "Device trouble: “my.daily.backup”, error 225 (FTP: no write privileges, bad name, or disk full)

 

After much frustration and some testing I notices that the OWNERSHIP of the folder "/volumes/storage_backup/TiPB-daily-backups-folder/TiPB-daily-backups" had changed to SYSTEM and was no longer me (cmd-I). I logged in to the G4 via SSH and confirmed this. I tried this quite a few times and it seems to be the case. The VOLUME privileges were available to all read/write but his path was changed during the initial backup.

 

WORKAROUND - REMEDY:

- I logged in as the root account for the G4 did a CHOWN myname "TiPB-daily-backups". I also insured that the CHMOD privs were ok for me.

 

I restarted the BACKUP script called “my.daily.backup” and the backup completed fine!

 

SUMMARY:

- I don't understand UNIX well enough to see why on earth the RETROSPECT.app changed the target backup folder privileges to SYSTEM and not make or those of my colleagues.

 

- as we don't hand out root password, this procedure is unreliable and after a finite number of requests all the backup seem to go ok to this directory for those that need it.

- it seems also clear to me that many of the suggestions on the net for this issue of not right.. same as my one as they offer no explanation to why this occurs. Except for the MULTIPLE active network paths (ie.e modem, airport, ethernet active), this is the one is a frustrating problem.

 

any feed back would be appreciated.