Jump to content

IndependentEdit

Members
  • Posts

    5
  • Joined

  • Last visited

Profile Information

  • Gender
    Not Telling

IndependentEdit's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Sorry for the delay in responding. I haven't tried to restore the files, but there are definitive differences in modification dates and file sizes with some of those files. What's strange is that this only affects backups where I use the COPY function, but doesn't affect all of the backups that use the COPY function. Backips using BACKUP are all fine, and some of my COPY backups are OK too. I should point out that I am using a 10.8.5 Mac to backup a 10.6.8 server, and most of the problem backups (like the one that backs up our Calendar Server) involve programs and files that may be open at the time of the backup. But these worked before flawlessly...not sure what has changed to cause the problem now.
  2. Running Retrospect 10.5 on a Mac, backing up a Snow Leopard Server. Suddenly, some of our backup sets have been producing errors indicating File "xxxx": appears incomplete. Not all of our backups have experienced these issues. Also, running an immediate backup of the probelm backup scripts produce no errors. These scripts were running fine until this week. Nothing changed on the server or the backup before then. Any suggestions on how to resolve these issues?
  3. Upon further review, I am wondering if the issue is with this Instant Scan process. I have disabled Instant Scan on the Retrospect server side, but for whatever reason this script still uses Instant Scan. Am I missing something in how to disable it, or is this issue caused by something else?
  4. Running Retrospect 10 on a Mac...trying to backup a Snow Leopard Server. On the Server, we are running a program called Rumpus to handle our FTP site. Recently, we have started to see a ton of errors in one particular client folder within our FTP site. We get a ton of "File X can't link to File Y, error -1101 (file/directory not found)" errors, and for whatever reason multiple files are trying to be linked to the same file...like so: Using Instant Scan 
 *File "FTP/Agency/.DS_Store": can't link to "FTP/Agency/.DS_Store", error -1101 ( file/directory not found) 
 *File "FTP/Agency/.DS_Store": can't link to "FTP/Agency/.DS_Store", error -1101 ( file/directory not found)
 *File "FTP/Agency/.DS_Store": can't link to "FTP/Agency/.DS_Store", error -1101 ( file/directory not found)
 *File "FTP/Agency/.DS_Store": can't link to "FTP/Agency/.DS_Store", error -1101 ( file/directory not found)
 *File "FTP/Agency/.DS_Store": can't link to "FTP/Agency/Client/.DS_Store", error -1101 ( file/directory not found) 
 *File "FTP/Agency/.DS_Store": can't link to "FTP/Agency/Client/.DS_Store", error -1101 ( file/directory not found)
 *File "FTP/Agency/.DS_Store": can't link to "FTP/Agency/Client/Bruno.mov", error -1101 ( file/directory not found) 
 *File "FTP/Agency/.DS_Store": can't link to "FTP/Agency/Client/Bruno.mov", error -1101 ( file/directory not found)
 *File "FTP/Agency/.DS_Store": can't link to "FTP/Agency/Client/Bruno_v09.mov", error -1101 ( file/directory not found)
 *File "FTP/Agency/.DS_Store": can't link to "FTP/Agency/Client/Bruno_v09.mov", error -1101 ( file/directory not found)
 *File "FTP/Agency/.DS_Store": can't link to "FTP/Agency/Client/David.mov", error -1101 ( file/directory not found)
 *File "FTP/Agency/.DS_Store": can't link to "FTP/Agency/Client/David.mov", error -1101 ( file/directory not found) I have tried re-creating the folder structure of that Agency folder with no luck. Also, these errors only pop up during a scheduled scan in the evening. If I run an immediate backup, I never get any errors. And in both cases, the FTP server software is running. Any thoughts on what these errors mean or how to fix them?
  5. Trying to use Retrospect 10.5 to backup FileMaker Pro 13 databases. Whenever the backup script runs (backing up the database folder from the FMP server) it shows 3 execution errors, with the same three databases reported as "appearing incomplete." Yet when I then run an immediate backup using the same script, the execution completes successfully. Any ideas why? Is this an issue I need to be concerned about?
×
×
  • Create New...