Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


Everything posted by abb668b8-e67d-45d2-8fe4-b2a87dc2831e

  1. Here are some suggestions: Don't use Recycle Backup except for emergencies Don's suggestion is the easiest to implement, costs no money and will speed up your backups. Recycle backups will take a long time. The main advantage of any backup solution is to backup only changed files. Instead, set the grooming option. I've set my grooming option to keep 1 copy for all my backups because I don't have the space for keeping backup changes and it's essentially the same as a recycle backup. My primary reason for backup is to restore in case of failure and not to store a history of changes. The only time I use a recycle backup is when there is a problem with Retrospect backing up to a media set and I need to start over from scratch. Try using Retrospect Instant Scan How much time on the backup is spent on scanning the source for changes? Are you using Retrospect Instant Scan on your sources? Instant Scan will monitor the backup source for file changes. When it's time to be backed up Retrospect queries the client for changes that need to be backed up. It's adds some processing overhead on the source computer when the computer is not being backed up but should start a backup sooner than scanning a source disk for changes at the time of backup. Create separate Media Set for each backup Source Having a different backup Media Set for each backup source will allow Retrospect to use backup threads. It will cut down on the "scanning for changes" time because all the backups will be scanning for changes on the clients at the same time instead of: 1st backup scan for changes, backup, 2nd backup scan for changes, backup, etc. Assuming this is the setup you have now: You've created 1 media set for the backup destination and set 6 sources to backup to that set. When it's time to backup, only one source will run at a time. Instead: on your backup destination create a media set for each source located on the backup destination drive. When it's time to backup, Retrospect will start all backups at the same time. Increase Backup Destination Storage Speed Increasing the backup destination storage speed will increase the backup speed. It's probably what is slowing you down if you are backing up to a single FireWire drive instead of a Firewire Raid. FireWire 800 tops out at around a theoretical 800 Mbps. Your speed at 580 Mbps is about what FireWire can handle, so even having a FireWire raid wouldn't make much of an improvement. Where are you seeing your backup speed? Is it 580 Mbps or 580 MB/m. The Retrospect console shows MB/m. 580 Mbps would be really fast on a single FireWire 800 drive. You're probably getting 10 Mbps. The source read speed will also limit the backup. If you are backing up computers whose top read speed is 168 Mbps, and your backup destination can handle 800 Mbps, then you aren't utilizing all the bandwidth of the backup source. This is another reason to create multiple media sets in Retrospect so you can have more than 1 backup happening at the same time to saturate your backup destination bandwidth. If the Mac Mini has a Thunderbolt connection that would give you the top speed. 10 Gbps. However, the drive connected to it needs to be able to read and write that fast. Leading back to getting a raid. OWC makes a reasonably priced Thunderbolt raid: https://eshop.macsales.com/shop/Thunderbolt/External-Drive/OWC/ThunderBay-4 If the mini doesn't have Thunderbolt you could try a FW 800 raid: https://eshop.macsales.com/shop/External-Drive/OWC/Elite-Pro-Dual https://eshop.macsales.com/shop/hard-drives/RAID/Desktop/ The more drives you have in a raid the faster the read / write speeds. Thunderbolt is the way to go if you have it. You can use a disk speed test tool to determine how fast your backup destination disk is. Blackmagic makes a good one that is free: https://www.lifewire.com/blackmagic-disk-speed-test-4065592 Even though you are using firewire 800 you are probably not saturating the firewire 800 bandwidth and are limited by your disk speed.
  2. I've been confused by this as well. There are two types of servers, Retrospect Server which is where the backup server software is running, and a hardware server. Backing up a hardware server counts in Retrospect licensing as backing up a server not a client even though it is a Retrospect client. In order to back up servers you'll need a multi-server license. That's my understanding.
  3. I'll check that out. Thanks for the tip. The email stopped working for me. I set up a free google account and it's able to send from the google account. Probably the easiest workaround.
  4. I found it. View menu, Log. I do see the full log messages there. Great idea. Thank you.
  5. Once a day I open the Retrospect client to see if any backups failed. When they do fail, I click on Activities - Past - Select the failed backup, and when I click on the Log button, the reason for failing is: 'No Log Available'. If I run the backup script again, there will be error messages. Seems to be a problem with reporting the reason for backup failures if the client is shut down.
  6. I'll give that a shot. Although it doesn't have anything to do with my email settings. There's quite a few bugs in Retrospect... email is one of them. See this post where I successfully tested getting to my email server using the terminal and the same email settings in Retrospect. http://forums.retrospect.com/index.php?/topic/150965-unable-to-send-email-from-retrospect/ Also, once this happens I can't just stop the retrospect engine and start it. I have to reboot the server. %
  7. After Force Quitting the process in activity monitor, the Retrospect in Mac System Preferences showed that the engine had stopped. I started the Retrospect engine again and the Running Queue is cleared.
  8. I just logged into the server running Retrospect server. Tried to stop the engine by going into system preferences, and clicking on stop. Nothing happened. Looked in activity monitor, and Retrospect is running 100% of one of the CPU's.
  9. This happened again today. Last Friday I rebooted the server in order to clear the Queue. Came in today and all the jobs are stalled in the Running queue with an Excecution completed successfully status. I did leave the Retrospect client running on my machine over the weekend? I'm wondering if this is what is causing the issue?
  10. I've checked on my client computer running the Retrospect console and running the Retrospect console on the Retrospect server. Both reporting the same thing.
  11. All of my Retrospect jobs say Execution Completed Successfully inside of the Running queue. None of the backups are excecuting because all the jobs are stuck in the Running queue. Anyone else run into this? I'll restart the server which should free this up, but would like to know if there are any solutions to keep this from happening in the first place.
  12. When I click on the Send Test e-mail button in the email settings in Retrospect, I get a message that says : no server found at that address (-597) or I'll get a message: Invalid response from SMTP server (-592). I'm using an IP address to send to a local email server, not going outside our internal network. From the same machine running Retrospect, I can telnet into the SMTP server and send an email. So I know everything is working from the machine. There seems to be a problem with Retrospect. How can I find out what is going on with Retrospect not sending out emails. http://www.port25.com/how-to-check-an-smtp-connection-with-a-manual-telnet-session-2/ Running Retrospect 10.5 on xserve 10.6.8.
  13. So if I've set grooming to 2 snapshots, and the media set fills up at 1.5 snapshots, will retrospect ask for more media or just keep the 1.5 snapshots?
  14. I had the same issue earlier. It may prompt you if you wait a bit: http://forums.retrospect.com/index.php?/topic/150570-retrospect-server-update-for-102/
  15. "Don't groom too often. Grooming will automatically remove data when the destination disk fills up. If you want to make sure the disk never fills, create a grooming script (Automate>Manage Scripts>New) to run once a week. Grooming every day is typically not needed." The above advice from this link: http://www.retrospect.com/en/support/kb_show/grooming-tips-and-troubleshooting In the past, when a destination disk fills up, I get a message that says needs media. I've always assumed that Grooming does not automatically remove data when destination disk fills up, but would love to be wrong about this. Have others had success with grooming automatically removing data when destination disk fills up?
  16. This is working beautifully in 10.5! I was even able to multi select backup sources and update all of them with one click! Thank you Retrospect!
  17. Interesting point. Are you saying if two laptops whose OS is being backed up to the same media set, then identical files found on the OS system are only backed as 1 file? That is impressive, and not something I was aware of. I may need to rethink my backup setup if this is true. Can you point me to documentation about this? I suppose I could do a test with two of my backups, note the size they are taking, delete then back both up to 1 media set and see the difference in size. But that would take some time and I would be without a backup while it occurred. I would loose the ability to multi thread backups as well, which can be really helpful for proactive backups as a laptop may not be on the network for very long. If that laptop is waiting for another backup to complete, it may not get backed up before it disconnects from the network.
  18. This post doesn't solve your problem, which is a valid one, but as a workaround; you could create a media set for each laptop source. This allows Retrospect server to use multi threads for backups and you could have multiple laptops being backed up at the same time, instead of waiting in line. Retrospect shines in this area and is incredibly fast, hampered only by the speed of the hard drive you are backing up to. We have a 25 TB raid that Retrospect is backup up to. I've created a media set for each source. 17 sources. It takes some setup but when the backups run it maxes out the Raid write speed. The first couple times I set up Retrospect, I was using 1 disk media set per hard drive destination volume. Although it makes it easier to make sure you don't overfill the hard drive volume, it can slow down the backups. In a perfect world, Retrospect would back up multiple sources to 1 media set using multiple backup threads. If this were possible, I'd change my media sets from being by each source, to the physical hard drive destination volumes. Your setup may be different with smaller hard drive destination volumes and it takes more time to setup a media set for each source, but you may like the benefits.
  19. This happened again today. It's been running fine for the past week. One of the jobs says closing. 8 Jobs say Excecution completed successfully. One job says Execution incomplete. And one job has 8 errors. All the jobs are set to stop at 5 AM in their scripts. The media sets are open for writing and any new backup jobs will hold in the waiting queue. This started happening with 10.2 update. I've been having issues with email's not getting through to the Exchange email server and have been unable to figure out why Retrospect is having problems sending the emails out. I mention this because I'm wondering if this is somehow causing a problem. I turned off email notifications, and will force quit the engine. I'll wait to see if this happens again with email notifications turned off.
  20. I tried relaunching the console & running the console on another computer that is not the Retrospect server, but the jobs were stuck until I force quit the engine. I've had this happen probably about 5 times since installing. However, when I looked at the console yesterday, no hung jobs. I left the console running on a computer that is not the Retrospect server, wondering if leaving the console open would cause the problem. Returned this morning and no hung jobs. I'm going to try leaving the console open on the Retrospect server to see if that will cause the issue.
  • Create New...