IS2
Level 3
Joined 12 years ago
User Profile
User Widgets
Contributions
Re: Exchange 2010 "Out of page buffers"
Well, after a week of using the following configuration, I have had no problems. See previous post from 10/28 for more details on why this works. System and Infostore jobs are separated System - Full with incrementals using GRT and DEDUP storage Infostore - Full with incrementals using GRT and DISK storage1.6KViews0likes0CommentsRe: Exchange 2010 "Out of page buffers"
I should have mentioned that the 'differential' will not delete log files - by design. Since the differential contains everything since the last 'full', it needs to keep all the logs in case of a restore. Glad to hear the 'differential' is working for you.1.6KViews0likes0CommentsRe: Exchange 2010 "Out of page buffers"
Update - but not necessarily good news. For the past week I did the following with the indicated results: Separate the System and Information Store jobs into two jobs - GOOD Use “Differential” for the Information Store - Didn't make a difference and actually seemed to cause move issues when GRT was turned on. Use “Incremental” for the System - GOOD Do NOT allow the “Differential” and “Incremental” to run at the same time - MAKES SENSE Do NOT turn on Snapshotting (Advanced File Open) for the Information Store job - UNNECESSARY - In reality, BE uses Microsoft VSS automatically on Exchange backups. Turn on GRT for both the System and Information Store jobs - BAD - on the Infostore backups, using GRT created different issues. The Symantec Tech I talked to recommended that we simply get away from backing up the Infostore using Dedup. While not necessarily documented, using Dedup for Exchange, due to the overhead required, isn't an efficientway to go. So, what I am now doing, and it appears to work fine, is the following: System and Infostore jobs are separated System - Full with incrementals using GRT and DEDUP storage Infostore - Full with incrementals using GRT and DISK storage The obvious downside is the need to use a lot more disk. I like to keep four weeks of fulls and two weeks of incrementals. I won't be able to do that with this technique. So, I've also added a "Duplicate to Tape" step on the Infostore so that I can have access to older copies of the Infostore. Here are some of the salient points of my discusison with Symantec Technical Support: Because of the dynamic nature of the Exchange database, Dedup storage is not the recommended storage media for Exchange databases. Even though my results were pretty good using Dedup, apparently the BE resources necessary to determine what needs to be written to Dedup are substantial. And, the further away you get from the full backup, the greater the resource requirement becomes - which may be why the incremental jobs die after a few days. One possible solution (which I am not going to try) is to run full backups every night using GRT and Dedup. I may try this at some point, but I'm going to give the Disk backup a shot first. Using Disk instead of Dedup will provide for much faster recovery time for an individual mailbox or mailbox items. Be sure that your Exchange database maintenance jobs do not run at the same time the backup is running. This is documented in the Best Practices Guide. Finally, just in case you haven't seen this link, it's worth checking out. It doesn't really help this situation (unless the documenation has been updated), but there are some good things to consider. http://www.symantec.com/business/support/index?page=content&id=HOWTO74626 I will update this post next weekend after I've had a chance to let a full week go by using the solution outlined above.4KViews0likes0CommentsRe: Exchange 2010 "Out of page buffers"
Update: Symantec Tier 3 support has suggested the following (which I will try for a week). Separate the System and Information Store jobs into two jobs Use “Differential” for the Information Store Use “Incremental” for the System Do NOT allow the “Differential” and “Incremental” to run at the same time Do NOT turn on Snapshotting (Advanced File Open) for the Information Store job Turn on GRT for both the System and Information Store jobs I’ll give this a shot and let you all know how it works. Obviously, we won’t know much until the end of next week.1.6KViews0likes0CommentsRe: Exchange 2010 "Out of page buffers"
Symantec is escalating the issue on Monday. In the meantime, I was successful this week by simply turning off the GRT option. This won't work for me long-term, but at least I have a backup of the Exchange Server in case something goes wrong.1.6KViews0likes0CommentsRe: Exchange 2010 "Out of page buffers"
Sorry about the delay in posting. I am working with with Symantec Tech Support. They started debug and have collected two days worth of logs. A couple of interesting items to report... When we started using the Troubleshooting tool, it found that the ASR Writer was in a failed stated. After a bit more research, we found that this seems to occur only when the Symantec Backup process begins. On servers where I do not run BE2012, I do not have this issue. The only way to get the ASR Write into a 'stable' state is to restart the server. If you want to run the troubleshooting tool, go to "Backup Exec button" --> Technical Support --> Run the support tool..." Also, changing the Exchange Server backup to NOT use GRT seems to have worked. It's already Thursday and the Exchange job has not failed. This is not a good long-term solution, but it's better (for me) to not have the job fail. The Tech Support person did have me change my default snapshot technology option on the backup job(AdvancedFile Open)from "Automatic" to "Microsoft VSS..." then pick "System - ". I'll post the results next week. Finally, I am also beginning to have an issue where periodically BE2012 reports that one of my Windows Agents is not the right version. When I look at the versions, all is fine... I have to reinstall the Agent to resolve this issue. Is that something any of you are also dealing with?2.1KViews0likes0CommentsRe: Exchange 2010 "Out of page buffers"
The change to a combination of Dedup (full) and Disk (incremental) did not solve the issue. I had my typical Wednesday issue this morning. For now, I'll move back to all disk. I will however call Symantec today and see what they can do. So far, they have not had a solution for the issue. I hope we now have enough information to help them resolve the problem. I'll post how the discussion went.2.1KViews0likes0CommentsRe: Exchange 2010 "Out of page buffers"
Not surprisingly, the issue is back... The full backup on Friday night ran fine as did the incrementals on Sunday and Monday. The Tuesday night incremental however failed with the "Out of page buffers" error again. Needless to say, this is frustrating. My next test is to run the full backups using dedup and the incrementals using disk storage.2.1KViews0likes0CommentsRe: Exchange 2010 "Out of page buffers"
Changing the storage media from dedup to disk worked like a charm. We had no issues this week (first time in months). I'm moving back to dedup this week but changing the schedule so that the Exchange backup runs on its own. I currently allow four concurrent jobs on the dedup storage media an onlyone on the disk media. I'm wondering if the Exchange job exposes a resource issue that I don't have otherwise.2.1KViews0likes0CommentsRe: Exchange 2010 "Out of page buffers"
I did check for the update and there was nothing available for our installation - but thank you for the info... An update... The change to "server-side" dedup did not appear to work. However, it wasn't a perfect test because we had two issues with the Exchange backup this week. What I am going to do this week is move the Exchange backup from dedup storage to disk storage. Given that we didn't have this situation prior to moving to dedup, I want to prove that it works in exactly the same environment with disk storage. If it does, I'll move it back to dedup and see what happens. I'll check back by the end of the week to update our status.2.1KViews0likes0Comments