Hey All, has anyone noticed just how slow consistency checks are for larger volumes? I know that this seems to be a grin and bear it currently but it's a bit of a showstopper having to miss backups due to it.
In our case a volume on one of our file servers contains about 1.8TB of data (not exactly insanely huge) and the other night it bluescreened (now sorted) just before the back which then triggered DPM to start a consistency check, this took over 22hrs to complete which meant we missed the backup window completely and had no option but to wait it out. I've checked the usual bottlenecks (see link below for more) and we pretty much as good as we're going to get for speed on that side for connectivity server resource and disk speed as nothing is stretched at either end and we get good transfer rates.
I've been looking at ways to mitigate against it and we currently have one recovery point daily with multiple syncs (will syncs help without without a recovery point?) and have just been looking at and old reply from Mike Jacquet on this thread and there was a recommendation where possible to start using volume mount points as a workaround. Is this still one of the only options? We'd rather not have to undertake that level of work and cost on our file servers if we can help it.
Any info or experience of optimising CC's would be greatly appreciated as this kind of thing could seriously effect SLA's etc.