Jump to content

Member lost / damaged problem


Recommended Posts

We've got a disk to disk to tape backup schema, and our current disk backup sets span two members.

 

I recently had the second member of a backup set fail, so I marked it as lost / damaged, and said "skip this member", installed a new disk and added it as a third member of the set. Fine- it looks like the backups picked up where they left off, and I'm trusting that it re-backed up the files that were on the failed drive.

 

However, when I went to do a tape transfer of most recent snapshots, Retrospect prompted me to provide the missing / failed member, and since I could not provide it the script terminated.

 

It seems to me that if a member is marked as missing / unavailable, it should never be requested. Or am I doing something wrong? We're running 7.5.508 single server on windows xp.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...