Jump to content

hevanw

Members
  • Content count

    11
  • Joined

  • Last visited

Community Reputation

1 Neutral

About hevanw

  • Rank
    Member
  1. Error -530 (backup client not found)

    So what is considered the most reliable way to access/configure a backup client ? I've had Retrospect for about 2 months now, and using Proactive Backup, this is now already the 3rd time that one of my client machines at home suddenly is not found anymore. I use direct hostname or IP. I normally can solve it by adding the client again in Backup Clients. However, right now e.g. my wife's laptop I cannot add through Direct as Access Method. Neither IP nor hostname work. Weird enough, when clicking on Multicast or Subnet Broadcast, her laptop does show up with it's normal hostname. I'm a bit wary of using those access methods though as they've given me plenty of -530 errors in the past.
  2. Is a Recycle required now and then ?

    Thank you. This is exactly what I wanted to know, and yeah I guess the recycling was still a remnant of the days where I backed up to DVDs.
  3. Is a Recycle required now and then ?

    (wonder why in all your posts you refer to the other forum members in 3rd person...? Looks rather goofy...) Anyway. I used to do for a decade exactly what you describe in your last paragraph. Every Friday morning I would turn on all client PCs and take backups. This was the only feasible way in the beginning as I was still backing up to DVD-RWs then (using Retrospect 7). I had multiple backup sets such that I could rotate and recycle them like twice a year, at which time I would have to tell my wife not turn off her laptop as a recycle is a full backup and thus would take several hours. However, with a NAS as target, there is really no reason to limit yourself to such infrequent backups. I'm now running proactive backups since 2 weeks or so (evaluating latest Retrospect) and realize I should have done this much earlier (basically as soon as I abandoned the DVDs). No longer the hassle of having to make sure that clients are on when running the backups (in fact, I ran the scripts manually then), and at the same time having much more frequent backups. And yes, even though it's a home setting, the schedule more corresponds with your Suzy SalesPerson model where the times the laptop is on and available for backup is rather arbitrary. The 2h frequency may be overkill, but it's again a trade-off between backup overhead and backup recency. The longer you wait with your backups the more potential data can be lost when a disaster strikes. At the moment I don't have the impression that the overhead of Retrospect is that high that a 2h frequency would cause a problem. The only reason my wife now knows her laptop is being backed up so frequently was because of the W10 notifications that popped up every 2 hours, but that was easy to turn off. Now as for cloud storage/backup, that's of course a different matter, since then other variables come in play like limited network speed (esp. upstream), cost of upload, cost of online storage, etc... I also read that specific section in the UG, and the only thing that really concerns me is that Proactive Backup is only available with the proper license. So I need to double check whether it's actually available in the Desktop version.. EDIT: Proactive just seems to be part of the Windows Desktop (and I then assume any) version : https://www.retrospect.com/en/products/win/desktop .
  4. Backup keeps including all files

    Thank you ! After some in-depth tests, it was indeed the Security Information that was the culprit. I've now disabled both file and folder options and now only what has truly changed is being backed up.
  5. GUI disappeared

    Ha nice, from the release notes it looks like 12.5.0.177 has addressed this as well.
  6. Backup keeps including all files

    Thanks for the suggestion ! I can indeed look into connecting the disk through USB on the NAS as that USB disk is only used as a disaster recovery backup of the NAS. The NAS is a Synology DS418j. Still a bit confused though why the matching fails. Isn't the matching supposed to do a comparison file-by-file or even block-by-block (since I have Block Level enabled) based on hashes ? Retrospect is even not supposed to write a full file if it is found elsewhere on the filesystem as well (unless that 'path match' option is enabled). The files have not changed, so the underlying file system should not matter.
  7. One of my backup scripts does the following : it back ups my entire NAS (8 shares in total) to an external 4TB hard disk. This script runs once a week. It now looks like every time the script runs, the entire NAS is written to the disk rather than only the changed/new files. The backup set has the following options: Block level incremental backup, Media verification, Data compression, Match source volumes to Catalog File, Don't add duplicates to Backup Set. The catalog files are stored on my Retrospect Server, and the 4TB backup target is an external USB disk. The one thing that I can imagine having an impact, is that the NAS shares are mounted on the Retrospect Server as read-only. But even with 'Match only files in same location' being unchecked, I would think this should not have an impact. Retrospect should match any file from the NAS with what is already in the backup set and thus not backup the same file over and over again ? Note that in total I have 6 backup scripts and sets and this is the only script that is behaving like this. It's however also the only script where data from the NAS is being backed up.
  8. Is a Recycle required now and then ?

    Thanks for the elaborate response ! Note that I'm currently not yet using Retrospect's own Cloud support for my uploads to the cloud. CrashPlan just considers the rdb-files as regular files and uses it's own algorithms for incremental backups to the cloud. As mentioned, this is working pretty well. Even though my entire Retrospect folder (i.e. where all the rdb-files of all clients are stored) is now about 1.4 TB and growing (as long as I don't groom), CrashPlan only sends a few GB per night to my CrashPlan cloud storage to complete the backup of the entire Retrospect folder. Anyway, for now I will not worry about doing Recycles. From what I see from the online information (still need to go through the actual User Guide) I should have no need to recycle my backups in the foreseeable future.
  9. GUI disappeared

    Problem solved. The separate Dashboard application has a button 'Relaunch' which then relaunches the actual Retrospect application/GUI.
  10. I've been using Retrospect 7.5 for almost a decade or so, in combination with CrashPlan Home. Retrospect was sort of the 'backup' (no pun intended) to CrashPlan where I only ran Retrospect once week for all Windows clients at home from a 24/7 Windows home server (running Windows 10 Pro). With CrashPlan Home being sunset, I'm now making Retrospect my main backup solution for all clients and therefore am upping the frequency to every 2 hours with a pro-active schedule. I'm evaluating the latest version of Retrospect for this (where especially the much improved speed looks to be very helpful). I then also store/backup my Retrospect backup files to the cloud every night as an off-site backup. This is currently working pretty well as the incremental backups cause only small changes to the rdb-files which then cause limited uploads to the cloud. Now, this will work well as long as I keep doing incremental backups. However, in my old backup strategy, I regularly recycled backups. This is now less ideal since a Recycle will basically generate a completely new backup set which then again needs to be completely uploaded to the cloud. Question: will never doing a recycle eventually cause problems with the backup sets, particularly in terms of performance and reliability ? Also, I realize that grooming a backup set (which will happen when I hit the max. allocated size for a backup set) may cause the rdb files to get modified so much that their cloud upload may require a full upload again.
  11. GUI disappeared

    I'm currently evaluating the latest Windows desktop version with 2 additional clients. Retrospect runs 24/7 on my Windows home server (Windows 10 Pro - Creators Update). Since yesterday, the GUI has disappeared in the sense that it looks like Retrospect is no longer running. I'm not sure whether it disappeared/crashed itself or I accidentally closed it. Retrospect engine is however still running fine as the clients are still reporting the backups starting according to the pro-active schedule. So question: how can I get the GUI back without actually going to kill the Retrospect processes first and then restarting the application ? Note that just starting the application does not work as it reports that Retrospect is already running.
×