cancel
Showing results for 
Search instead for 
Did you mean: 

BE 2014 Exch2013 Database size erratic???

fv
Level 3
Partner

Hi All.

 

OS is Server2012 R2.

(not an option when creating Forum Discussion)

I have a weird behavior when backing up Exchange databases.

The setup is to move items older that 6 months to archive, and delete "Deleted items" older than 14 days in primary database.

That should give some movement, but this is waaaaaaaaaaaaaaaay to much.

100-130 GB per day up AND down, on both databases.

Both DB go up and down same day, so movement of data is not the cause.

What is happening?

  •  
1 ACCEPTED SOLUTION

Accepted Solutions

VJware
Level 6
Employee Accredited Certified

Thanks for the logs. If you compare the size of "Mailbox Arkiv", this is what you get from the job logs :-

17 Mar - Processed 172444103086 bytes
18 Mar - Processed 172565546238 bytes

As you can see there is hardly any variance. The size which is displayed in the UI can be due to either one of these 2 reasons -

1) Maybe a cosmetic issue

2) Delayed Cataloging of backup sets from multiple backup is processed. http://www.symantec.com/business/support/index?page=content&id=HOWTO99624

 

View solution in original post

12 REPLIES 12

fv
Level 3
Partner

Same problem in BE 2012 and 2014

 

VJware
Level 6
Employee Accredited Certified

If other resources are being backed up along with the Exchange resources, would first recommend to split the backup jobs. Secondly, do ensure AOFO is not enabled for the Exchange backup.

Setup a new full Exchange backup job without AOFO and without GRT. Once this backup completes, setup a scheduled Exchange backup job again without AOFO but with GRT enabled. Run the backup and observe the size.

fv
Level 3
Partner

Sorry, I've had problems logging in.

AOFO removed, Client side dedup removed, no change.

Not keen on removing GRT. :(

 

 

VJware
Level 6
Employee Accredited Certified

Would you pls attach or PM the jobs for the 17th & the 18th ? Thanks.

The suggestion to disable GRT was only for an one-time job and not to disable it completely.

fv
Level 3
Partner

Just noticed the dates are weird on this pic.

I'm running mixed backup.

Disks and System state is daily inc, monthly and yearly full.

Databases are daily full.

Backupsets (dates) for disks and system state is OK.

Job is currently running, i'll check and/or post when done.

fv
Level 3
Partner

Not quite awake, sorry.

Log for 17.

fv
Level 3
Partner

Log for 18.

VJware
Level 6
Employee Accredited Certified

Thanks for the logs. If you compare the size of "Mailbox Arkiv", this is what you get from the job logs :-

17 Mar - Processed 172444103086 bytes
18 Mar - Processed 172565546238 bytes

As you can see there is hardly any variance. The size which is displayed in the UI can be due to either one of these 2 reasons -

1) Maybe a cosmetic issue

2) Delayed Cataloging of backup sets from multiple backup is processed. http://www.symantec.com/business/support/index?page=content&id=HOWTO99624

 

fv
Level 3
Partner

I do not use Delayed Catalogging. (not at purpose anyway)

I'll your answer as (propably) solution, and hope it gets fixed at some point.

fv
Level 3
Partner

Ok, now it makes some sort of sense.

I kept an eye on things this time.

Here's what happens: (I assume)

After the Backup job, before Catalog, Archive was 161 GB, and Databse was 242 GB

After Catalog, Archive is 321 GB and Database is still 242 GB

 

The erratic behaviour then occours because:

Sometimes Catalog fails, and does not correct the size.

This is probably hard to fix.

Sometimes Catalog does not correct the size, but makes a new BackupSet entry.

This is an error, that should be addressed.

Screenshots in route.

fv
Level 3
Partner

Before Catalog

fv
Level 3
Partner

After Catalog