Search the Community
Showing results for tags 'mediaset'.
Found 3 results
I have a set of 5 'working day' disk media set backups, Mon, Tues, etc.. Each media set has a single member i.e. one physical disk per day backup. The media being backed up is a single Thunderbolt volume. All 5 media sets are uncompressed and unencrypted. As they are off-site portable backups I would like to convert them to compressed and encrypted. My understanding is this can't be applied directly retrospectively. My plan is to: Clone each disk to a similar sized new disk using Carbon Copy Cloner Erase the original member disk and create a new media set on it with a slightly different name and compression and encryption enabled. Use a "Copy Media Set" script to copy the cloned set back to the original member disk applying compression and encryption. I plan to use the two step "clone and copy back" rather than just a single step copy script because I want to keep the oldest disk as the first member of the set. My questions are: Is it OK to drag-copy or clone Retrospect data files between disks or do all copy operations have to be done using the Retrospect engine as part of a managed database/filesystem? When a "Copy Media Set" script is used is the ability to restore from a snapshot point in time preserved? Is any functionality of the media set lost? Will software compression and encryption be applied using this method. Thank you in advance for any assistance with this, as you can probably tell I am a relatively inexperienced user. Regards, Andrew Retrospect 15.0.0 LaCie Rugged Raid 4&5TB Thunderbolt connected disks
I've created a new media set (type: disk) named "ServerBackupDisk", with an external USB disk named "ServerBackupDisk1" and created a backup on this media set. Later I tried to add a second disk (same make/model) named "ServerBackupDisk2", but Retrospect wouldn't allow me to do this, saying "This disk is already a member of this media set." The second disk is _not_ showing in the list of media for the media set. I tried renaming the second disk to something less similar ("BackupB"), biut that didn't solve the problem. I ran the backup script to see if the disk was maybe added "invisibly" to the set, but no, it asked for the first disk. Does Retrocpsect maybe confuse the two disks because they are connected to the same USB port?
allan34 posted a topic in Retrospect bug reportswhen a member of a mediaset is marked as lost. Running verification on that set will stop with an error that the lost member is not found. Obviously it is not expected that the lost members are checked becausewe know they are not to be found... See also this post for a few othere whoa re seeing the same issues. http://forums.retrospect.com/index.php?/topic/148086-how-to-verify-one-media-member/