#Retrospect defintion update#
My suggestion would be to work out a deal with Retrospect Sales to buy Retrospect Mac 18 with a free update to Retrospect Mac 19-a deal which should now be available because it's getting close to the usual Spring release date for new major versions-but to get them to throw in a license code for Retrospect Mac 17. Those administrators at least were using Version 18 of Retrospect Mac, which I myself have not upgraded to from release 16.6. I did so because apparently the Retrospect "Inc." engineers are too distracted to act on any Support Case that TurningFred or DigitalItalian may have filed.
P.S.: On 7 March 2022 I filed my own Support Case #83532 for the bug whose description is linked-to in the second sentence of this up-thread post. The engineer who wrote the KB article would have been able to fix the bug in 30 minutes, and he'd have been unlikely to create it in the first place-which was most likely done by "inexperienced manpower". of this same up-thread post that the existing Retrospect engineers have been split into two groups one group developing the Linux-based "backup server" variant and the associated LAN remote GUI Console, and the other group-possibly bolstered by new hires-trying to fix bugs (ones they created?) in the existing "backup server" code. This tends to confirm my speculation in the last paragraph and P.S. And the KB article uses the Retrospect Windows term Backup Set instead of the Retrospect Mac term Media Set, implying it's oriented towards Windows administrators. BTW that's the Retrospect definition of "snapshot" adopted in 1990, not the Unix filesystem definition of "snapshot" industry-adopted later-even by APFS. "Active Snapshots" in the Catalog File enable de-duplication and grooming.
0 kommentar(er)
