1. If your client backups are huge because of allot of local data, consider pointing (moving) them to separate drive. It can be a standalone, RAID, or a large drive such as a 3T drive. The size of the destination drive is not limited for the client backups (only the server backup is limited), I store my client backups on a 4T RAID 5 Partition which provides redundancy I am looking for with no concerns of size limitations. If you really need to have a backup of a backup, then consider a mirror of two drives such as 2x2T, or even 2x3T drives dedicated for this task using the built in tools in the OS to create a mirror. (see link below). This way you clients are protected beyond what you had in V1 without the manual process of BDBB.
2. If you do the above and still find that your server backup and critical shares are still not large enough, again consider splitting off your critical data into a mirror of any size which will be in a sense folder duplication and remove it from the backup. For example, if you regularly have 1.5T of critical data, 1T of local backups, plus the server. This will not obviously fit on a 2T drive. One option would be to have 1 2T drive dedicated for client backups, 2x2t mirror for the data, and a 2T drive for server backup and "selective" shares such as documents or pictures (as a third copy).
I know that many of us wanted to pile everything together into one continuous stream, but rememeber that we did not have that in V1 either. We did not have the ability to backup the server at all and backing up our client backups required an add-in and a manual process that was painfully slow. If we break down each requirement carefully and look at our options, we will find that the limitations are workable and we can end up with a nice server experience. As a matter of fact, V2 is actually more capable and more flexible that V1 ever was if we start looking at what it can do rather at what it cant. As was the main point of the recent HSS podcast, planning is the key and with planning, there really are no limitations. As a reference, here is how I broke mine down which will shows I have much opportunity for growth.
Critical data - 2x2T mirror. Only two of the ultra critical shares are included in the backup (about 40 gigs) as third copy (more copies and protection that we had with V1 folder duplications)
Server backup - Dedicated 2T drive. Server OS, 40 gigs from above and misc other things from the RAID 5 partitions. Could have been a much smaller drive as 87% of it is free.
Client backups - Redirected to a 4T RAID partition (could be a separate drive mirror dedicated for client redundancy)and not included in the backups as it being protected by the RAID (or mirror) redundancy.
When you break it down, you will find that the data in most cases can be managed easily for 98% of the use cases. The last 2% will end up with different solutions. The point I am trying to make is that with a bit of planning you do not give anything up at all as a matter of fact you gain by going with V2 as all these task are automated and done without a single add-in.
Creating a mirror. These instructions work perfectly on WHS-2011 as I have tested it
http://www.howtogeek...p-in-windows-7/
