Principios básicos de la prisión preventiva

Creating a Copy script manually is much like creating a Backup script. The differences are that where a Backup script uses Media Sets as a destination for the backed up files and folders, the Copy script uses volumes as a destination for the data, and calls them, sensibly, Destinations. There are options within the Copy script’s Destinations tab that allows you to fine tune the way Retrospect does the copy.

To create a Copy script manually, follow these steps:

1. In the Retrospect console’s Sidebar, click Scripts. A list of previously created scripts (if any) appears on the right side of the window.

2. In the List View Toolbar, click the Add button. The Script dialog appears. 3. In the Script Name field, enter a name for your new Copy script.

4. Make sure that the All or Backup category is selected, then click Copy in the script types list on the right side of the dialog, then click Add. The new script appears in the list, with a red icon next to it, indicating that the script is not complete. Below, in the Details area of the Summary tab, you can see that it is blank, telling you that you need to add one or more Sources, Destinations, and Schedules.

5. Click the Sources tab. Retrospect displays the Sources that you have already defined. Select the Source you want to copy by clicking the radio button next to it. By the nature of the copy operation, you may only copy one Source to one

Destination. The source can be a volume or a Favorite Folder from a volume.

6. Click the Destinations tab. Retrospect displays the Sources that you have already defined. Select the destination of the backup by clicking the radio button next to it. The destination can be a volume or a Favorite Folder from a volume.

The Destinations tab has a pop-up menu with several copying options. Choose the option you want:

Overwrite entire volumereplaces the entire contents of the destination volume or Favorite Folder with the selected files and folders from the source volume or

Favorite Folder. Everything else on the destination volume is deleted. Retrospect saves time by not copying identical files, that is, files that share the same location, name, modification date and time, etc., that are already present on the

destination. New files are added, and different versions of files already present on the destination are replaced by the files from the source, even if the file already present on the destination is newer.

Overwrite matching filesworks exactly like “Overwrite entire volume” above, with one important difference: Files and folders that already exist on the

destination volume but that aren’t present on the source volume are not deleted from the destination. This means that if a file that exists on both the source and destination is deleted from the source before an “Overwrite matching files” Copy script is run, the copy operation won’t remove that file from the destination. This is the default option.

Overwrite older filescopies the selected files and folders to the destination volume. When Retrospect finds a file that exists on both the source and destination, the destination file is overwritten only if the source file is newer.

Copy only missing filescopies the selected files and folders to the destination volume. When Retrospect finds a file that exists at the same location on both the source and destination, Retrospect leaves those files untouched. No files are deleted from the destination.

Copy to a new foldercopies the selected files and folders to a new folder on the destination volume. Other files and folders on the destination are left untouched. 7. Click the Rules tab. Click the radio button next to the Rule that you wish to apply

to this copy operation. For more information about Rules, see Chapter 7.

8. Click the Schedule tab. A script has no default schedule, so you must add one by clicking the plus (+) button under the empty schedule list.

9. In the schedule interface, the Destination pop-up menu lists the Destination that you previously set. Finally, set the date, time, and frequency for the Schedule to execute. See “Working with Schedules,” later in this chapter, for more

information.

10. Click the Options tab, then set the copy script options you desire. See “Copy Script Options” for more information.

11. Click the Summary tab to review your work. You can now see that Retrospect has all the information it needs to complete the backup.

Copy Script Options

Copy scripts share most of their options with backup scripts. See “Backup Script Options,” earlier in this chapter. The Copy script options are:

Move filesdeletes files from the source volume after they have been copied. If Thorough or Media verification is turned on and the files do not match exactly, the originals will not be deleted. Do not turn on the move files option without also turning on the Thorough verification option. You should perform at least one additional verified archive, backup, or duplicate before deleting files from the source. Retrospect cannot move files from a client computer if its Retrospect Client control panel has been set to allow read access only. By default, this option is off.

Tip:Before you use the Move files option, first archive to a different Media Set by copying without moving. This provides an extra measure of safety should one Media Set become unusable.

On Move, don’t delete empty folderskeeps folders that become empty as a result of the move instead of automatically deleting them. By default, this option is off.

Recompute icon positionsmanipulates the positions of file and folder icons copied to a Mac OS destination to prevent overlapping of icons. By default, this option is off.

Ignore encrypted file verification errorscauses Retrospect to ignore verification errors with encrypted files on NTFS volumes, preventing the Log from being filled with errors that can typically be ignored, as they result from valid changes made by the file system during the copy process.

Ignore file verification errors in security streamcauses Retrospect to ignore verification errors with security streams on NTFS volumes, preventing the Log from being filled with

errors that can typically be ignored, as they result from valid changes made by the file system during the copy process.