Jump to content


  • Content count

  • Joined

  • Last visited

Posts posted by ivar2

  1. Hi. In previous versions was one big problem. Sometimes I need to change complete location on source, altough all files and folders remain the same, just source drive letter changed or letter remains the same, but drive was needed to reformat. Afrer source drive reformat and after copying data back, Retrospect think that its other source, altough all files are the same, even data-time. When I started incremental backup, Retrospect copied all files as first full backup. This was really frustrating. How this is implemented in v.9.0.1 ? And also do block level works after source relocation or it also starts copying whole file without changed blocks taken into account. 

  2. I made second test with this big file and block level seems working. The only thing that in first time was differ was that I moved catalog file into different location. Is this catalog file location moving allowed operation in Retrospect? Seems while its moved into other location, it looses block-level checksums. Also there was one other strange thing - I wasnt able to enter catalog file location in Retrospect window where it asks catalog file location, it just says that there isnt file when I select it in window, altough its there and visible. Then I opened Totalcommander, right-click to catalog file and opened it with Retrospect and then it finally find file.

  3. The only VMDK files I use with VMware Workstation are the 'twoGbMaxExtentFlat' type which seem to work with the block level feature. (Mostly Linux guests on Windows hosts.)


    I doubt changing the file extension would have any effect. Retrospect will treat any file over 100MB as eligible unless it one of the few types currently known to be unsuitable.


    Not the best configuration for reliability/stability. Is there a reason why the USB3 drive cannot be connected directly to the backup server? Is the other computer being used for anything else while the backup is running?

    Its not important that its vmware file. I can rename it if problem is with extension. Question is in large files. Because small files work with block level. Where at all Retrospect puts this blocks checksums. Into data set or into catalog file. Seems it just looses this information and therefore in second time starts backing up full file. Also I have latest version, through update. Now I try to make backup with Ahsay, its also have block-level feature. USB3 drive I cant connect directly to server because server dont have USB3 and also dont enough free space. Usually I have enough room in my storage, but now I need to archive this large file because I need to broke mirror and make new raid and its large raid array and then copy this file back from backup. Of course I can just copy it with explorer but maybe sometimes in future I also need to do the same thing and its time consuming to copy it. Therefore block level is very good thing. Previously I tested with rsync, its command-line delta-copy (blocl-level) software, but rsync dont like USB at all and its not work also there. 


    But its not VMWare volume, its just regular file, I can temporarily also change its extension if this is problem. Its Workstation file that I want to backup offline......Also I noticed some other problem. My storage set was made into other computers USB3 drive through share, 1GB LAN, but it stops backup and log says that this share looses network connection.

  5. What is your 900GB file? Certain file types are more suitable to block level backup than others. If you haven't already done so have a look at the User Guide section on Block Level Incremental Backup for more details:




    I have already readed it. The 900 GB file is vmware workstation preallocated virtual disk file, backed up while snapshot was taken (while no writes, only reads from it), name is  -  storage-flat.vmdk

  6. Hi, is there some limitations for file size to be processed by block level? I have 900 GB file and in second backup log says that file is backed up fully, without block-level. So, I canceled backup. Upgraded my trial 45day version to 9.0.1, deleted backup-set and now started from beginning with first backup. But it takes about 1 day to complete before I can start testing with second backup and then find out do block-level works or not. I also tested with smaller file, 110 MB and in second backup it processes block-level fine. Is my 900 GB file too big for block-level? Why block-level wasnt worked with it? Thanx! 

  7. I find out the problem. The problem is not in Retrospect, sorry (Retrospect is the best backup software). But problem was in Windows approach to disk formatting and partitioning. This Windows part is unfortunately connected also to Retrospect Disaster Recovery CD. First, Windows partitions previous C-drive as logical D and make previous D as C and bootable. Second, if you format C-drive previously with FAT32 and then make it NTFS partition with example Part manager, then Windows dont format it and .....my problem was exactly this.....when I look later, restored server C-drive, then I give big surprise - it is FAT32 and of course domain-controller don't like FAT32. If I look it with some partition tool, then it is NTFS. Finally, partition is NTFS and formated filesystem is FAT32 and Windows like to think it is FAT32.

    Altough,to use Windows installer in Retrospect Disaster Recovery is not very good idea. Maybe later EMC finds some other solution, it's own installer like example in Acronis.


  8. As I understand, both FULL and INCREMENTAL exchange backups must commit log files. I think full backup commits before backup and then does backup from store, and incremental backup backs up log files and then does commit. Correct me if I am wrong. Differential only backs up all the time log files. Also exchange itself must set to not commit log files (circular turned off).

    But also I noted that Retrospect fails to commit log files in incremental exchange backup (and also fails to backup log files at all) if this script isn alone - if srcript also backs up mailboxes or other drives. I always make storage backup script alone, athought this is wery strange, maybe some bug.


  9. Hello,

    I restored second time domain controller and after that again some services don't start anymore (server is not usable anymore). Services are - certificate services, FTP Publishing service, IIS Admin Service, Microsoft Exchange Routing Engine, SMTP and some more.

    I restored from snapshot, with disaster CD, complete C-drive and system-state. First time I boot into AD restore mode. After that Retrospect Helper completes it's work fine. Domain controller is 2003 Enterprise R2, all windows updates installed. Retrospect is 7.6.

    Where can be problem or Retrospect can't at all recover domain controllers. First time, when I try to restore my domain controller, Retrospect was 7.5 (about half year ago), but still the same problem, and completely other domain controller server (also 2003 ent R2).



  10. Grooming should not remove items that are needed to recover the database. Retrospect uses the database history report to track all the parts needed to restore the database.


    But what then grooming does at all in Exchange log-backup? (database backup even dont make snapshots - snapshot list remains empty)

  11. Moving exchange data to a new server is a very complicated process, that may require the help of MS tech support.


    You could try doing a restore to a recovery storage group on a new server if the storage group does not contain public folders.


    But why not just install Exchange into new server and restore FirstStorageGroup with Retrospect.

    (as I know Retrospect don't need Exchange "recovery storage group")


  12. I am little mess. Why many instructions and helps suggests in Internet, about Exchange migration to new server, all talk about replication needs of Exchange system folders to the new server. Are those Exchange system-folders part of "public folder store" or they are not part of it? If they are part on "public folder store", then why not just backup-restore this storage (or just simple copy it) to the new server?


  13. Retrospect will backup the Windows system state, if you backup the C drive.


    Retrospect will backup everything from whatever disk you pick. Retrospect will backup the storage groups you select.


    I backup system-C drive with system-state separately from Exchange. Now I have situation, where operating system is broken, but Exchange is in good working state. I want to restore operating system with system-state to previous snapshot, but I want Exchange to remain with current configuration. I plan to first restore drive C with system-state and then restore Exchange back to the current, newest point (backed up right before drive C restoration).

    But how then I restore Exchange "system-state"? Drive C system-state is then old, but for Exchange I want current state. I need separete system-states for operating system and for Exchange.

    Is Exchange backup in Retrospect backs-up also Exchange system or not? I don't mean operating-system state.