UNSOLVED

oldhercules

updated

10 years ago

O

oldhercules

1 Rookie

116 Posts

0

1652

April 22nd, 2016 13:00

savegroup cloning, APPLICATION ss

Hello,

What do you think, is it normal that networker is not cloning some APPLICATION Exchange savesets when I use savegroup initiated cloning?

Savesets like this: APPLICATIONS:\Microsoft Exchange 2010\Users_DB101 04/18/2016 05/18/2016 4  B are never cloned.

All other savesets related to the backup are cloned, savegrp ends successfully.

Do I need these 4 byte savesets to restore Exchange?

I have to run regular checks on my systems to search for type=Data Domain,validcopies=1 savesets and clone them manually because they are never cloned automatically. The bad news is that if I set a scheduled cloning for a pool for non-manual backups  it can cause that the cloning process(es) will create more than 1 copy: if the savegroup cloning phase runs in parallel with the scheduled 'pool cloning' then even if save set clone limit is set to 1 sometimes more copies are created - I guess the limit of the copies are evaluated at the beginning of cloning when the saveset list is examined + the savegroup doesn't cares about such limits.

Regards,

Istvan