Jump to content

kolohe280

Members
  • Content count

    3
  • Joined

  • Last visited

Community Reputation

0 Neutral

About kolohe280

  • Rank
    Newbie

Recent Profile Visitors

29 profile views
  1. kolohe280

    Can't add more storage to a backup set

    Unless you are the owner of the forum (which I'm pretty sure you're not), please don't take it upon yourself to suggest "housekeeping details" to me. The "genesis" of my user name is of no concern, nor is my location or when I created a userid on this forum. And, in today's environment, asking a person for their gender is just plain dangerous. I opened a ticket with support on this issue. It was accepted, which surprised me since I'm not paying for maintenance.
  2. kolohe280

    Can't add more storage to a backup set

    Well, duh. I should have mentioned all of that. Sorry. I am not running an ancient version of Retrospect - in fact I am running 16.6 on Windows 10 Pro. I did take a look at the volumes database and cleaned it up since it seems that the failures with trying to connect to the new backup target left some clutter in there. That, however, did not solve the problem. Regarding the not accessible message - no error code - it's in a popup. However, the operations log does show a message "TVol::Set: no volume name" which makes me think that the volume isn't accessible because the particular piece of code that adds members to existing backup sets neglected to pass that information to the piece of code that actually sets it up. It only seems to happen with UNC specified volumes. I can add local disks all day and no problems. Right now, I'm thinking that this is yet another bug that was added when 16.0 came out. I've got two tickets open for serious problems with the storage group feature that have been open since March! They've admitted that one is a major design flaw, and they were working with me on the other problem for a while and then stopped just saying that it had been sent to Engineering. My confidence in the product is pretty low right now. I've had to do a crazy number of catalog rebuilds on the NAS backup set since 16.0 came out due to crashes. And, if they fix the 16.0 problems in 17.0, I'll get to pay for the fixes!!
  3. I have a NAS with 2 RAID5 arrays. I backup to one of them on a share called Online_Backup. I wanted to add some more space to that backup set, so I created a second share on the other RAID array and called it Online_Backup_2. When I tried to add the second member to the backup set, it went through the entire dialog (it was able to see how much space is available on that array), and when I clicked OK I got an error "The disk is not accessible". However, if I create a new backup set and point it to the new share, everything works fine. I have had no problem creating multiple member storage groups on USB drives. Ideas?
×