Jump to content

All Activity

This stream auto-updates     

  1. Last week
  2. Great work David! I hope there was some error along the way to the developers, keep this post updated. For further reference on Bacula you can read this: Bacula and Docker Now, either you wanna backup anything about the docker or just a simple file on the Linux client Retrospect should be able to handle the client and the filesystem. One could expect to be able to take backup of your /home or what ever you fancy while Docker is installed. I do wonder if the retroclient stops working if you install docker on a windows server? If anyone reading this knows, please drop a reply! The retroclient should not freak out and die because Docker is installed on your system(linux, mac or windows), right? Regards, Pontus
  3. SHAB, Yesterday I phoned the Worldwide Head of Retrospect Sales, and left a message asking whether the soon-forthcoming Retrospect 18.x would handle Docker containers. He phoned back (because they've got several people out sick and he was in meetings) while I was out to dinner , and left a message that is a bit muddy on my answering machine. When I listened to it again tonight, I understood him to be saying that Retrospect "Inc." has no plans to handle Docker in Retrospect 18.x. However his message indicates that he believes Docker is a Linux distribution, and I shudder to think about how he re-phrased my question when talking to the engineers. 🙄 I'm merely an ancient home user of Retrospect Mac (although one of my "clients" in 2002–2004 was a Windows 95 machine forced on me for Work From Home by my bosses' boss). The only time I've ever encountered a VM was briefly as a remote user in 1969 of what was later to become IBM's mainframe VM/370, but I do read enough Ars Technica posts to be somewhat aware of what Docker is and its current importance. I'll write him an e-mail tomorrow, containing links to that Wikipedia article as well as to this thread—and stressing that Bacula will handle Docker containers. Salespeople worry about competitor's capabilities, so that should perk up his ears. 🤣 P.S.: E-mail sent 21:37 on 15 April 2021. In the first paragraph it also links to the Ars Technica front-page article saying Docker now runs natively on the Apple Silicon M1 chip, as requested by many developers. In the second paragraph it also links to a YouTube video on Bacula Enterprise Principles, a Web page showing Bacula's "backup server" only runs on Linux or FreeBSD or Solaris, and the Web page on Bacula and Docker you linked to below. I then said "Bacula—rather than just Synology’s Hyperbackup or OWC's maybe-back-from-the-dead BRU—looks like the competition StorCentric will run into for the Retrospect 18.x 'backup server' running on Linux [publicly predicted by StorCentric management]." How's that for motivating Product Management? 😎
  4. Clive Bruton

    Download Retrospect for 10.6

    David, it is hard to imagine where English came from, if not from the British Isles. Johnson’s dictionary had a little bit of a lead on Webster, as did the dictionaries that preceeded it. And you'll note the vendor of the dictionary in MacOS. Apple included many buggy bits of immature software in its distributions, ever tried MacOS Server? Do you work in politics, the twisted form of debate you enter into would certainly be suited to that line of… work. New York is certainly a long way from UDF 2457.5.
  5. Anyone knows where to read about Linux fix #8985 ? Been trying to find it but finding nothing...
  6. DavidHertzberg

    Download Retrospect for 10.6

    Clive Bruton, If you actually want help with your problem from volunteers such as me, IMHO you're not going to get it by picking fights about trivial points. My original guess that you're British was in the context of suggesting which location of Retrospect Technical Support you'd have talk to about getting a license code for Retrospect 16. Read that post again, and discuss its tone with your spiritual advisor. "Spelt" is the correct spelling in Britain; the Oxford dictionary is not considered an authority on American English spelling. In 1806 Noah Webster published his first dictionary; he was "very influential in popularizing certain spellings in the United States"—which resulted in Americans being spared Anglo-Saxon relics and Frenchifying. Retrospect "inc." is an American company, so its product terminology—including "catalog" without a "ue" on the end—follows American spelling standards. People on the Forums can cope with British spelling in a post, but IMHO we shouldn't be faulted for taking it as a clue to the poster's nationality when it's relevant to the problem—as it is for getting a license code. BTW the dialect's name is pronounced and popularly spelled "Strine"; I used to work for Australians. As the article at the right bottom of page 33 of this 25 September 1989 edition of InfoWorld says, "Apple will bundle Dantz Development Corp.'s Retrospect backup and archiving software with the Apple Tape Backup 40SC, Dantz officials announced recently." Apple is not in the habit of "buying a pig in a poke", so Retrospect must already have been in a demonstrable form around the 1988 timeframe when .tar was standardized. And use of the BSD version of Unix was legally restricted to universities until June 1989. I assume you already know that "Adoption of Linux in production environments, rather than being used only by hobbyists, started to take off first in the mid-1990s." Thus IMHO you'd be well-advised to quit griping about Retrospect not having adopted .tar format, and instead figure out how to skip your bad DVD file via copying. Discuss your feelings about the unfortunate necessity of that task with your spiritual advisor. Agreed, there's a rarely-encountered bug in Retrospect that should be fixed—but the only way you'll get that done is by submitting a Support Case.
  7. Clive Bruton

    Download Retrospect for 10.6

    If it was a bug, and still appears to be a bug, then it is a long-standing bug. Even if one did not have the limit of finite disk space to check against one could check the number of files the OS says are available for backup – once that is exceeded there is obviously an error. Of course run verify was on – what would be the point otherwise!? Although this bug does not manifest in the same way on verify, it may be the cause of the "internal consistency check" error I posted previously. The looping bug only seems to happen on rebuild/repair. Although Retrospect 10.x+ seems to also call verify "rebuild" in the process list. I'm not sure that, even if the backup failed an initial verify, that this would be much of an excuse for the persistence of the bug. This situation is rather like finding a bad file on a HDD and declaring the entire device unreadable. I'm sure you can see how untenable that is. Even if the original backup was not verified that does not preclude the fact that there is an obvious bug. If I am reading correctly, in my odd dialect of English, the article you point to, then the tar program was introduced in 1979, and made part of the POSIX standard in 1988 – 10 years and one year, respectively, before the first version of Retrospect. That MacOS < X had no connection to Unix is no barrier to tar being ported to classic MacOS, or being included as a library element in an application. So, this train of logic does not prove, either way, whether Retrospect uses tar format. Indeed, I have run Apache on MacOS 9.x. As you’ll note in the link you gave, tar is included in Windows too, which is also not Unix (a new OS: WIANU!) – I'm pretty sure de-archiving tools have been available for extended periods. According to Oxford, inter alia, it's spelt, spilt and learnt – so I don’t “think” that’s the correct spelling, it is the correct spelling. And I believe no one cares what my nationality is.
  8. Thanks for your answer David! Well, I did read that but thought it was "history". I initially failed to mention that the server side run on windows and is running the latest version of Retrospect Server. So, from whatever fix they made (#8985) it was not for servers running with docker installed 😞 I guess we will have to try some other backup solution for those servers running docker... We "only" have two so far but the plan was to expand that. Would have been nice if the Retrospect team could solve this since we have read about other backups that supports it and even supports backing up the containers. One example is Bacula. But we would prefer not having one more backup system running. I will let this question hang out a bit more and see if there is any more info to get. Regards, Pontus
  9. SHAB, Unfortunately this post in a January 2020 Forums thread says However that was for Retrospect Mac 16.6. You might consider upgrading your "backup server" to the latest 17.5.2 release, if you haven't already done so. For that release, the cumulative Release Notes for Retrospect Windows include
  10. Hello! We have been running Retrospect for years and seldom had any major problems, until today! We have been backing up a lot of Linux clients, mainly Ubuntu. Recently there is two new clients to backup that we just don't get to work. What is different from all other clients is that they have docker installed. They both run Ubuntu 20 fully patched and have the retrospect client Version 17.0.1.132. When connecting to them and checking volumes from the server it starts to show a lot of them, some with an icon of a pen with line across it, then after displaying all they drop off until none left. And so it goes on... Picture attached below. Now, what is wrong with the client? Why is it bananas just because we have docker installed on the client that is to be backed up? Any hints would be much appreciated! /Pontus
  11. DavidHertzberg

    Download Retrospect for 10.6

    (Disclaimer: Anything I may say about the intentions of Retrospect "Inc." in this or any other post is merely the result of "reading the tea leaves", the "tea leaves" being documentation and public announcements supplemented by an occasional morsel from Retrospect Sales. I have never been paid a cent by Retrospect "Inc." or its predecessors, and I pay for my upgrades. Any judgements expressed are—obviously—mine alone. The same is true of Retrospect's history, especially with references to here.) Clive Bruton, Good point about Retrospect's potentially being able to detect looping on a Rebuild when it continues to scan the same device past the data limit for that device.😁 That wouldn't be an example of the Halting Problem. In regard to this being a bug Retrospect Inc. should have fixed, note that the Forums post I linked to up-thread was in 2010 for Retrospect Mac 8.2. As this section of the old Wikipedia article indicates, Retrospect Mac 8.2 had a lot of more pressing bugs to fix. Here is why and how to submit a Support Case for a new feature. Retrospect has always had the option to run a compare phase after a backup, because writing to physically-flexible magnetic media—including DVDs—has always been error-prone; my backup scripts always include a compare even though their destinations have been HDDs for the past 6 years. Did you run a compare phase when you originally backed up to this problematic DVD? If you didn't, caveat emptor; if you did, it's bad luck your DVD decayed later. The format of Retrospect Media Set members isn't .tar, because the original version of Retrospect's "backup server" was developed before .tar was standardized for Unix. And, as that same section of the old Wikipedia article implies, that original "backup server" ran on Classic Mac OS—which had no connection to Unix. There is a fairly-reliable prediction by insiders that Retrospect 18.x will have a variant of the "backup server" that can run on Unix, but IMHO its format for Members of Media Sets won't be switched to .tar. If you want to switch to a non-client-server backup application that uses .tar format, consider A**. According to Wikipedia, "Spelt (Triticum spelta), also known as dinkel wheat[2] or hulled wheat,[2] is a species of wheat that has been cultivated since approximately 5000 BC." If you think "spelt" is the correct way of spelling "spelled", it's probably because you're British. Why try to hide your nationality?
  12. Clive Bruton

    Download Retrospect for 10.6

    The bug in the forum software is that it suggests that you can sign-in with your email address, but in fact you can only sign-in with your username. The endless loop of Retrospect getting stuck on a DVD member in a catalogue isn't really an example of the Halting Problem. This is primarily because there are parameters, which are easily discernable, which tell you whether the program is functioning correctly, and therefore should have ended. In this example there is a very definite limit to the data that can fit on a DVD (sans compression), ~4.5GB. If the program continues to scan the same device when it is obviously well past that limit, then there is obviously a software bug. While there could possibly be an arbitrary number of members, that make the actual end run of the program difficult to predict, that doesn’t prevent a decision being made about each individual member.
  13. Clive Bruton

    Download Retrospect for 10.6

    Oh, and there is some kind of bug in the forum software, where it doesn't let you sign in with your password, you have to keep resetting!?
  14. Clive Bruton

    Download Retrospect for 10.6

    I find it very concerning that this bug is still present in Retrospect, it really does not give a great deal of confidence. The entire raison d’etre of the product is to give peace of mind that data is secure, which is completely undermined if all the file on a dataset member are unrecoverable due to one bad file on the member. This is equally applicable to any kind of backup where the files are obscured by the process (ie you can't see them on the desktop), like DVD and tape archives - where files may actually be split across members. I would know where to start copying the member to a HDD and trying to edit it. When the DVD mounts on the desktop you see a small retrodata file, and the actual data is not shown, and the format not known (I've recently come to conclude that it's probably a .tar, but do not actually know). Catalogue is actually spelt (not "spelled") that way en Francais, in Canadian English, 'Strain and K'wee (probably other dialects too). Thanks for the family history. There are lots of people int he USA who think they have “British” names, but which actually do not occur in the British Isles, and which are actually anglisisations/mispellings of European names. As you have established with your own ancestry. A popular variant on this is the Dutch “van” prefixed attached to a British name (ie Vanowen was actually van Ouyn).
  15. DavidHertzberg

    Download Retrospect for 10.6

    Clive Bruton, If this 2010 thread relating to Retrospect Mac 8.2 is applicable, then it looks as if your "constant looping on rebuilds/repairs" while "repairing a catalogue from a DVD" means a .rdb file in a Member of that Media Set on the DVD is bad. IMHO that would call for a Support Case to detect the looping, except that I believe your compatriot Alan Turing demonstrated doing it would require a solution—which he proved to be impossible—to the Halting Problem. A preceding post in that thread describes how the OP identified the problem file during the rebuild—and evidently got around his problem by removing the bad .rdb file from the Member; however his Member was on a Drobo (genuflects in the direction of San Jose CA)—not on a DVD. Maybe you can identify your bad file by the same method, then copy the Member to a HDD that you can edit to remove the bad file, and finally copy the edited Member to another DVD and rebuild your Catalog with the edited DVD as the substitute Member. You'll lose the backed-up data on the bad .rdb file, but that can't be helped. My jocular remark about the typical Britishness of your "handle" was intended to encourage you to edit your Forums Profile to allow us to see your Location. (However you've "outed" yourself as British by your spelling of the Retrospect term "catalog" as "catalogue", unless you're Canadian.) You could also be really brave and enter a Gender, so that other posters wouldn't have to guess whether to refer to you in the third person as "he" or "she". As my Profile says, my Location is "New York, NY", and it's always difficult to guess at the ancestry of Americans. My paternal grandfather told me "Hertzberg" was originally spelled "Herczberg", but a U.S. immigration official suggested he change it when he emigrated from Poland. (If it makes you feel any better, my mother's side of the family emigrated from Germany after 1848.) Nevertheless—from my childhood onward—people have been deciding my name must be spelled "Hirshberg" because I look like a Jew—which I am. I've lately been telling such people to imagine they're on a trip to Greenland, and want to rent an iceberg from a car rental company that's well-known in the States—hence a "Hertz berg" spelled as a single word.
  16. Clive Bruton

    Download Retrospect for 10.6

    Erm, well it seems that the demo code system is only able to give out licence keys for the current version… so I won't be, imminently, giving feedback on the state of bugs in Retrospect 16.1.
  17. Clive Bruton

    Download Retrospect for 10.6

    Lennert, thanks. David, if that “fix” is the constant looping on rebuilds/repairs, then I think it is not fixed, because I see exactly the same issue on Retrospect 17 on MacOS 10.13: it is currently repairing a catalogue from a DVD and thinks it has successfully retrieved 77GB from that DVD. A new world record I think! I'll let you know if the “out of memory” fault is fixed. Is David Hertzberg not “typically” German?
  18. DavidHertzberg

    Download Retrospect for 10.6

    Clive Bruton, Do what Lennart_T said. This Knowledge Base article says the last version of Retrospect to run on macOS 10.6 is Retrospect 16.1. Lucky you; the Retrospect Mac Cumulative Release Notes have this Engine bug fix for 16.0: My instinct says that's your problem with Retrospect Mac 10.5. 😄 Of course you'll have to get a License Code for Retrospect 16. Since your "handle" is so typically British that it may in fact be a pseudonym, you'll have to consult Retrospect Tech Support for Europe (unless there's a separate Retrospect Tech Support for formerly-Europe 🤣 ) . Be sure the appropriate credit card is close at hand when you make that phonecall; they may give you a discount because you want a license code for an older major version.
  19. Lennart_T

    Download Retrospect for 10.6

    At the bottom of the general "Downloads" page ( https://www.retrospect.com/en/support/downloads ) there is a (small) link to "Archives". https://www.retrospect.com/en/support/archived
  20. Can someone give me a link to download the last version of Retrospect to run on MacOS 10.6 (Snow Leopard)? Retrospect 17 does not. I have Retrospect 10.5 running on Snow Leopard, but it seems to have a bug in that it cannot rebuild catalogs with more than 79 members (perhaps this is a bug in more recent versions too?). The log says "!Not enough application memory". I don't really accept this, because it gave the same error on two different machines – one having 2GB of RAM, and the other 4GB. Cannot see that RAM is an issue there, when the recatalog/repair is failing at exactly the same point. An odd kind of bug because Retrospect 6.1 creates catalogues with (at least) 100 members. I cannot use Retrospect 6.1 for the rebuild, because it seems to have a bug that when verifying catalogs it cycles repeatedly over the same member, or when rebuilding/repairing it will get to a member and declare some kind of fault that it cannot continue: "Trouble in Retropect: Internal consistency check failed: Assertion check at "elem.c-918"" (see attached file).
  21. Earlier
  22. cgtyoder

    Disaster Recovery doesn't support high DPI screens

    Already been talking to support. They walked me thru the garbled screens. This is actually for Windows on a MacBook Pro (a "Boot camp" partition). Turns out Dantz doesn't support Disaster Recovery on Apple hardware - too bad I didn't know about that ahead of time. Looks like I'll be reformatting & reinstalling everything manually - what a PITA. Looks like also I'll be changing what backup software I use...
  23. DavidHertzberg

    Disaster Recovery doesn't support high DPI screens

    IMHO cgtyoder—because he's definitely got a license for Retrospect Windows 17—should create a Support Case at https://www.retrospect.com/en/rscustomers/sign_in?locale=en . If he isn't already signed-up he should click that link to do so. He should be aware that, if his problem statement runs much over 2000 characters (16 lines of a 9-inch-wide inner window), it will spill over into an Additional Note. He should also be aware that Retrospect "Inc"'s highly-advanced Support Case system doesn't allow linking or underlining; I use before-and-after underline characters, and I paste-in links with a space afterward to facilitate copying into a browser link window. Having done that, cgtyoder should put the Support Case number into new a post in this thread. x509 can then create another Support Case, with a Problem Statement mention of cgtyoder's Support Case number. That will get around the wonderful feature that limits access of a Support Case to the administrator who submitted it. Be aware that these problems may turn out to be a result of limitations in Microsoft's WinPE underpinnings for Disaster Recovery.
  24. I have the opposite problem. A low DPI laptop screen. A secondary monitor doesn't work. (Lenovo T series)
  25. mbennett

    Disaster Recovery doesn't support high DPI screens

    The only possible idea I can offer is that if you can plug an external, lower resolution monitor into your laptop, and it it lights up (both very big "ifs" I realize) that may give you the ability to view a screen. I assume the second monitor is made accessible in the BIOS, so it's something to try.
  26. I am in the process of attempting to perform a disaster recovery (latest and greatest R 17.5.2.103) on my laptop with a high DPI screen, and when I boot from the WinPE disk, the text is garbled or only partially displayed - it looks like the screen is corrupted. I added in my laptop's drivers before creating the recovery disk, but that didn't help. There's really no excuse for lack of high DPI screen support in 2021 - any idea for a workaround so I can get my PC back up and running?
  27. backy, After some more belated thought and one little experiment, I'd like to revise my recommendation in the last paragraph of this up-thread post. If you want to use a Storage Group defined on a Retrospect Windows "backup server" as a Destination, you may be able to get away with it—but I'd advise against it. My belated thought was that you could define a Grooming policy for the Storage Group. My experiment showed I can do this even on a Retrospect Mac 16 "backup server". Presumably the Grooming policy is applied to each component Backup Set as it is automatically created—when a new machine-volume is added as a Source for a script whose destination is the Storage Group, but I can't confirm this because of the so-far-incomplete Storage Group GUI in Retrospect Mac. Also presumably in Retrospect Windows you could modify the Grooming policy and the initial Member size for a particular component Backup Set, but again I can't confirm this. Ability to do those modifications depends on the capability of using the Retrospect Windows GUI to directly access a component Backup Set; there's currently no such capability in Retrospect Mac's GUI. The combination of these two capabilities—if they exist in Retrospect Windows—would allow you to tailor the maximum initial Member size for a particular component Backup Set. This—done carefully—would enable you to ensure that the sum of all components' initial Member sizes would never actually exceed the size of the Storage Set's defined Destination disk. Therefore, if you ran Transfer scripts frequently enough, you could make sure that all files from components had been Transferred to tape before they were groomed out of existence. So you wouldn't have to run any Recycle scripts having as a Destination the Storage Group; you could rely on the components' Grooming policies. If you can add additional Members to a particular component Backup Set, that would provide an additional safety factor. I can't do this either, again because the so-far-incomplete Retrospect Mac Storage Group GUI won't let me directly access a Storage Group's component Media Sets. Of course your Transfer scripts wouldn't be copying files simultaneously backed up by your Proactive scripts (because you couldn't make them use one Execution Unit)—pending enhancement per my Support Case #54601 (case# in P.P.S.). And it'd take substantial effort for you to explain this strategy to another employee of your company. Undoubtedly my recommendation in that up-thread post that you not use a Storage Group is still the wise choice.
  1. Load more activity
×