zer0aster Posted May 15, 2014 Report Share Posted May 15, 2014 I am having some problems rebuilding a media set from members located on two SMB NAS shares. So I want to move them to a couple of USB disks and so off the network. Unfortunately although the total size of my 2 USB disks is more than adequate (2x 4TB), one of the NAS shares that contains most of the data has 4.2TB of retrospect data. i.e. 200 GB more than will fit on either of the USB drives. I wondered whether, given that the rdb files that make up the data are in 630 MB chunks, can I redistribute them across the 2 USB disks and still have a chance of rebuilding a media set out of them? 3 Quote Link to comment Share on other sites More sharing options...
Lennart_T Posted May 15, 2014 Report Share Posted May 15, 2014 I think so. When rebuilding the media set, it finds which files there are on the first disk and then asks if there are any more member disks in this media set. Quote Link to comment Share on other sites More sharing options...
zer0aster Posted May 15, 2014 Author Report Share Posted May 15, 2014 Thanks, I'll give it a try then. Obviously not something I want to be doing. So many TBs of data not something one casually moves about. Quote Link to comment Share on other sites More sharing options...
zer0aster Posted May 15, 2014 Author Report Share Posted May 15, 2014 Further to my question about redistributing rdb files to new folders... In the directory structure created by Retrospect there is a single file in the Retrospect folder that contains the media set folders called "Backup Media". It is 0 kb and I guess just flags something to Retrospect. Any ideas what this is and whether I need to recreate it in my new folders on my USB disks? Quote Link to comment Share on other sites More sharing options...
twickland Posted May 20, 2014 Report Share Posted May 20, 2014 In my experience, Retrospect doesn't tolerate moving .rdb files to a different volume. I'll be interested to know if you have success. Quote Link to comment Share on other sites More sharing options...
Mayoff Posted May 20, 2014 Report Share Posted May 20, 2014 You can move the entire folder of .rdb files to another disk, but you will want to run a catalog rebuild after the files are moved. Make sure you bring the folders over along with the files. Quote Link to comment Share on other sites More sharing options...
dan.jordan Posted July 23, 2015 Report Share Posted July 23, 2015 A related question: If I have a backup set spread across two drives can I move, say, the last 5 RDB files from the first drive in the backup set to the 2nd drive in the backup set and then do a rebuild? (Note: I've have learning that this technique won't work if you take RDB files from the middle of the first drive in the backup set and move them to the 2nd drive in the backup set. Rebuild doesn't like that.) Quote Link to comment Share on other sites More sharing options...
Lennart_T Posted July 23, 2015 Report Share Posted July 23, 2015 In my experience, Retrospect doesn't tolerate moving .rdb files to a different volume. I'll be interested to know if you have success. A related question: If I have a backup set spread across two drives can I move, say, the last 5 RDB files from the first drive in the backup set to the 2nd drive in the backup set and then do a rebuild? You are on your own here. I don't understand the purpose of moving a few (or many) files to another disk. Quote Link to comment Share on other sites More sharing options...
dan.jordan Posted July 23, 2015 Report Share Posted July 23, 2015 The reason for wanting to do this is its a handy way (compared to rearranging things via Retrospect) to free up space on a disk that has become too full for defrag to run, for instance. The correct, longer term solution is of course to allocate space to Retrospect in such a way that there's *always* available space on the volume. I had failed to do so in the case of the one disk volume. My testing confirms your suspicion that this won't work. The rebuild announces that the first volume of the two volume backup set is either corrupt or is from another set, and kicks it out of the set. Ah, well. it's something I've wondered about for years. Next time I'll just transfer the backup set to a new backup set in which space has been properly allocated. Thanks for your response, Lennart. You've been a valuable member of the newsgroup. Quote Link to comment Share on other sites More sharing options...
Lennart_T Posted July 23, 2015 Report Share Posted July 23, 2015 Why do you want to defrag the drive in the first place? I run Ultradefrag on members that are very full. I have never seen it make any performance improvement in Retrospect. http://ultradefrag.sourceforge.net/en/index.html Quote Link to comment Share on other sites More sharing options...
dan.jordan Posted July 23, 2015 Report Share Posted July 23, 2015 The performance hit is on the defrag software, not Retrospect. Microsoft defrag want 15% free space to do its thing, Auslogics wants 10% free space. Otherwise they suggest not running them until that amount of space is available. Ultradefrag, at some point, will have the same problem, as indicated under General Usage in their FAQ. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.