1. Lucid8 Digiscope Serial Port Numbers

Yes, eseutil and all other methods of recovery have failed. What I am referring to are products such as this: The demo version pulled up all mailboxes quickly so I purchased it. However, that was a mistake. It is a good product and is not a scam, but it is an indian company and they are telling me it is going to take 4-24 hours to process the order and then another 48 to get the license key, so I am looking for another solution that works just as well but gets me results faster. I have been down almost 24 hours now and this is not good.

This Konus 1301 Universal Digiscoping Adapter is a system that consists of three main components: a camera platform, a camera platform extension, and a smartphone holder. Those three components can be variously configured to allow a point-and-shoot camera or a smartphone to use a telescope or spotting scope as a telephoto le.

Recently there have been issues with our Exchange Backup. The backup admins are pointing to the fact that our Exchange server has the maintenance windows on the DBs during our backup windows. I'm not sure how I want to adjust this because we only have 2 Exchange DBs which are both around 1 TB in size. The backup of Exchange runs from 7PM - 11:00AM. The work day is from 8:00AM - 8:00PM weekdays. So there is literally no time that there isn't a backup or users on the system. MS documentation states that it should be done during the least amount of DB activity time.

This might give me a window of Sunday morning, but definitely not Daily as it runs now. Will this be a big issue? Any advice is appreciated. 1&2: Ok I understand why you have circular logging on, however with that should not be a long term methodology since there are ramifications to consider. Check out this 3.

The issue with the backups not finishing is because you are using Brick level backups and; A: Brick level backups are notoriously unreliable B: The reason you are seeing all those connections and CPU spikes with the CAS server is because you are extracting ALL the email for each mailbox for the Brick Level backup via MAPI (same as outlook) and it all has to come through the CAS server. Think of it like this, what do you think would happen if you tried to extract ALL email from ALL mailboxes via Outlook?

It would take forever and cause all sorts of constraints on CPU, I/O, Storage and network bandwidth. Here is an older article on this as well aka DO NOT DO BRICK LEVEL BACKUPS they are horrendous. C: what you should be doing is just the Database level backups and then using the MS method to recover granular information i.e. RSG/RDB which work but are a bit clunky IMO or use a GUI based powerful tool like DigiScope to open the offline copy/backup of an EDB to get the granular information you need. HOPEFULLY you are also doing a DB level backup since that will save your bacon in a nuclear type event i.e. Major crash, hardware issue etc, its faster and also allows you to recover granular if needed.

Troy Werelius Search, Recover, & Extract Mailboxes, Folders, & Email Items from Offline EDB's and Live Exchange Servers or Import/Migrate direct from Offline EDB to Any Production Exchange Server, even cross version i.e. 2003 - 2007 - 2010 with Lucid8's. Good suggestion in breaking up the databases into smaller ones as 'btasaf' suggested, however another thing you might consider is letting maintenance run for 24 hours on the least impactful day. For example if Sunday is your least busy day then set the maintenance window to run at all hours on Sunday. What this will do for you is IF a backup interrupts the maintenance process the maintenance will be interrupted during the backup time, but will then proceed once the backup is complete. This will cause some additional overhead to the server on Sunday but the impact will be less than if it occurred during a weekday. NOTE: if you have not been able to complete maintenance in some time you may also want to consider a wider window to allow maintenance i.e.

Perhaps Friday at 6PM until Monday at 8AM. This would be temporary of course but would get you to the place where maintenance was completed since I imagine based upon your description that it has been some time since a full online maintenance was able to complete. Once you get caught up then you should be able to suffice with using Sunday or another day to let it run all day without impacting your users greatly Troy Werelius Search, Recover, & Extract Mailboxes, Folders, & Email Items from Offline EDB's and Live Exchange Servers or Import/Migrate direct from Offline EDB to Any Production Exchange Server, even cross version i.e. 2003 - 2007 - 2010 with Lucid8's. Ok so lets step back here; 1.

A backup will NEVER have an issue due to maintenance running, its the other way around i.e. A Backup kicking off while maintenance is in process will stop the maintenance until the next scheduled time. NOTE: I do recall in the past that at least one person said that NetApp advised them to turn off online maintenance all together because it messed with the NetApp waffle system. To me that seemed like a ludicrous statement but IF you are relying on NetApp to do the backup it MIGHT be that they freak out during a backup if maintenance is running.

Not running nightly maintenance of course would have some ramifications but its easy enough to test that statement by disabling maintenance during the backup process and see what happens. That said please do read and reply to the questions below. Not sure where you are geographically but has Sunday come and gone since you made the last maintenance window change.

What are you using to do your backups, how often do they occur and what is the error message you are receiving. Troy Werelius Search, Recover, & Extract Mailboxes, Folders, & Email Items from Offline EDB's and Live Exchange Servers or Import/Migrate direct from Offline EDB to Any Production Exchange Server, even cross version i.e.

2003 - 2007 - 2010 with Lucid8's. The original thing I was being told was the backup admin felt that the Exchange maintenance routine was slowing down the backups and causing them not to complete within the backup window. He backed this up with statements from MS articles that said that the maintenance window should be run outside of user and backup hours because it could interfere with performance. Sunday has not come and gone, however since the schedule has been changed to Only Sunday the thought was it would not run during the backup window (to my knowledge it didn't) however it seems changing that setting did not improve backup performance. They are using a group of backup servers that are connected via FC to a robotic tape library. It uses the ArcServe family of backup software with the Exchange specific agents.

These are Exchange 2010 databases correct? You are using ArcServe to back them up 3. You are backing up to tape which has to in essence backup the EDB files from the VM across the LAN to the tape library. I highly doubt that this is an online maintenance issue and more than likely a bottleneck elsewhere, i.e. The VM host server, Network connection, Switch or the backup system itself. I know you said that everything else is running properly but how many 1TB files are being backed up during the process? A couple of other ideas are' 1.

You said that you have been cancelling the backups each night because they cannot finish correct? If so that the logs are not getting truncated and therefore are building up more and more each day meaning that there is more and more to backup each day and since you always kill the backup the issue gets worse and worse. So how many log files are there for these databases 2. I would check out # 1 above first since that is more than likely the issue but the other thing to do would be to check the overhead on the Exchange server, i.e. CPU, I/O and network bandwidth when the backup is running to see if anything is maxed out and therefore constraining the backup throughput. But again lets look at # 1 first. It wont be exactly apples to apples but IF you have the space available you might try dismounting one to the DB's and then copying one of the 1TB database files to an alternate location and see how quickly the backup of that file can be handled.

Lucid8 Digiscope Serial Port Numbers

BUT AGAIN lets look at # 1 first because I bet there are a ton of log files for each of the DB's and it may be so large that it just cannot complete in a timely fashion Troy Werelius Search, Recover, & Extract Mailboxes, Folders, & Email Items from Offline EDB's and Live Exchange Servers or Import/Migrate direct from Offline EDB to Any Production Exchange Server, even cross version i.e. 2003 - 2007 - 2010 with Lucid8's. Hello, I am the aforementioned 'backup admin'. The issue with doing disk to disk backup is lack of space currently. I do not have the space to allocate at the present.

Also, I don't see how this would help.since it doesn't seem to be bottlenecking when writing to tape.it seems to be bottlenecking in GETTING the data off the exchange server. The tape drive frequently has to pause its writing since its waiting for data. We had to enable circular logging due to the issue mentioned above.prior to enabling that we had that exact issue where the backups would just keep getting longer and longer every time we'd cancel. One other thing we cannot determine is that the ARCServe software only deploys an exchange specific agent to the DB server only, and not the CAS server.yet while the backup is running, the RPC client connector PIDs on the CAS server is consuming about 60% CPU constantly. It also shows thousands of connections seemingly to itself (using procexplorer we see connections from MCAS1 to MCAS1 (the name of the server). Soon as the backup is cancelled this all goes away.

You temporarily turned on circular logging to clean out the logs? Circular logging is off now? What type of backup are you doing, i.e. There is Database level backups and then Mailbox level backups.

If DB based backup then the CAS server should not be involved at all, HOWEVER if you are doing Mailbox Level backups then you would be going through the CAS server because in short its doing the equivalent of extracting every mailbox to PST. Doing a Mailbox level backup would also take a LOT longer and a TON of more space to backup vs just doing a DB level backup and then using RSG/RDB OR a 3rd party product like Lucid8's DigiScope to extract granular data from an offline copy/backup of the database Troy Werelius Search, Recover, & Extract Mailboxes, Folders, & Email Items from Offline EDB's and Live Exchange Servers or Import/Migrate direct from Offline EDB to Any Production Exchange Server, even cross version i.e. 2003 - 2007 - 2010 with Lucid8's. 1&2: Ok I understand why you have circular logging on, however with that should not be a long term methodology since there are ramifications to consider. Fallout 3 expansion pack xbox 360.

Check out this 3. The issue with the backups not finishing is because you are using Brick level backups and; A: Brick level backups are notoriously unreliable B: The reason you are seeing all those connections and CPU spikes with the CAS server is because you are extracting ALL the email for each mailbox for the Brick Level backup via MAPI (same as outlook) and it all has to come through the CAS server. Think of it like this, what do you think would happen if you tried to extract ALL email from ALL mailboxes via Outlook? It would take forever and cause all sorts of constraints on CPU, I/O, Storage and network bandwidth. Here is an older article on this as well aka DO NOT DO BRICK LEVEL BACKUPS they are horrendous. C: what you should be doing is just the Database level backups and then using the MS method to recover granular information i.e.

RSG/RDB which work but are a bit clunky IMO or use a GUI based powerful tool like DigiScope to open the offline copy/backup of an EDB to get the granular information you need. HOPEFULLY you are also doing a DB level backup since that will save your bacon in a nuclear type event i.e. Major crash, hardware issue etc, its faster and also allows you to recover granular if needed. Troy Werelius Search, Recover, & Extract Mailboxes, Folders, & Email Items from Offline EDB's and Live Exchange Servers or Import/Migrate direct from Offline EDB to Any Production Exchange Server, even cross version i.e. 2003 - 2007 - 2010 with Lucid8's. So to recap I would recommend 1. DO NOT DO BRICK LEVEL BACKUPS 2.

DO DATABASE LEVEL BACKUPS 3. Turn Off Circular Logging 4. Use one of the methods above to extract granular mailbox, folder and item level data from the database level backup when needed If you do the above the problems with backups never ending will go away and performance will increase across the board Troy Werelius Search, Recover, & Extract Mailboxes, Folders, & Email Items from Offline EDB's and Live Exchange Servers or Import/Migrate direct from Offline EDB to Any Production Exchange Server, even cross version i.e. 2003 - 2007 - 2010 with Lucid8's.