Jump to content

Ron Haines

Members
  • Posts

    21
  • Joined

  • Last visited

  • Days Won

    3

Posts posted by Ron Haines

  1. Hi,

    I upgraded a Retrospect 14.6.1 (101) machine to Retrospect 15.0.0 (190) and after the upgrade the machine can no longer e-mail reports. It can't even send a test e-mail  - it says 'Trouble communicating (-102)'. E-mail preferences are configured to use an un-authenticated SMTP host on our campus. I can telnet from the upgraded machine to port 25 on the SMTP server, and I have a second Retrospect machine still running 14.6.1 which continues to send e-mail reports through the smtp server. It looks like something changed in the way e-mail is handled in 15.0.0. 

    Has anyone else seen this, or can give me a clue about getting e-mail working again? 

     

    Thanks,

    Ron

    Update: in system.log on the upgraded machine I can see "Retrospect[81482]: PreferencesEmailController::sendTestEmail exception: E-mail notification failed: error -1027 (connection refused)"

  2. We have all of our Retrospect clients authenticated with passwords. Managing and securing the passwords is becoming a big task, so I am contemplating going to private/public key authentication. If I generate a key pair and start using it to add new clients, will this interfere with the existing clients using passwords? If I update a (passworded) client with a newer version, with the public_key in place for the client install, will the server switch to authentication with the key?

    Thanks

    • Like 2
  3. In the Mac Version 12 User Guide (and in several previous versions) the section "Upgrading from Previous Versions of Retrospect" (page 18) doesn't make much sense. The first sentence reads "Because Retrospect for Mac has a different underlying architecture and uses different configuration files than previous versions of Retrospect for Mac, version does not import settings from version 6.x or earlier installations."

    I think there are three places in that sentence where specific version numbers should be inserted. The KnowledgeBase article about upgrades says that since version 8, upgrades have preserved settings etc, which is contrary to what the User Guide says. Could someone have a look at this and correct it please?

  4. Just in case this lets someone else avoid my brain-block...

    After a long time looking irritably at the disabled settings in the client on my machine, I finally realised that the user options for allowing exclusion of files etc have to be enabled per client (which is actually what Robin said above, but didn't sink in to my brain). It is not sufficient to turn on "Preferences > Clients > Allow clients to: exclude items from backups" on the Retro server. You then have to go to each source and enable the options you want. 

  5. Is it possible to get Retrospect (11.5.3) to compress the catalog for a disk media backup set without doing a backup to the set or having the backup disks mounted? I have the catalog for last year's backups uncompressed and at 72BG I am sure I can save a useful amount of disk space by turning on compression in the media set settings, but I doubt ticking the 'Keep Catalog compressed' button will trigger compression of the catalog. The disks containing backups are in the cupboard and I would prefer to avoid having to unmount this year's disks just to get the catalog compressed. 

     

    Thanks for any tips on how to get this done. 

    • Like 1
  6. I noticed that an overnight backup of my machine had copied a huge amount of data (17G compared to an expected 1G). Browsing the backed up files I saw a directory of temp files which I had listed under the Privacy tab in the client to prevent it being backed up. This exclusion had worked for dozens of backups until this most recent one. This only change which might have happened prior to this backup was that I added one more directory to the Privacy tab. Details: 10.5 server (running on OS X 10.7.5), 9.0.2 client (running under OS X 10.8.5), backing up to disk media.

     

    Related to this, I setup a windows machine for backup last week and added a directory to the Private tab, only to find it was backed up. Has anyone else seen the settings under the Privacy tab not being respected by Retrospect? Am I misunderstanding how the Privacy tab works?

     

    Another possible bug: in the OS X client, the list of directories under the Privacy tab is never enabled to allow a directory to be selected, regardless of whether the user has authenticated or not. This means there is no way to remove a directory from that list. 

     

     

    • Like 1
  7. Thanks, I've already tried stopping and restarting both the engine and the console. And I did a restore from a backup which was listed in the backups pane. Still nothing in the 'Retrieve...' dialog. The problem is that I want to restore a directory to an earlier date than what is shown in the listed backups. About doing the restore... If I do a restore from a point in time I get the same list of backups in the dialog, but the 'More backups...' button is inactive. 

  8. I have a disk media backup set with one member (a 6TB RAID) which according to the summary tab has 3363 backups and 11,504, 004 files. In the backups tab it shows me about 400 backups. When I click the 'Retrieve...' button I get an empty dialog (i.e. the other 2900 odd backups aren't shown). Any suggestions as to how to get to those other backups? This media set was recently rebuilt (following a groom-related crash) and it did show backups in the 'Retrieve' dialog immediately after the rebuild. Since then the machine has been doing backups with no crashes.

     

    thanks,

    Ron

  9. A suggestion following on from my question. Our 10.5 Retrospect is showing lots of log lines:

     

    Version 6.3 client incompatible with Mac OS X 10.8 and higher
    Version 6.3 client incompatible with Mac OS X 10.8 and higher
    Version 6.3 client incompatible with Mac OS X 10.8 and higher
    Version 6.3 client incompatible with Mac OS X 10.8 and higher
    Version 6.3 client incompatible with Mac OS X 10.8 and higher

     

    It would be really really good if each message included the client name, because I cannot see any way of getting the OS version via Retrospect. I am seeing far more of these log lines than we have client machines, let alone clients running OS X 10.8 or higher.

  10. We have two retrospect servers, one in each of our buildings, and clients are backed up to each server on different weekdays. One server is Retrospect 9, and the other is a new Retrospect 10.5 (upgraded today from Retrospect 8). The clients are OS X and windows, with a range of OS versions. New in the log for the retrospect 10 server is the message "Version 6.3 client incompatible with Mac OS X 10.8 and higher." This wasn't in the log of the Retro 8 server, but it strongly suggests I need to update our OS X 10.8 clients to a retro client higher than 6.3. Keeping in mind I need to maintain compatibility with our Retro 9 server, which client is recommended for OS X 10.8 machines? Based on my own trials I know the Retro 10 client gives an 'incompatible version' error when you try to log it into a retro 9 server.  

     

    thanks,

    Ron

    • Like 1
  11. Apologies if this is obvious or implicit in the documentation, but I could not find it addressed here in the forums. I have a mac mini running OS X 10.6.5 and Retrospect 8.2(399) with disk media backups on external drives. I am going to replace the mac with a new mac mini running OS X 10.8.5 and Retrospect 10.5.0 (145). I have moved the settings and catalogs from the old to the new machine (and these appear to be OK), but before I connect the external drives I want to confirm that Retro 10.5 will be able to read and write to the disk media sets on the external drives. I don't want to lose nearly a year's backups of many computers in the migration. 

     

    Thanks.

    Ron

    • Like 1
×
×
  • Create New...