Does anyone know what this means? in Professional Posted December 15, 2017 · Edited December 31, 2017 by DavidHertzberg It's Borrowed Big New Disk, not Borrowed Big New Backup Set; because scenario 2 in fourth post in thread is only possible per P.S., modified third paragraph · Report reply On 12/14/2017 at 11:27 AM, JohnW said: So I have been told by you and another that I should post to TS to resolve my problem. I did that. I just wanted to know exactly what I asked. The answer seems to be that nobody who has ever posted to these Forums knows what the message means, apparently because nobody has ever seen it before. IMHO that is because nobody has tried to do what you are trying to do, which is to expand the Use At Most space for an existing Member on a volume which also has Members of other Backup Sets. Nobody has tried to do that because it is just as easy to add a new Member of a Backup Set on the same volume, assuming the space is available. And the space has usually not been available on the same volume prior to recently, because there had not until recently been a rapid expansion in the size of a disk available at a particular price—what I have referred to in Scenario 1 in the fourth post in this thread as the Big New Disk. I just a few minutes ago thought of a third possible Scenario 2 explanation of why you are trying to expand the Use At Most space for an existing Member. It is that you are the Retrospect consultant for an installation which doesn't have an on-site backup administrator capable of adding a new Member to an existing Backup Set, or which doesn't have such an administrator on-site when the installation's backup scripts—each using a different Backup Set—are run. This would explain why you are so reluctant to explain what you are trying to do and why you are trying to do it. My latest suggestion is that you combine my Scenario 2 solution in the fourth post in this thread, as I modified it in the P.S., with the Borrowed Big New Disk I suggested in my Scenario 1 solution. You would follow a separate set of steps for each Backup Set:  Transfer Backup Set from old Backup Set to equivalent new Backup Set on Borrowed Big New Disk,  increase space for the only Member of equivalent new Backup Set,  delete the only Member of old Backup Set and add a new Member—with the same increased space—for the same old Backup Set on Big New Disk,  Transfer Backup Set from equivalent new Backup Set to old Backup Set—whose only Member would be on Big New Disk,  delete equivalent new Backup Set's only Member—which would be on Borrowed Big New Disk—and then delete equivalent new Backup Set itself. With this set of steps there would be only one Backup Set at a time on Borrowed Big New Disk, so you wouldn't get the message when expanding the Member; also Borrowed Big New Disk would only have to be big enough for the largest expanded Member of any equivalent new Backup Set, so it would only have to be Borrowed Not-So-Big New Disk. Actually you wouldn't even have to do any Member expansions on Borrowed Not-So-Big New Disk; you would just have to create the only Member of the equivalent new Backup Set with the size you had wanted to expand it to. And now for a moralistic message: When you are describing a Retrospect problem on these Forums, don't hesitate to explain the real-world problem underlying it. You can pick a "handle" that doesn't identify yourself if you are a consultant; you can even pick a "handle" that conceals the fact that you are a woman—which I suspect many of the posters on these Forums are. If you describe your real-world problem sufficiently well, it's likely that someone on these Forums will be able to solve it by thinking of an approach that wouldn't occur to you—possibly based on a better knowledge of certain features of Retrospect. Here's an example from about 6 months ago.