![]() The link somewhere about MS not fully supporting a snapshot based backup of Exchange is also a little disconcerting, but I honestly won't mind that as long as I can get it backing up smoothly, and without waiting for an eternity for a snapshot to be 'deleted. These options seem mostly obvious, but with something as critical as Exchange, I think it's understandable that some are a little nervous about backing it up properly. ![]() Would the defaults listed above, with the application aware processing set, be fine for 99% of Exchange setups?Īgree that it'd be nice to see a best practice doc for Exchange. When mounting an Exchange database, Veeam Explorer for Microsoft Exchange replays relevant log files which may significantly increase time needed for mount operation in case there is a lot of logs to replay. Under settings for that, I have the 1st two radio buttons set (by default, it seems) "Require successful application processing," and "Truncate logs on Successful backup Only." I currently have Application Aware Processing set. Which is best for which situation? Is one better for a system with circular logging, for example, while another may not be? Questions on the settings, which is mainly why I'm commenting here. ![]() ![]() Been hiding out, trying to absorb as much as I can, but have to ask, since I'm not clear on the above, and cannot seem to find a clear answer. I'm very new, and even newer to the forums. The logs can be truncated after every backup job, every successful backup or not truncated at all. VB&R provides advanced options for controlling truncation of transaction logs so that you can ensure correct backup of applications that use transaction logs. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |