![]() * Mozy does not publish a guaranteed service availability. The 2xProtect option enables rapid restores for the most recent backup, however this will not be helpful if attempting to recover from a data corruption issue that spread to the last backups. * Even when using the restore by DVD, the restore process will take days not hours. * Mozy Sync does not have any features to enable file sharing with colleagues. * No password policy on Mozy Pro for businesses with less than 200 users. * There is no two factor authentication to provide additional security to online administrator authentication. * Mozy provides the 2xProtect option to allow local backups, in addition to online, to assist if you need to restore data quickly (only the most recent backup is available locally, historical backups are available online only) * Mozy provides a restore by DVD service for large data restores that cannot wait for Internet download (delivery time is 3 – 5 days). * The Mozy Data Shuttle provides a pragmatic method to achieve a first backup when your Internet connection will not suffice. * The entire Mozy business has successfully completed a SOC 1 SSAE 16 Type 2 audit which is a significant accomplishment. * Files are encrypted when stored at Mozy facilities, and you can chose to keep your encryption key, which means Mozy has no access to your files. I explain fully in a blog post,, but below are the key points. I've reached the conclusion that Mozy Pro may be suitable for businesses without rapid restore requirements, but you will need to compensate for poor password controls, and Mozy Sync will meet only the most basic of needs. Thread.I've been evaluating Mozy for business use over the last month. _currentMessage = _helper.Process(_currentMessage) //sets global _inProcess flag ![]() _currentMessage = (MyMessageType)_queueMessage.Body _queueMessage.Formatter = new BinaryMessageFormatter() _queueMessage = _queue.EndPeek(e.AsyncResult) ![]() Private void MessageReceived(object sender, PeekCompletedEventArgs e) _queue.Formatter = new BinaryMessageFormatter() _queue.PeekCompleted += new PeekCompletedEventHandler(MessageReceived) Throw new Exception(string.Format("'ReadyFormQueue()' returned null", _queueName)) If it should is there something else I should be looking for?Īny suggestions welcome! protected override void OnStart(string args) I assume OnStart fires when the server comes back up so the handler must get attached, but I am not clear whether message that were (a) already in the queue at re-boot or (b) arrive during re-boot will actually trigger the event ? Question: in OnStart the MessageRecieved function is attached to the PeekCompleted event. My first inclination is to think that there is something in the OnStart handler that isn't getting hit when the server comes back up and I am attempting to sort out the Logs (another story) but Windows Services and threading are not my normal domain so I am hoping someone can point me in the right direction.īelow are the OnStart Handler and message handling function, stripped inconsequential stuff. The service is problematic - whenever Windows Update requires a server reboot (so like almost always) the Service comes back up in a "Started" condition but has to be REstarted manually or the messages just pile up in the queue. I am working with a legacy Windows Service that reads messages from a private MSMQ queue processes them (does some database work, sends some emails) and then waits for the next message (PeekCompleted)
0 Comments
Leave a Reply. |