Moving Retrospect backup set

[jamesiporter]

No, I deleted it. But I created this copy by drag and drop in the finder. Then moved it to an existing Retrospect folder. Are you sure it's useless? I don't mind starting over if necessary, but would like to know if this is dead in the water and why the procedure I followed won't work (as I thought it should).

 

 

[CallMeDave]

I don't know if it's snookered beyond repair, but I see a folder named "[color:red]JSPORT-NewerTech-090.03.10[/color] and inside that folder is a folder named [color:red]JSPORT-NewerTech-090.03.10[/color] and inside that is the first Member of a Media Set.

 

Why do you have two nested folders with the same name?

[jamesiporter]

Search me! For some reason I keep ending up with these nested folders, usually numbered (-1, -2, etc.). I thought it was a Retrospect thing. And I don't even play snooker.

Edited September 17, 2010 by Guest

[CallMeDave]

I thought it was a Retrospect thing.

 

There is a nasty bug where Retrospect creates new, improperly nested Member folders, but I thought you'd see "2-FooMediaSet" if it were biting.

 

Still, if things are gonna work, you'll probably need to have:

 

/ (volume root)

->Retrospect

-->FooMediaSet

--->1-FooMediaSet

---->All Your .rdb files

[jamesiporter]

Actually, I do: 2-FooMediaSet, then 3-, 4-, etc. I was wondering why. (In just about every Backup Script I have running.)

 

It happens sometimes that a script cannot recognize a Media Set it previously recognized and if you select what was the old Media Set it creates a new nested, n+1-M.S. But I haven't tracked all the ways this comes about. That's how one happened tonight, I know this. Doesn't bother me so long as the whole thing works if I need to bring a file or folder back from the dead.