Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


mdwyer20175 last won the day on December 12 2013

mdwyer20175 had the most liked content!

mdwyer20175's Achievements


Newbie (1/14)



  1. I chose to bite the bullet and pay for OFO upgrade from my 7.6 license. Since I only do I/T when I must, I don't know what is best, but for backing up drive C to disk, windows DR seems fine. My main office uses VEAAM for the VR server backup and then uses Windows Server backup for the separate, physical backup server. As of 2008, windows backup can run on a schedule, but I think it is only disk to disk, and keeps one version as a big lump. I would not use it for 'data' backup, where I want multiple and individual file versions. It is to save the boot drive, and I am using other s/w (retro in my branch office here) to copy to tape to take off-site. Anyway, buying ofo gives me 2 different ways to restore if I have to. I once had a server failure and the backups were no good. I overspend a bit now in my dotage.
  2. Using Windows Single Server 8.5.0 (136), I back up 600K files onto an LTO5 tape (Win 2K12, Dell PE T420): - 11/29/2013 11:53:31 PM: Copying DATAPART1 (D:) 11/30/2013 1:22:33 AM: Snapshot stored, 115.9 MB 11/30/2013 1:22:49 AM: Comparing DATAPART1 (D:) 11/30/2013 2:36:42 AM: Execution completed successfully Completed: 607542 files, 510.7 GB Performance: 6563.2 MB/minute (6089.3 copy, 7117.1 compare) Duration: 02:43:11 (00:03:50 idle/loading/preparing)
  3. Has anyone tried this? IMO, bare metal restore should leave me a server that is working the same as it was when I did the backup. My guess is that it does not work too well, if at all, without the ofo add-on, in which case R should note that on marketing materials. But that is just a guess on my part, so I would appreciate corrections. QUESTION: The table http://retrospect.com/en/products/win/versions implies that single server Retrospect is capable of bare metal disaster recovery. If using Windows Server 2012, is the Open File Backup Option a prerequisite for this to work with the Single Server edition? RESPONSE RECEIVED: It is not prerequisite but it is recommended so that Retrospect can backup all open files on the system. Thank you for using Retrospect,The Retrospect Support Team
  4. Using Single Server 8.5 to back up a 2012 Win Server that is a basic file and print server. Used Retro for many years, but first time I have not had the open file option add-on package (no more exchange or sql at this site). I see LOTS of 1020 sharing violations for NTUSER.DAT and other files (mostly log files, but not all). If I someday try a bare metal restore of this server, will it fail because I can not use open file option? I am not worried about compare errors, but CAN'T READ NTUSER.DAT doesn't sound so good. Given that level of failure, is there any point to Retrospect for server backup of the C drive for me? Pity a semi-crippled ofo could not included that covered the basic files, but too tricky I guess. My workaround is Windows Backup to a usb disk and then let retro copy that to tape. I set that up already, once I saw these failures. Then I can do this sort of thing: http://www.windowsnetworking.com/articles-tutorials/windows-server-2008/Restoring-Windows-Server-Bare-Metal.html Is Windows better at bare metal restore than the basic Retrospect server package? Am I am missing something?
  5. If I have a disk used for backup, I can limit the GB used by any particular backup set. Getting this right is like picking the Kentucky Derby winner, which I have done on occasion. I would much rather set NEVER KEEP MORE THAN xx SETS instead of the GB limit. I intend to keep 2 or 3 sets of some backups if I can, and if I could do the math and keep users from adding data, I could set the GB limit, but... And if I don't set any limit (99%), one of the sets winds up taking over the disk. This would be similar in concept to the "keep at least xx set" option for the inevitable DISK FULL AS USUAL problem, but it would be a MAX number of sets not a minium number.
  6. I wish I could get a report (view with option to email) that listed all scripts scheduled, and for each script, a table of what conditions are used for file selection (COMPLETE list not ..more), what targets are, what percent full the targets are now, how many backup sets are on each target, and if it worked the last time it ran. One report, generated with a couple mouse clicks, without endless drilling. A separate sparse list could show scripts that have flaws, and list the flaw (NOT SCHEDULED. NO TARGET. TARGET MISSING. WHATEVER). Otherwise, if I reconfigure servers, I have a dozen or two scripts to mess with and it is tedious to error check. One report, and I will see errors quickly, plus if emailed, I can pass it on to others for error checking. Most of this is a glorified text file of what is defined for scripts. Mind you, text is woefully underappreciated in GatesWorld.
  7. Windows network, xp station, 519 repeatedly. Having read the kb on 519, I get that it is always something other than retrospect. This one station "used to" have network problems in daily use until I changed network cards and went to static ip etc, etc (don't remember which fix fixed it). For the past year, this user has had no network connectivity problems in daily use (email, cad, database, etc). 3Com's network monitoring reports no issues. I still need to drag thru his event viewer to look for clues. Is there anything unique in the way Retrospect works that might offer a clue as to why only Retrospect is grumpy about this guy's setup/hardware etc? I realize that there are a couple hundred things I can try (including yet another network card, new ip, reformatting, etc), but wondered if I could zero in on it.
  8. I hired MSoft to help me fix a corruption problem. Long story, but this latest email from them might be of some interest to others here, and led me to two questions... Is this why competitor BExec no longer does brick level backup? They sell a very pricey alternative product I think. Also, is the 2007 Exchange version of Retrospect still using brick level backups via MAPI? Chime in if you have an opinion on my questions or the following comments, please. I am not going to list sender here, no point in getting sender in trouble for no reason, but this is quoted from a tech support email >>>>>>>>>>>>>>>>>>>> Microsoft does not recommend brick level backup. This is because brick level backup does not run on the normal backup API provided by Microsoft. Instead, it uses MAPI, just like the Outlook client does. Using MAPI will cause backup performance down-grade and may cause memory leak problem. If you indeed has the requirement to perform brick level backup, I suggest you consider the following practices: 1. Do not run brick level backup on every mailbox. Only run brick level backup on important mailboxes, such as the mailboxes for executives. 2. Set mailbox size restriction, especially for those whose mailboxes need brick level backup. Keeping smaller sized mailbox will lower the possibility of getting corrupted. And running brick level backup on large mailbox will extend the backup procedure significantly. 3. Disable store level scan with the registry change as I’ve mentioned above. 4. If you have found a certain mailbox has some corrupted items, as reported in the brick level backup log, I suggest you try to move this mailbox to another store or another server. Move mailbox operation will fix some corruption if the problem is not severe. (NOTE FROM MATT DWYER - THIS DOESN'T WORK FOR BRICK LEVEL CORRUPTION!!) 5. Please keep it in mind that if the brick level backup log shows there are some corrupted items in certain mailboxes, and there is a failure, it does not always mean the backup fails. Usually, the overall backup is still successful. Only the backup on items/mailboxes reported are not successfully. You can try a restore test to verify if the backup is successful. For brick level backup, the corruption is often caused by antivirus application scanning the Exchange database. I recommend you disable store level scan by editing the following registry: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExchangeIS\VirusScan If the registry does exist, please click Enabled on the right pane. On Edit menu, click Modify. In the Edit DWORD Value dialog box, type "0" (without the quotation marks) in the "Value data" box, and then click OK. Restart Information Store service. With this change, we can disable the store level scan. >>>>>>>>>>>>>>>>>>>> Not sure this helps anyone, but maybe this explains why MS wants me to install a recovery server, restore to that server and then move a mailbox back to original server (ouch, I have lots of extra servers lying around and time to do this...).
  9. I went to each mailbox and deleted the messages and folders that Retrospect says are corrupt. Now, it suddenly picks entirely new ones as corrupt. This makes me skeptical. Question, this is exchange enterprise, and mailboxes are larger than 2 GB. Is that a problem for Retrospect? Should not be I would think, but ... I also got other general errors that were not there before. Here is an example: - 1/27/2008 5:11:56 AM: Copying Matt Dwyer on EXS File "Matt Dwyer\Cabinet\ECA\000000004f05b8d31742f647be2954e368fba4ba0700fa53bd248d2a7441964493152b4c0b04000000236eeb000023268af362a82748b0f13b95381a7aba00000006842b0000": can't read, error -1101 (file/directory not found) File "Matt Dwyer\Cabinet\OFFICE\STATUS\000000004f05b8d31742f647be2954e368fba4ba0700fa53bd248d2a7441964493152b4c0b040000002b8318000023268af362a82748b0f13b95381a7aba000000ac2efa0000": can't read, error -1101 (file/directory not found) T-865: MBDataInputStream::PrepareLongProperty: Failure (winerr = 0x80040102) to read long property 0x3fe1. File "Matt Dwyer\Inbox\000000004f05b8d31742f647be2954e368fba4ba0100b6c916443f5e9c4faa98ede824cb655d00000000281d0000": can't read, error -1012 (feature unsupported) File "Matt Dwyer\Inbox\000000004f05b8d31742f647be2954e368fba4ba0700b6c916443f5e9c4faa98ede824cb655d00000000281d000023268af362a82748b0f13b95381a7aba0000017f598f0000": can't read, error -1101 (file/directory not found) 1/27/2008 6:42:54 AM: Snapshot stored, 50.4 MB 1/27/2008 6:43:06 AM: 1 execution errors Remaining: 4 files, 6,133 KB Completed: 82531 files, 6.8 GB Performance: 150.5 MB/minute Duration: 01:31:09 (00:45:17 idle/loading/preparing)
  10. Good question. Looking there, and using "code" instead of my actual license code (which would probably be a no-no to publish): Open File Backup 7.5.387 - Open File Backup Add-on (code) Under properties, it says.. Type: Open File Backup Add-on Code: xxxxxxxxxx (blotting it out here) Version: 7.5.387 Installed: 3/14/2006 9:46 AM Depends on: Application FYI, it does not say 1 used, 0 available off to the right - as it doesn't say anything off to the right. In addition, and this seems odd, under Add-On Value Package (which is how I got open file option), it shows the code but says 0 used, 1 available off to the right. That makes no sense to me.
  11. hmm, maybe I am not posting ENOUGH. Are the lines that follow significant? - 1/26/2008 12:15:52 AM: Copying Data (E:) on PJ File "E:\ARCMAIL\Cimof-archive.pst": can't read, error -1111 (locked range conflict) File "E:\ARCMAIL\DGrser-archive.pst": can't read, error -1111 (locked range conflict) 1/26/2008 1:23:18 AM: Grooming Backup Set PJ-TOTAL... 1/26/2008 2:10:31 AM: Groomed 308.3 GB from Backup Set PJ-TOTAL. File "E:\System Volume Information\15{3808876b-c176-4e48-b7ae-04046e6cc752}": can't read, error -1020 (sharing violation) File "E:\System Volume Information\16{3808876b-c176-4e48-b7ae-04046e6cc752}": can't read, error -1020 (sharing violation) 1/26/2008 10:19:04 AM: Snapshot stored, 110.1 MB 1/26/2008 10:19:56 AM: Comparing Data (E:) on PJ File "E:\ARCMAIL\BDavis-Archives.pst": different modify date/time (set: 1/25/2008 10:17:56 AM, vol: 1/26/2008 4:08:32 AM)
  12. - 1/26/2008 12:15:52 AM: Copying Data (E:) on PJ File "E:\ARCMAIL\Cimof-archive.pst": can't read, error -1111 (locked range conflict) File "E:\ARCMAIL\DGrser-archive.pst": can't read, error -1111 (locked range conflict)
  13. Closing outlook is tough with 25+ users (not sure what people with 100 users would do). The archives are all on a shared drive for backup purposes, which I guess should not matter. OFO is installed, and selected according to the script. Not the same server as exchange, which could be a mistake(?). Sometimes that pst backup occurs at same time as main exchange backup (different servers, d2d backups, so separate threads). Could that be it?
  14. Any tricks to avoiding range errors when backing up archive pst's? File "...................pst": can't read, error -1111 (locked range conflict)
  15. Ok, I went through the folders with corrupt messages and exported them to a PST file, and then deleted the folders. I emptied junk mail, and then emptied deleted mail. By the time I retried the backup, there were new messages in junk and deleted mail, and I got errors again in those (admittedly useless) folders. Does this mean I have a corrupt junk mail and deleted mail folder? I am not having fun yet....
  • Create New...