Jump to content

Putting files back where they should be

Recommended Posts





I'm using Retrospect 5.0.205 in OSX.5 on an X-Serve for a few workstations. One of


the larger issues we have is restoring files to where they originally came


from after a scripted backup. Now, maybe I'm missing something, but every


time I try and do anything but a full system restore Retrospect places the


files in a root level folder (usually titled "Backup Set B"...of which I'm


assuming is due to the name of the backup set being used).




The files desired are there but we fear anything but putting files exactly


where they were before for the risk of possibly confusing members of our


user base even slightly and sending them into a state referred to commonly


as a "tizzy".




All the backup methods documented seem to do this, except for the full


system restore. Am I missing something vital or is what I'm trying to do


just not an option?









Link to comment
Share on other sites

The default restore type (Restore files from a backup) will do this, as will a restore by search.




If you'd like files to go back to where they came from, use the Restore entire disk option instead. If you only need to restore a few files, there are two VERY important steps to take to do this.




First, in the destination selection window, you must change the pull-down menu from "replace entire disk" to "replace corresponding files." This prevents the possibility of data loss.




Next, in the restore summary window, click Files Chosen. In the browser that appears, this is where you select the files that you want to replace. Once you've done this, close the broswer, check that the summary looks correct, and then click Restore.




If you need more details, please see page 48 in your 5.0 User's Guide.

Link to comment
Share on other sites

Irena's suggestion is right on the mark!




Another way to view the other strategy, where the restore puts the files in a separate folder (complete with the original folder hierarchy) is that the restore is really a three-step operation for the system admins.




First, do the restore.




Next, review the restored files to ensure you got exactly what you (and the users) wanted - no more, and no less.




Finally, move (manually, unfortunately) the restored files back to their original location.




While this is more effort than Irena's suggestion, it has the advantage of inserting a verification step before placing the files where they need to go.








-- Jim

Link to comment
Share on other sites

REMEMBER that there is an important difference between "Replace Entire" and "Files and Folders."




According to the Retrospect user's guide, Executing a Restore using the "Retrieve" choices (Files or Files and Folders) will NOT restore the original unix permissions with the file. Instead, every file will have a set of default permissions (as outlined in the guide).




In order to restore files with their original permissions intact (and remember, owner/group informatio is stored as a number, so restoring this way to a _different_ computer might give unexpected results) you must select either "Restore Entire Disk" or "Replace Corresponding Files."




It's up to you to decide if you need restored files to keep their original permissions, but that's how it's done.




Note that the term "Entire Disk" is misleading, since you can define a folder as a Subvolume and use that as a Destination; you don't have to use the root level of your disk as the restore location.





Link to comment
Share on other sites


This topic is now archived and is closed to further replies.

  • Create New...