Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


Soda last won the day on July 14 2017

Soda had the most liked content!

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Soda's Achievements


Newbie (1/14)



  1. Soda

    error -1101

    Thanks, will keep in mind if it does return
  2. Soda

    error -1101

    I have done something incredibly stupid I found that there was a pending update which windows had downloaded and queued. After a restart the problem went away. So as you see it's actually Windows 10 whose fault it was.
  3. Soda

    error -1101

    Hi, I get the following 2 errors Writer "NPS VSS Writer" backup failed, error -1101 (file/directory not found). Component "NPS Database" backup failed, error -1101 (file/directory not found). It appears to happens when the snapshot is being saved Everything else seems to work as normal. I do not have any errors/warnings in windows event viewer > Windows Logs > System This started after I recycled my Backup Set. However this is the first such backup after windows updated itself to 1709 and also retrospect updated itself to so really it could be anything! Any ideas on what it is and how to move forward? Thanks
  4. Thanks for all the inputs. Support confirmed to me that it would be ok to go ahead with the backup and as long as I don't have any open files, then 100% of the data will still get backed up. Incidentally on a side note I managed to fix the vss error and get everything working properly. My problem seemed to point at the Hyper V shadow copy service and removing it as a VSS provider as outlined in the following post fixed it for me. https://answers.microsoft.com/en-us/windows/forum/windows_10-update/backups-fail-volume-shadow-copy-errors-22-12292/1db3215c-af3c-45fa-a061-5f8bab823b5e?auth=1 However there is no guarantee that this maybe the same reason someone else would have a VSS error, so do make sure this solution is applicable to you before following it.
  5. Hi, When starting a full backup I get the following error in the log. "Can't use Open File Backup option for Local Disk (C:), error -3050 (VSS reported an error)" The backup doesn't halt, but I did stop it rather than let it complete. Any ideas on how I should I proceed or what this is? Thanks
  6. Thanks for that!! As for the hidden partitions, after many re installs(getting used to windows again) I feel comfortable that the windows installer prompts you and then creates the additional partitions needed for a boot volume. At least it did for my ssd which I removed all the partitions from.
  7. iCompute, I just got this from a Retrospect agent. Looks like it does everything for you. "If you select in Source "My Computer" Retrospect will backup all partitions available in the computer disk, so it will be then possible to restore all, in case of crash disk, using Disaster Recovery. Make sure Open files backup is selected in preferences"
  8. Hi, It seems that when you boot with the retrospect recovery drive you created in retrospect you get the option to 'setup your hard drive before restoring' and the partitioning option makes it self available there. As to the partitioning scheme, it looks like it will auto magically create it as it was. The recovery partition mentioned below gets created by windows (at least in 10, I cant speak for anything earlier. ) "If the drive that are restoring had a hidden Recovery Partition, the Retrospect Emergency Recovery process will recreate the exact partitioning scheme that was present when the backup being restored was originally created. This process will destroy all data present on the drive."
  9. Thank you. So are the efi, msr and recovery partitions generic? As long as you have a backup of all the local files you can restore to even a different HD, the system partitions will get created and you're ready to go? I'm asking as for the moment I have been using some cloning software that seems to backup even those partitions.
  10. Just a follow up. It all worked very well, Retrospect perfectly restored on to windows my mac backed up media set.
  11. Hi, I am just getting to grips with Retrospect on windows after many years on Mac. The day to day folder specific backups are working fine. Can I use retrospect to backup my entire boot disk including the hidden partitions(EFI, MSR and recovery) to restore/roll back my entire OS? I don't see these partitions when I select the local drive? Is it just done anyway or not needed? Please excuse me if anything seems stupid, I am new to windows. Thanks!
  12. Hi, I've just rebuilt my catalog for a media set to be restored. I'd like to know that the files are ok as they been transferred over different drives. I know I can verify the media set to check this. In order to save time, if I just went ahead and did the restore, would that be doing a verify anyway? Thanks
  13. I hear this a lot regarding exFAT. I understand the risk is there because of the lack of journaling if there is a connection dropout. As long as that doesn't happen is it generally reliable and would I be able to create a media set on an exFAT drive to directly make a backup to? Only while migrating data one time and not for long term use.
  14. Thank you, That sounds much easier, so when I perform a "Recreate from Disk," Retrospect(Windows) will be able to use the backup I created with Retrospect(Mac.)
  15. Hi, I use Pegasus RAID formatted HFS on a mac and would like to migrate about 3tb of data back onto the drive after formatting it as NTFS for use on an new windows machine. I use Retrospect 13.5 on a mac. Any tips or suggestions for a fast and reliable method to rehome the data with verify would be much appreciated. Is verify even reliable when changing formats? I was thinking about using retrospect to 'copy' the data either via direct connection and smb or formatting an external hard drive as exfat. I'm not sure whether exfat will be a sensible thing or also whether I would need a windows retrospect license for this. Would appreciate and suggestions or advice on the matter.
  • Create New...