Jump to content


  • Content count

  • Joined

  • Last visited

  • Days Won


Daniels last won the day on January 12 2015

Daniels had the most liked content!

Community Reputation

15 Good

About Daniels

  • Rank
    Retrospect Guru
  1. Daniels

    New Server Weekly & 3 Month Strategy?

    Since week 1's tapes got used multiple times during the week it was easier to leave them in the library than change them daily. If you are going to change tapes daily then you could use the same sequence with individual daily tapes for each day in each week.
  2. Daniels

    New Server Weekly & 3 Month Strategy?

    When using tapes I had a four week rotation: Week 1 in drive; Week 2 on site; Week 3 and 4 off site; Full/Recycle backup for each week on Friday, Incremental backups during the week, and switch tapes on Monday. In your case it would be a similar setup also including four monthly tapes that would rotate in the same fashion.
  3. Daniels

    Accessing Backup

    Do you have any programs that might be accessing the catalog file running when try to access the backup. In my case I have CrashPlan running which causes me to wait about 15 minutes until I can actually see the files. @Steve: Definitely running a copy script would effect the access.
  4. When I using tapes, I encountered this issue. If the Retrospect engine starts up without proper communication to the tape driver, it will either not see it at all or misread the tape information. The best course of action is to stop the Retrospect engine and cycle power on the tape drive. Once the tape drive finishes it start up procedure, start the Retrospect engine and it should show up correctly.
  5. Daniels

    Can I recover????

    You need to mark the 4th member as Lost and then Retrospect should no longer asked for it.
  6. Daniels

    Can I recover????

    Actually looking through the log, the issue seems to be with the following file AC015111.rdb. Try moving this file to the desktop like Lennart said and see if that fixes your issue.
  7. Daniels

    Retrospec 10 backups failing to backup to NAS

    I have experienced this issue with the NAS I am using. For me it usually happens when the NAS gets nearly full and I have to either recycle or groom my media sets. You might want to look into how you are connecting to the NAS.
  8. Anytime a disk is fragmented the performance will be reduced, so it is very likely that the fragmentation is causing the performance drop. Depending on the Server OS you might want to set up an automatic task that defrags the drive, once a week or what time frame you think is appropriate. I would also try running disk cleanup on the drive as well to eliminate files that are no longer needed such as temp files, Windows Update files, etc.
  9. You can first try using the 'config77.bak' file and see if that fixes your problem. If that does not then you will need to delete both 'config77.dat' files and create your configuration from scratch.
  10. You should be able to move Retrospect from one Mac to another. In order to keep your existing license, scripts, etc. you will need to move the Retrospect config file as well. If you copy this file you should not have to re-enter existing license number.
  11. Usually when that happens it means the engine is not running. You can check the Retrospect Preferences Panel in System Preferences to determine if the engine is running.
  12. Daniels

    Improved reporting & alerting

    Dantz no longer owns Retrospect. It is now owned by Retrospect.
  13. I am not sure as I am not that familiar with OS X as I am with Windows. You might want to try looking up how to find the network log on Google.
  14. Definitely sounds like there might have been a network glitch. Sounds like the Retrospect engine lost its connection to your network. I would check the network log to see if anything got logged.
  15. If the manual backups are running fine during the day, I would check the clients to make sure that they are not checking for software updates overnight. I have run into issues where checking for software updates has caused Retrospect not to find the client. I would also make sure the hard drives on the clients do not go to sleep as that can cause Retrospect to not find the client.