Jump to content

Mayoff

Administrators
  • Posts

    10,537
  • Joined

  • Last visited

  • Days Won

    46

Mayoff last won the day on November 18

Mayoff had the most liked content!

About Mayoff

Recent Profile Visitors

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

Mayoff's Achievements

Grand Master

Grand Master (14/14)

  • Very Popular Rare
  • Dedicated Rare
  • First Post Rare
  • Collaborator Rare
  • Posting Machine Rare

Recent Badges

127

Reputation

  1. 18.2.1 was released yesterday to fix this issue. http://www.retrospect.com/updates
  2. It should appear as Retrospect Engine, as far as I know. It is running under rosetta.
  3. Retrospect fully supports M1 hardware. If you are trying to back up the M1 over the network to the Windows system, you would need to run Retrospect for Windows on the 2019 server and put Retrospect Client onto the M1
  4. This does seem like a bug. We have it flagged as a high priority with our engineering team to resolve.
  5. We have a new set of DR directions that can be found at http://www.retrospect.com/dr that include new/updated articles and new detailed tutorials.
  6. The bootable USB thumb drive is based off of Microsoft WinPE and it will work on all windows computers. You don't need a different disk for each computer. You can boot from the disk and then do either a local restore or network based restore of the C disk.
  7. You could do a selector that has the exclude condition of "Folder Path does Contains temp\filename" Or you could do an exclusion of "folder path does contain russellg\temp"
  8. If the original backup had the bios configured for legacy boot mode, you need to be using legacy boot mode during the restore. The Microsoft ASR writer will fail to restore registry/partition info if the boot mode is different when you are doing the restore vs what you had during the original backup.
  9. Did the Retrospect engine get installed? You can look under System Preferences. You can also check library/application support/Retrospect. You are also welcome to email support@retrospect.com and we can help directly.
  10. I don't think dropping of a network connection would be a factor, but if the network device is on DHCP instead of a fixed address, that might cause some confusion.
  11. First thing is to make sure you have the security settings in Retrospect configured correctly. Retrospect has 3 or 4 different places to set the security. https://www.retrospect.com/en/support/kb/configuring_retrospect_7_x_for_use_with_a_nas_device In general, it isn't normal for the NAS settings to be lost for automatic login. When you click the button to update the login info, does it ask you to change existing settings or does it act like no prior setting had been entered?
  12. I have upgraded the forum software to the latest version. We will be fixing the SSL certificate also. If you run into any issues, let me know.
  13. I made sure the Retrospect Product Manager saw your document.
  14. Thank you for the thoughtful and well details article. I am sure other users will find it helpful. side note: I see some access keys and secret keys in the article. I assume those are generic and do not expose anything private. And for the record, we fully support most models of NAS devices and that will never change. We want users to have the most flexible backup storage solutions available.
×
×
  • Create New...