Just curious how others are managing their Fastback jobs and dealing with performance. I have an Exchange server using LCR with 10 storage groups. I've found that I can't clump those all into one job, as this bogs down Fastback. Sometimes jobs abort. It seems that spreading the storage groups across multiple jobs works better.
Has anyone else experienced something similar? Is this common among D2D solutions? Anyone know of any best practices for Fastback?
Thanks.
jwoo
Has anyone else experienced something similar? Is this common among D2D solutions? Anyone know of any best practices for Fastback?
Thanks.
jwoo