That being said I upgraded to 2016 a few days after release so maybe the Snapshot issue has been resolved.Īpologies if it seems slightly off topic, but if I go to restore, then exchange, then try to restore individual mailbox items, then it is trying to work from the snapshot from the day before we upgraded. I changed it back to Standard Processing Method. That setting is under Configuration and Settings>Backup Exec Settings>Virtual Machines. We don't use Snapshots at all so It took me a few days to notice after seeing that my disk space was decreasing fast. It would leave Snapshots running on all my hyper-v hosts even after the backup finished. Let me know if either of those don't fix it and I'll look a little closer at my settings.Īfter the upgrade I had issues with a new faster processing method they introduced for incremental backups. Also under the job and Instant GRT I have "Run a Full Catalog operation as a separate job immediately after the backup job finishes" selected. I think I had to turn that off for GRT to work with Exchange. Also I would turn off compression and encryption for the exchange backup and see if that makes a difference. I remember reading something about BE Exec doesn't like GRT with Exchange and AD on the same server. Do you have active directory on the same server as exchange? Try a backup with GRT turned off for active directory objects. I did get it too work but I can't remember exactly what I had to do. I had this same problem after upgrading from 2014 to 2016.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |