Jump to content

mmsadmin

Members
  • Content count

    17
  • Joined

  • Last visited

Community Reputation

0 Neutral

About mmsadmin

  • Rank
    Occasional forum poster
  1. mmsadmin

    Disk Grooming versus Media Timeout

    Thank you Robin, With regard to #2, I don't think anyone has described this as being an issue. Obviously in order to groom a backup set, it (and all associated members) need to be present. However, if a backup script attempts to groom a backup set that is offline, it should time out and continue with the rest of the script. In the original posters scenario, I believe each hard disk he was using for backup was a single-member backup set.
  2. mmsadmin

    Disk Grooming versus Media Timeout

    Now that I've re-read this thread and thought about it even more, I realized that fixing the bug would partially solve the problem. If the media timeout feature actually terminated the script and allowed further scheduled items to execute, I could accomplish what I want by creating 2 identical backup scripts to run every day, each with it's own dedicated backup set assigned to it. However, this would cause me to receive a "backup failed" notification or something of that sort every day. But it would still be more acceptable than not having a backup at all. Ideally my original suggestion would probably work better, but I'll take whatever I can get.
  3. mmsadmin

    Disk Grooming versus Media Timeout

    So after I re-examined the "Media Timeout" feature in Retrospect today. The description of the feature is as follows: 'Terminate execution after waiting this interval when required media is unavailable.' According to this description, if I have 2 backup sets configured as a destination, and one is not available, the script would then terminate and the backup would not occur. So according to the description, the function is actually doing what it says. Although when I've tried to use it, it actually never timed out and terminated the script.. It just continued wait for user input indefinitely. And so I do believe there is a bug in this feature, but I don’t think fixing that bug will solve the problem we have because we want the script to continue; not terminate. No end-user or administrator can be expected to always guarantee the swapping of media on any specific day. If the person is not able to get to the office one day or has an emergency situation that precludes them from reconfiguring the backup, the program should still be backing up the system if there is any destination backup set available at that time. If the regular backup would handle destinations in the same manner as a proactive backup, it would. In other words, if multiple backup sets are configured as a destination, then the program should back up to whatever destination sets are available to it at that time and continue normally. This would allow administrators to implement an effective off-site rotation strategy while guaranteeing that there will always be a full backup of the systems in the event of a failure to swap media. I really hope that EMC will find a solution for this. Even if its in the form of an option or preference, it would allow me to sleep better at night knowing that I am always going to have a backup. Right now it's an administrative nightmare having to verify that the right backup drive was swapped in every day. If ever I am unable to for whatever reason, there is no backup that night, which is unacceptable.
  4. mmsadmin

    Curious

    Is Retrospect X going to be a free upgrade for us? I certainly hope so. It would be quite disconcerting to have shelled out all this money with promises of useful enhancements and bug fixes and then to be forced to pay even more to get them.
  5. I appreciate your suggestion about the recovery storage group Robin. However, the reason I am doing mailbox backups is because I have a public folder that is too large to be backed up and needs to be eliminated from the backup. The only way to do this is to deny the retrospect account access to that public folder, and do a mailbox backup. If you are really the Senior Manager of Worldwide Technical Support, then I urge you to please push the development team to at least fix these bugs that have been hampering users from doing rotating off-site backups and mailbox backups. I've spoken to someone from tech support before. He was condescending and insisted there was nothing wrong with retrospect. If I can't get help from the forums, and I can't get help from tech support, why am I paying such an enormous amount of money for yearly support?
  6. mmsadmin

    Curious

    Has anyones suggestions actually been implemented?
  7. mmsadmin

    Error -1101 and -1012

    I get these errors every day as well, and it causes my backup to be reported as "incomplete". When I tried to get support from EMC, I was told that there was corruption in my exchange database. However, I am very meticulous about maintaining my databases. There are no errors or corruption in them, but the errors still persist. The error messages reported by Retrospect do not give any indication of the message subject or related information that would assist in finding the problematic messages, and so the error never disappears (unless the user themselves delete the message, which is rare)
  8. Why didn't anyone ever respond to my post?
  9. Why is it taking EMC so long to fix this bug? When I spoke to tech suport, they actually INSISTED that retrospect DOESNT have this problem and that my installation was corrupted. Now I am surprised to see that you are acknowledging this as being a bug. This is also a problem when new users are added to exchange. They dont appear in the mailbox list unless the license is reinstalled. I actually reported this problem in December of 07. http://forums.dantz.com/showpost.php?post/72935/ Also I asked about this problem on the forum here but never received any response. http://forums.dantz.com/showtopic.php?tid/26231/ I pay for my yearly support like everyone else. I'm quite disappointed with it to say the least.
  10. mmsadmin

    Disk Grooming versus Media Timeout

    Don't hold your breath. I reported this problem back in December and still have no resolution. I need to have a FULL backup every single day, with an off-site backup as frequently as possible. The only way for me to accomplish this is to have 2 separate backup scripts and 2 backup sets that alternate running every other day, and swap the hard drive every day. If the wrong hard drive is ever plugged in, the backup doesn't get done, period. This is a really bad thing. One can't expect to be in the office every single day, and a business can't afford to be without a daily backup, so I rely on the email notifications to let me know if I ever forgot to swap the drive. I then have to remote into the retrospect server and reconfigure the script to allow the backup to continue that night. If I am not able to do that, the backup doesn't run at all. I'm really surprised that there isn't a new post about this every day. Are we really the only ones backing up to hard drives for off-site storage? Is everyone else so perfect that they never miss swapping the hard drive on any single day? If only the Media Timeout function would actually work, I wouldn't have this problem. I actually regret purchasing Retrospect for this very reason (and a few others). Proactive backup solves this problem, but causes other problems that are even worse. I require an email notification when backup is complete to let me know if there is a problem. With proactive backup and backing up individual exchange mailboxes, I have to weed through hundreds of emails each night to see if everything was backed up (because proactive sends a separate email for each mailbox). The proactive backup also takes much longer on my system than a regular backup, for whatever reason. But the quantity of e-mails received after each night requires too much administration and leaves too much room for error. And so I cannot use the proactive backup. Which leads me into the reason why I have to do individual exchange mailbox backups in the first place. I have a public folder that is too large to be backed up. The only way for me to exclude this folder from the backup is to do individual mailbox backups. And, of course, there is a bug with this as well. When a mailbox is deleted from exchange, retrospect still tries to back it up, even after its purged, causing the backup to report as failed. The mailbox has to be manually de-selected from the configuration. It also doesn't automatically back up new mailboxes when they are added to exchange (when doing individual mailbox backups). The only mailboxes that are ever backed up are the ones that are polled from exchange when the license is first installed. The only way to get new mailboxes to show up on the list, and get backed up, is to re-install the exchange license. So I have to reconfigure the backup every time someone is fired, and remember to re-install the exchange license every time someone new is hired. It's an administrative nightmare. All in all, when I spoke to tech support about my problems, He insisted that my installation was corrupted. However, even after reinstalling several times, I've still got the same problems. I was left with a very bad taste in my mouth from this. http://forums.dantz.com/showpost.php?post/72935/
  11. mmsadmin

    Feature Requests

    I followed those instructions to the T back when I installed retrospect. The new mailboxes are showing up UNhighlighted in the volume tab of the client config, which explains why they arent being backed up automatically.
  12. I've been doing mailbox backups for about a week now, and dealing with the errors and warnings to test how it works in my environment. In my testing, new mailboxes added to Exchange are not automatically backed up; they remain unhighlighted in the volume tab of the client config. Deleted users never disappeared from the volume list (even after the mailbox was purged). Deleted/purged mailboxes received this error: - [Date & Time] Copying [Deleted/Purged Mailbox Name] on [Exchange Server Name] Scanning incomplete, error -3405 (unknown) Disabled users mailboxes received this error: - [Date & Time] Copying [Disabled Users Mailbox Name] on [Exchange Server Name] Retrospect error code error -3407 (unexpected provider error) Reported by function kMsg_DirScan Mailbox provider error. There is a problem connecting to the mailbox. Check: 1. Microsoft Exchange may not be running. 2. The mailbox may not exist. If the mailbox has been deleted, this is normal. 3. The mailbox store for this mailbox may not be mounted. Check its status in the Exchange manager. Scanning incomplete, error -3407 (unexpected provider error) Various other active mailboxes receive warnings similar to this one below, and I am unable to locate the items based on the given name, and so I am unable to correct the problem: - [Date & Time] Copying [Mailbox Name] on [Exchange Server Name] File "[Mailbox Name]\[Folder]\00000000e16894cfd668d611847100e018c522d807005da790251f0fd511845000e018c522d80000003bf07600005da790251f0fd511845000e018c522d800000097d1b70000": can't read, error -3420 (unknown)
  13. mmsadmin

    Feature Requests

    I've been doing mailbox backups for about a week now, and dealing with the errors and warnings to test how it works in my environment. In my testing, new mailboxes added to Exchange are not automatically backed up, nor are they even visible in the volume list. Also, deleted users never disappear from the volume list (even after the mailbox is purged). Instead, an error is generated for every deleted user, every day: - 12/13/2007 10:26:20 PM: Copying [Delted Mailbox Name] on [Exchange Server Name] Scanning incomplete, error -3405 (unknown)
  14. mmsadmin

    Feature Requests

    When attempting to backup the mailbox container with the individual mailboxes, my backup fails with a bunch of errors and warnings. The warnings are all "can't read, error -1101 (file/directory not found)" The errors are all either "can't read, error -3420 (unknown)" or "Scanning incomplete, error -3407 (unexpected provider error)" The 3407 errors are on mailboxes of disabled accounts. The accounts need to remain disabled and not deleted. If this is going to cause my backup to be continuously reported as failing, then I have to go back to backing up the entire storage group, and so I am still unable to exclude the large public folder from my backup.
  15. mmsadmin

    Feature Requests

    Thank you for responding to my concerns so quickly. I am a little frustrated at the forums. After spending a long time compiling my original message, and this message. I received an error that caused me to lose my entire message and have to retype it from scratch "We cannot proceed. The form you have submitted is no longer valid. Please use your back button to return to the previous page." With regard to: 1) Thank you for the suggestion, but the security policy in my organization frowns on the use of server desktops for any reason, even backups, unless there is no other choice. This causes Retrospect to be the only application "under scrutiny" at every security meeting. The backup server has other applications on it that the backup operator is not authorized to use, and so we must maintain strict group policies on that server to prevent unauthorized access. These policies must be maintained and reviewed on a regular basis. Yes, this is a feature request. 2) The Media Request Timeout causes the script to halt execution if a listed backup set is not available. And so in order for this to work for our organization, we would have to schedule every backup script to run every day. This is in addition to still having to create a separate backup script for each backup set and a separate backup set for each hard drive used. Our organization also requires an email notification to be sent on success or failure of a backup. Eventually our organization is going to require a separate hard drive backup for each day of the month. Having to manage such complex schedules and a myriad of backup scripts for a rotating backup of the same data requires a lot of administration. Also having to read 30 e-mails every day just to find out whether the backup was successful or not greatly increases the chance that a failed backup will not be addressed in a timely fashion. There was a user above that had similar concerns with rotating backups on hard drives. It would be nice if Retrospect was more accomodating for these types of backup routines. This is a feature request please. 3) I will try this and let you know, but I wish you had a more definitive answer for me. I don't have a test environment and my exchange folders are very large. Each test might take me several hours. I'd rather know for sure than take a chance that something doesn't get backed up. The ability to backup specific information stores within a storage group would help. Ideally, a windows explorer style "information store/mailbox/public folder selection list" with checkboxes would be a very good feature to have. This is a feature request please. 4) I've tried this and was unsuccessful. The problem is that the same folder name exists in many places on the same server and other servers as well. If I try to exclude the folder I dont want, it ends up excluding other folders that I still want to backup. I could not find a way to exclude an exact client/pathname. Also this would require a lot of administration and maintenance when dealing with 30 backup scripts (see #2). As noted in #3, the option to use a windows explorer style "backup selection list" with checkboxes would be a very good feature to have. This is also a request please. As a note: When choosing files to restore, a window explorer style window with check boxes is used to pick the items for restore. This is exactly the type of window that I am referring to, except without the necessity to "highlight" what you checked. I honestly don't see the point in having to do that. When you check a box, that is your selection. The highlighting of selections after selecting them seems like an unnecessary step. I feel that these are all very legitimate feature requests. The workarounds are complicated and cumbersome to use, in some cases require a lot more administration than should be required. I would much rather see these features implemented and reduce the amount of administration required to use retrospect. I do appreciate your time in reviewing and addressing my concerns.
×