cancel
Showing results for 
Search instead for 
Did you mean: 

storage usage when migrating a client to a different policy with the same storage unit

AlexeyF
Level 3

Hi

we had a client that was backed up within a policy "ABC" which was using a storage unit DSK_10

one day we migrated it to a policy "BCD" which uses the same storage unit DSK_10.

And the first full backup took 8 hours while previous lasted 15 minutes (thanks to the deduplication).

Now I wonder why it took so long to make the new full backup in policy "ABC" ?

Did NetBackup write all the client data to a new place ignoring the fact that most of the blocks resided already on this storage unit ?

1 ACCEPTED SOLUTION

Accepted Solutions

Michal_Mikulik1
Moderator
Moderator
Partner    VIP    Accredited Certified

Hello,

it was previously running 15 mins thanks to acceleration, not deduplication. After moving to a new policy, accelerator start point must be established again, thus the first full backup was running in a traditional (long lasting) way. Now it should take 15 mins again.

Regards

Michal

View solution in original post

5 REPLIES 5

Michal_Mikulik1
Moderator
Moderator
Partner    VIP    Accredited Certified

Hello,

it was previously running 15 mins thanks to acceleration, not deduplication. After moving to a new policy, accelerator start point must be established again, thus the first full backup was running in a traditional (long lasting) way. Now it should take 15 mins again.

Regards

Michal

Nicolai
Moderator
Moderator
Partner    VIP   

What Michal said :)

The accelerator log file has the name of the policy in it (as far as I recall). So new policy, new accelerator log file.

/Nicolai

thank you for the explanation, Michal. 

so after the first full backup with a new policy NetBackup will identifiy the blocks that are already present on the appliace and it will store only one set of data (1 Full backup and not 2), right ?

Michal_Mikulik1
Moderator
Moderator
Partner    VIP    Accredited Certified

Hello,

no, this characterizes deduplication, not acceleration. Here VMware (not NetBackup) will identify blocks changed from the last backup, send them to NetBackup, and NBU will assemble a new full. 

Regards

Michal

I mean there is one Full stored for the client in policy ABC and one Full in policy BCD

thanks to deduplication made on NetBackup appliance they will not occupy 2xFull but only 1xFull. is it correct ?