Mayoff

Is the Mac logged in or logged out when you are running this screensaver. If you are logged out of the finder, that could prevent disks from mounting to the desktop and being available to Retrospect.

In 27 years of supporting Retrospect, I have never seen a recycle delete anything but the files that are inside the backup set that you are recycling. In the example screenshot above, the contents of 1-MacMini_Seagate 4TB_12, 2-MacMini_Seagate 4TB_12 and 3-MacMini_Seagate 4TB_12 should have been cleared out and nothing else. Those folders appear to be on 3 different disks. The "ArcDisk::arcExportSessionFile: unexpected value of ArcCatalog::m_lastvol 0; can not write session file" error is a little odd and it implies that something prevented Retrospect from writing the .session file, but I have no way to know what caused that. You may want to check the OS X Console utility logs to see if any unusual errors are reported for the time of the recycle operation.

When the update is pending, the Mac OS has changed the state of the disk, so that Retrospect no longer recognizes it as the original disk. The only option is to install the update.

Directions are at https://www.retrospect.com/en/support/kb/retroisa_advanced_options

It sounds like your preferences may have gotten lost or damaged and Retrospect automatically rebuilt the preferences from the configs.xml file. Reverting back to the original preferences isn't a good idea, but you could restore an old version of the config80.dat file if you really need the info.

18.2.1 was released yesterday to fix this issue. http://www.retrospect.com/updates

It should appear as Retrospect Engine, as far as I know. It is running under rosetta.

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

This does seem like a bug. We have it flagged as a high priority with our engineering team to resolve.

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.

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.

Are you using a disk backup set or a disk storage group?

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"

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.

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.

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.

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?

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.

I made sure the Retrospect Product Manager saw your document.

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.

>except that my experience with the -530 bug several years ago shows that Tech Support is normally not allowed to submit a bug to the engineers unless Tech Support can reproduce it on their own system. This is 100% false. If support believes the issue is a bug, it will be submitted as a bug. In no way does tech support have to reproduce a bug themselves. >that's why I have out-and-out said that using Storage Groups for Retrospect Mac is not a good idea That is a choice you can make for yourself, but we have 1000's of customers successfully using Storage Groups on local disk backup sets and cloud backup sets.

>Source disk image When you see disk image, are you talking about .dmg files or do you mean the actual mounted disk? Are you using a backup script or a copy media set script? Maybe consider posting a screenshot of what you are seeing. You may also want to just contact support directly and we can try to help.

We have released version 18.1, which contains a lot of bug fixes. Please give that version a try. If you still have trouble, please contact support directly. Configuring Retrospect to remember the password for an encrypted backup set does not apply to a catalog rebuild. If the password is not accepted during a catalog rebuild attempt, it typically means something is wrong with the password being entered. You might see the same error during a restore attempt. The catalog rebuild process reads the header of the .rdb file to identify if it is encrypted and when the password is not accepted, it means the decryption attempt failed.

I think it is time to reply to "forum rules" as a reminder, if you are posting inaccurate and unsubstantiated information into the forum it will be deleted. This of course does not include troubleshooting advice, because none of us have all the answers and we can often be wrong. >Please note that this forum is intended to be a constructive place and we don't tolerate personal abuse. Direct attacks against individuals or abusive posts could result in you being banned from the forum. If you are posting derogatory information about any member of Retrospect/StorCentric or toward anyone else posting in the forum, you will get banned from the forum.

Retrospect 18.1 has been released with a bug fix for the Activity Thread settings. http://www.retrospect.com/updates