Jump to content


  • Content count

  • Joined

  • Last visited

Community Reputation

6 Neutral

About gabbiano.brillo

  • Rank
  1. Hi Mayoff, thank you for your answer. I should have read the compatibility table before posting ... Apart from this, I regularly test a backup/restore process with sample data (and real restore needs), according to my experience the installation I described earlier has always been working like a charm, with the exception of the problem I posted earlier. Of course I trust your statement about the unsupported client and its possible consequences ... So, definitively, this is an old installation and it would be the time to upgrade. This depends on the fact that it will be approved in the budget, and this was not planned for this year :-( So, in case there is a workaround to start the client enabled we will appreciate it a lot :-) Waiting for next year and the new budget, with this upgrade considered in advance ... Thank you again! Gabbiano.
  2. Hi, I have an old installation of Retrospect multiserver 7.7 for Windows that performs backups of a number of Windows and Mac OSX clients. With the OSX clients, no problems till version 10.9. When I upgraded the operating system to OSX 10.10 Yosemite the Retrospect client (ver. 6.3.029) starts disabled. Can you suggest a method to start the client enabled when the machine boots? Thank you in advance! Gabbiano.
  3. Hi, in the past I purchased a license of Retrospect 7.5 (to point out better the software is versioned 7.5.251) which I upgraded to 7.6.123 following the update feature in the program itself (i.e. Help --> Retrospect updates) and this was alive for years. Now I need to reinstall this server, and I reinstalled the 7.5.251 version. Unfortunately, when I follow the same update procedure I get the desolate "Unable to connect to Automatic Updates site" error message. I exclude that this is due a firewall or similar setting preventing the network traffic from succeeding. My guess is that the source of software used by this procedure has disappeared in these years. Am I wrong in somethng? Or are you aware of an alternate source where I can fetch these updates from? Thank you in advance! Gabbiano.
  4. gabbiano.brillo

    Recover a "partial" backup set

    Hi Mayoff, thank you for your answer. But my additional question is: are you aware fo the existance of an utility to rebuild the integrity of a partial backup set? The files I undeleted are consistent (i.e. no cluster lost), but some others are missing, that's the reason why I cannot start recovering the catalog from. But possibly the data I need to recover are indeed in the files I saved. If this utility actually exists, I would like to make this last attempt before contacting (paying) and external company - or eventually giving up. Thank you again!
  5. gabbiano.brillo

    Recover a "partial" backup set

    Hi, odd question I'm posting here, i know :-) I deleted a backup set intentionally because I've been ensured that it was not useful anymore. Then, after the successful deletion (I deleted the .rdb files with the content, of course), I'm now told that this backup set is indeed useful, because a workstation was not included in a new backup policy, and a disk was broken (I'm omitting how), and of course it was soooo important (otherwise, why backing it up?) ..... I can post here a number of comments about the people I'm working with, but let's switch to the actual question. I tried to undelete the relevant *.rdb files to rebuild this disgraced backup set and I managed to get back a number (an huge amount of data), but not all of them. Now I'm trying to recover the catalog, which unfortunately fails ("The selected disk does not contain any Backup Set data files") because this set is incomplete. As far as you are aware of, is there any way to recover the backup set to restore its integrity, despite incomplete, so I can try rebuilding the catalog and then trying to restore the content that this smart colleague needs? Some details: Retrospect 7.6 in Windows Wk3 server. Thank you in advance! Gabbiano.