Jump to content
The search index is currently processing. Activity stream results may not be complete.

All Activity

This stream auto-updates

  1. Earlier
  2. 18.2.1 was released yesterday to fix this issue. http://www.retrospect.com/updates
  3. Any timeframe on native Apple Silicon binaries for Engine, Console, and Client?
  4. It's been some years since I used proactive scripts, so things may have changed how they work. And I also may not remember everything correctly. Back then (I think) the time between backups was measured from the end of the last backup to the start of next, so I had to set that to 23 hours (instead of daily) to get the next backup of that source to start a little earlier "tomorrow" than it ran "today". Otherwise it may miss the active window. The active windows was set to normal business hours plus one hour at each end to cater for those who came a bit early and those who had been on the road and arrived late. Perhaps you should set up the proactive script to run between (say) 6 AM and 8 PM. That should be ample time for the backup to finish. Except, perhaps, with the exception of the very first backup for each backup set. As for why your backup terminates at midnight, I have no idea. It shouldn't do that. Perhaps you could share a screenshot or two of your script settings?
  5. Two of the 4TB drives are from 2019 and have never been used (WD Reds), the other 4 drives are about 6 years old (WD My Books). Thank you for the advice about incremental backup, I have unchecked that function as well as the groom function which I will do manually every so often. I do have a question about proactive scripts. The one I have set up so far is set as "Always Active - Allow automatic execution anytime" but it does not want to start until midnight in spite of there having been no previous backup made. I would have expected this would run at anytime (as implied) in the background. I got fed up, and changed it to a scheduled time of 10:25 PM (I did this at 10:20 PM and wanted to see if something would happen), and it started up, but terminated at midnight. It did the same thing the next day. What am I missing here? Shouldn't the backup be running now (I have changed it back to Always Active) since the backup is not complete?
  6. How old are they and how much have you used them? Old hard drives are failures waiting to happen. (On the other hand, it's many years ago I had a drive fail on me, even after years of use. ) No. Most files nowadays are already compressed and can't be compressed more. It's just a waste of (CPU) time and energy. Anyway: With that kind of data, you should be fine using the setup you have proposed with 2 sets of 3 backup drives. They should be large enough. I would not use block level incremental backup. That's useful only for very big files where you change only parts of the files, such as database files. I would use Disk backup sets, not storage groups. You should probably run a Groom script every once in a while, to groom out old backups. (You don't HAVE to, as Retrospect will do that for you when the disk becomes full. BUT that will happen in the middle of a backup and according to Murphy's law it will happen when you are in a hurry to get the backup finished.) Hope this helps.
  7. Drives currently at: E: Data - 0.6TB Used X: Photos 1 (up to 2018) - 2.9TB used - but other than occasional editing of older images, not actively adding new photos to this drive Y: Photos 2 (2019 +) - 1.7TB Used - but adding new images as time goes on. Understood about using a fewer larger drives for back-ups but I have the drives I mentioned from the past and not looking to spend money on more drives at this time as I have these other spare drives available. Is my basic understanding in my original post how to set this up correct? Should I also have Retrospect compress files on the back-up drives? I believe I saw that an option somewhere. Thanks
  8. How much data is there on E: X: and Y: respectively? As a rule of a thumb, you should allocate storage about twice the size of the DATA you want to backup. Instead of two sets of three backup disks, you may want to have two larger disks. Seagate has disks with 16 TB capacity as well as 8 TB for about 40% of the price for the 16 TB disk. With larger disks as backup disks, you need only two backup sets. That way you can use "grooming", a process that "grooms" out the oldest backups. That way you don't have to erase all data to start copying x TB of data from scratch.
  9. HI. I have purchased Retrospect 18 (Solo) for keeping back ups of my photos and documents. I am not an IT professional and probably over thinking this and so very unsure of what I need to do to set this up efficiently for what I want to do. I have attached a simple sketch that will hopefully aid in understanding what I have and what I would like to do. Basically I have three SSDs or HDDs on my home PC that I wish to keep backed up. One 2TB SSD contains date (documents, spreadsheets, etc.), while two 4TB HDDs hold my photo collections. I have 6 HDDs (2 x 2TB, 4x4TB) that I will be using as backup destinations. At any one time three of these HDDs will be at home and the other three will be stored at our cabin located about 200 km from home. I plan to swap these drives on a roughly monthly basis taking the three back-up drives home up to the cabin on a Friday and returning back with the other three drives on the Sunday and connecting these to my Home PC. These would be one month out of date and so I would expect retrospect to update them and bring them up to speed. I want to set this up so that other than me physically disconnecting and reconnecting these drives to my PC that all of the backing up is carried out automatically without any user intervention in the software. I believe I want to do pro-active backups that backup daily while the three backup HDDs are connected the PC and set up incrementally so that only changes to files are backed up. And I would like it to be set up so that when my back-up HDDs become full, that Retrospect just overwrites older back-up data on the disc and does not ask me for a new disc. Otherwise I would just reformat the backup HDD and live with redoing a full initial backup on the disc. From what I have gathered in my stumbling around so far in the software is that it looks like I will end up with six back-up sets and six scripts (one for each back-up set). I am finding the process confusing because of my lack of familiarity with all the jargon and so I am suffering from analysis paralysis so to speak (like I said before, overthinking this). ! could use some help in setting this up. Is it basically: Clicking Proactive AI Backup under the Backup and create New + name it Source - Select disc on Home PC to be backed up Destination - create new backup set choose disk, give it a Backup Set Name and choose destinations disc unclick create as storage group??? choose backup security level keep only last 10 backups Use default catalogue file destination and finish Select - All files Options backup every day block level incremental backup on thorough verification on back up open files Schedule - always active And repeat the process a total of six times. Thanks in advance.
  10. It should appear as Retrospect Engine, as far as I know. It is running under rosetta.
  11. I just installed Retrospect on an M1 iMac and noticed there is no process named Retrospect Engine visible in Activity Monitor, so it must be operating under a different name. Does anyone know what that is?
  12. Not an engineer and so this comment may be without value, however this reminds me of problems I've had with MacOS and even IOS, that make me suspect this might be an OS problem rather than something easily fixed by Retrospect. There have been numerous times when other software also thinks my Mac has changed and is no longer the Mac it had saved data on. The example that comes most readily to mind is web sites telling me I am logging in from a new device. I am not. It is the same the Macbook pro and yet I get this kind of complaint when I authenticate with sites several times per year. I had loosely assumed that it has something to do with updates to the OS, that somehow change something that web sites use to uniquely identify the device... and I haven't worried much about it because unlike your situation, there isn't really any hassle involved. Maybe someone from Retrospect will chime in and confirm or deny my observation has anything to do with it.
  13. Update: It all went well as far as booting Windows PE from the USB drive and starting the Retrospect utility on the client PC. Restore of the ~230GB data backed up from the old Samsung 850 Pro 1TB would not restore to a brand new Samsung - 870 EVO 1TB. Retrospect claimed not enough space, even though it said there would be ~700GB free. Spent ~2hours on phone support and in a remote control zoom session proving that this is what happened. Strangely enough the restore kind of worked to another brand new Samsung - 870 QVO 2TB (yes, this exercise is getting expensive). Logging in with the user account gave Windows error message: "We can't sign in to your account". I was able to patch it up using the "Fix a corrupted user profile" procedure, but that is not a successful restore in my book. The phone tech "escalated" the problem -- as far as I can tell that just meant opening a support ticket on my behalf, which remains totally silent from the Retrospect side. This has not been a good experience.
  14. Today on my MacBook the Retrospect Client icon appeared with an exclamation mark. The control panel informed my that the client was waiting for the Retrospect login. Why? I don't know. The client had been installed ages ago and I haven't made any changes to it. It only had the client software upgraded to 18.2 via the automatic client update but that was a couple of days ago. But now I'm facing that wonderful error -525 on the server. Retrospect says my MacBook is not the MacBook it used to be. So all I have to do is forget the client and add it back. Easy, except for one thing: I have 20 favorites on this Mac. And they have each their own script to save data. Which means I have to add 20 favorites back and then modify 20 scripts again to get my backups up and running again. But what am I complaining? It only takes 1 hour to get it al how it was before the Retrospect client decided to do it's thing. This behaviour should be fixed. Error -525 has given Retrospect users lots of unneeded issues. And the whole point of using Retrospect is to be protected against loss of data. But having to lose (read: wipe) configuration data to get backups running again is a joke.
  15. Great! Our Win server is running Retrospect 18, so we're good there - it's already backing up a pair of Synology NAS boxes without issue. I don't need to back up the M1 itself, just the RAID that's attached to it, but I didn't want to do it via 'sharing' unless I had to. Thanks!
  16. I have the same issue. Since daylight saving time Retrospect sends Daily report in hundreds of copies. Version 18.2.0 (Mac), Daily report set at 0:00 and Retrospect starts sending flood of reports at 23:00
  17. Retrospect fully supports M1 hardware. If you are trying to back up the M1 over the network to the Windows system, you would need to run Retrospect for Windows on the 2019 server and put Retrospect Client onto the M1
  18. This does seem like a bug. We have it flagged as a high priority with our engineering team to resolve.
  19. I tried it with just one installation (our own - Version 18.2). Immediately, when I set 0:00, I got another bunch of emails. So I switched the reporting off in preferences again. I played around with it: on/off, several time settings 3:00 and 0:00. When turned on again to 0:00 another email was sent. But only one. It seems the process calmed down. No more emails at the moment with standard settings. So, probably I found a way to solve this. But the question remains: Why did this happen?
  20. Lennart, thanks for your reply. As I described above I changed the sending time of the daily backup report from 0:00 (standard) to 3:00. Tonight we only had one backup report. So hopefully, with this change we reset the timing to working condition again. Next try: Going back to 0:00 😰 All installations are on version 18. Not every one with the latest update but some are. Regards
  21. I remember seeing something similar, but that was years ago. Please provide some facts, such as which version you (they?) are running and what the emails say.
  22. Since the European time section of daylight saving time ended last weekend we got tons of emails of the daily backup report. This is on four different locations (four customers). Did anyone notice the same issue? I changed the sending time from 0:00 to 3:00. Wondering if this helps... Regards from Hamburg Olaf
  23. Running Big Sur on an M1 Mini, want to backup DAS to a Windows 2019 server running Retrospect Server v18 over LAN. I've had a search through the forums and can't find much regarding M1 clients. Not much in the documentation either. I'd rather not share the volume and mount it on the server unless I have to. Interested in your experience running client on an M1 Mac. TIA!
  24. I went through creating the bootable Windows PE USB stick. The biggest problem is that the USB stick must be MBR, while it appears that GPT is now the default (at least for my machines and my USB stick). Once I got through using diskpart to make the USB drive an MBR drive, it all went well.
  25. We have a new set of DR directions that can be found at http://www.retrospect.com/dr that include new/updated articles and new detailed tutorials.
  26. Bump . . . is there a guide to create a Microsoft WinPE recovery flash drive that includes the necessary retrospect files to recover a client?
  1. Load more activity
×
×
  • Create New...