I have a protection group that includes several directories on the E:\ volume 
of a database server. The database files themselves are about 185GB and are 
located in E:\Databases, and several other files totaling about 600MB are in 
various other directories on E:\, including some located in 
E:\Databases\Connections (I didn't set it up this way, but that's the way it 
is).

The PG backs up the databases as a SQL Server, and other files using Volume 
backup. In the PG I have explicitly excluded E:\Databases (to avoid backing 
up the DB files a second time) and included E:\Databases\Connections.

DPM allocates over 274GB of space for the E:\ volume, even though the actual 
data being backed up is only 600MB. I presume it's doing this because there 
are other large files on it, even though they are not being backed up. Well, 
they are being backed up, but they are backed up as a SQL Server and each DB 
gets its own volume which is sized appropriately.

The problem is that DPM is allocating space for the E:\ volume based on the 
total size of the files on it, and not just the size of the files being 
backed up. This means I'm wasting over 273GB of space that will never be used.

I also tried excluding .ldf and .mdf files, but it still allocates the full 
274GB for the 600MB of files actually being backed up.

I am also dealing with this allocation issue for files.  I just want
to backup a quickbooks directory that is about 500MB, but it is
requiring 12 GB allocation, I think because I have an excluded
subdirectory with 8 GB in it.


On May 7, 8:08=A0am, Daniel Segel
<DanielSe...@discussions.microsoft.com> wrote:
> I have a protection group that includes several directories on the E:\ vo=
lume
> of a database server. The database files themselves are about 185GB and a=
re
> located in E:\Databases, and several other files totaling about 600MB are=
 in
> various other directories on E:\, including some located in
> E:\Databases\Connections (I didn't set it up this way, but that's the way=
 it
> is).
>
> The PG backs up the databases as a SQL Server, and other files using Volu=
me
> backup. In the PG I have explicitly excluded E:\Databases (to avoid backi=
ng
> up the DB files a second time) and included E:\Databases\Connections.
>
> DPM allocates over 274GB of space for the E:\ volume, even though the act=
ual
> data being backed up is only 600MB. I presume it's doing this because the=
re
> are other large files on it, even though they are not being backed up. We=
ll,
> they are being backed up, but they are backed up as a SQL Server and each=
 DB
> gets its own volume which is sized appropriately.
>
> The problem is that DPM is allocating space for the E:\ volume based on t=
he
> total size of the files on it, and not just the size of the files being
> backed up. This means I'm wasting over 273GB of space that will never be =
used.
>
> I also tried excluding .ldf and .mdf files, but it still allocates the fu=
ll
> 274GB for the 600MB of files actually being backed up.

    The allocation is not just based on how much files to be protected, but 
rather when any volumes directories are protected, those volumes will have a 
growth ability up to the max size of the volumes free space. Hence while 
allocating disk space, DPM considers the max protectable data under the 
volume hence it allocates 1.5 times of the protectable data. To avoid 
running into this, you can use modify the disk allocations at the time of 
protection group creation manually or by clicking on the calculate size link 
given in the Disk allocation wizard.

Thanks,
Praveen D [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.

"Ken" <kgarello@gmail.com> wrote in message 
news:e9ecf4e4-432d-49a0-8319-9a09558ea766@n37g2000prc.googlegroups.com...
> I am also dealing with this allocation issue for files.  I just want
> to backup a quickbooks directory that is about 500MB, but it is
> requiring 12 GB allocation, I think because I have an excluded
> subdirectory with 8 GB in it.
>
>
> On May 7, 8:08 am, Daniel Segel
> <DanielSe...@discussions.microsoft.com> wrote:
>> I have a protection group that includes several directories on the E:\ 
>> volume
>> of a database server. The database files themselves are about 185GB and 
>> are
>> located in E:\Databases, and several other files totaling about 600MB are 
>> in
>> various other directories on E:\, including some located in
>> E:\Databases\Connections (I didn't set it up this way, but that's the way 
>> it
>> is).
>>
>> The PG backs up the databases as a SQL Server, and other files using 
>> Volume
>> backup. In the PG I have explicitly excluded E:\Databases (to avoid 
>> backing
>> up the DB files a second time) and included E:\Databases\Connections.
>>
>> DPM allocates over 274GB of space for the E:\ volume, even though the 
>> actual
>> data being backed up is only 600MB. I presume it's doing this because 
>> there
>> are other large files on it, even though they are not being backed up. 
>> Well,
>> they are being backed up, but they are backed up as a SQL Server and each 
>> DB
>> gets its own volume which is sized appropriately.
>>
>> The problem is that DPM is allocating space for the E:\ volume based on 
>> the
>> total size of the files on it, and not just the size of the files being
>> backed up. This means I'm wasting over 273GB of space that will never be 
>> used.
>>
>> I also tried excluding .ldf and .mdf files, but it still allocates the 
>> full
>> 274GB for the 600MB of files actually being backed up.
> 

The quickbooks directory that I included  is 500 MB

1.5 * 500 =3D 750 MB correct?

as I stated in the above message, it appears that it is calculating
the entire directory tree, even though I excluded it.
Your explanation below does not account for this.

Is this desired behavior?

Thanks

Ken

On May 11, 4:42=A0am, "Praveen D [MSFT]" <praveend...@hotmail.com>
wrote:
> =A0 =A0 The allocation is not just based on how much files to be protecte=
d, but
> rather when any volumes directories are protected, those volumes will hav=
e a
> growth ability up to the max size of the volumes free space. Hence while
> allocating disk space, DPM considers the max protectable data under the
> volume hence it allocates 1.5 times of the protectable data. To avoid
> running into this, you can use modify the disk allocations at the time of
> protection group creation manually or by clicking on the calculate size l=
ink
> given in the Disk allocation wizard.
>
> Thanks,
> Praveen D [MSFT]
> This posting is provided "AS IS" with no warranties, and confers no right=
s.
>
> "Ken" <kgare...@gmail.com> wrote in message
>
> news:e9ecf4e4-432d-49a0-8319-9a09558ea766@n37g2000prc.googlegroups.com...
>
>
>
> > I am also dealing with this allocation issue for files. =A0I just want
> > to backup a quickbooks directory that is about 500MB, but it is
> > requiring 12 GB allocation, I think because I have an excluded
> > subdirectory with 8 GB in it.
>
> > On May 7, 8:08 am, Daniel Segel
> > <DanielSe...@discussions.microsoft.com> wrote:
> >> I have a protection group that includes several directories on the E:\
> >> volume
> >> of a database server. The database files themselves are about 185GB an=
d
> >> are
> >> located in E:\Databases, and several other files totaling about 600MB =
are
> >> in
> >> various other directories on E:\, including some located in
> >> E:\Databases\Connections (I didn't set it up this way, but that's the =
way
> >> it
> >> is).
>
> >> The PG backs up the databases as a SQL Server, and other files using
> >> Volume
> >> backup. In the PG I have explicitly excluded E:\Databases (to avoid
> >> backing
> >> up the DB files a second time) and included E:\Databases\Connections.
>
> >> DPM allocates over 274GB of space for the E:\ volume, even though the
> >> actual
> >> data being backed up is only 600MB. I presume it's doing this because
> >> there
> >> are other large files on it, even though they are not being backed up.
> >> Well,
> >> they are being backed up, but they are backed up as a SQL Server and e=
ach
> >> DB
> >> gets its own volume which is sized appropriately.
>
> >> The problem is that DPM is allocating space for the E:\ volume based o=
n
> >> the
> >> total size of the files on it, and not just the size of the files bein=
g
> >> backed up. This means I'm wasting over 273GB of space that will never =
be
> >> used.
>
> >> I also tried excluding .ldf and .mdf files, but it still allocates the
> >> full
> >> 274GB for the 600MB of files actually being backed up.- Hide quoted te=
xt -
>
> - Show quoted text -