If a simple retry does not help, you need to try to track down the reoccurring errors yourself. That’s possible if you investigate when and where the error happens and try to see a pattern. To be able to do that, you need to know what is happening during an offload in Silverstack. When opening the offload wizard for a folder or volume (source), Silverstack scans its content, tries to identify the recording device, and reads-out first metadata to give you a condensed overview of what’s actually there. If the (file-)system or Silverstack’s metadata scanner notices any error related to this process, the wizard will show it: A scanning error got flagged up in the offload wizardĮven if the wizard indicates no error, you should check the file list for completeness as it is the reference for the offload job: what Silverstack did not find at this point, it won’t copy later.
This is even more important when offloading from shared or virtual volumes as those might change their contents (e.g., during initialization) without your awareness. Once the “Offload” button is clicked, Silverstack adds a new offload job to its queue and reliably keeps track of its progress, even when terminating the application, or the system crashes. Per default settings, file after file is read on the source and written to the destination(s).
Silverstack shows no files to copy verification#
The files will appear on the destinations with the extension “.pfncopy” for as long as the copy is incomplete and until Silverstack has read them again to ensure they are identical to the respective source files – this process is called verification.ĭepending on the configuration in the offload wizard, the verification will either be performed after a single file is copied and before copying the next one (default: “Included in Copy Job”) or as a separate job after all files are copied (option: “Separate”). Verification behavior configuration in the offload wizardĪdditionally, there is the option of “Source Verification”. This refers to the process of also rereading the source after the copy’s completion. This allows you to confirm the copy was successful.This makes sure that the source files did not change in the meantime and can detect if the source volume is unreliable concerning read consistency. Here -v is short for “verbose.” It causes the details of the file transfer to appear, similar to the -v option in the cp command. If we want to copy the file to dir_2, here’s what the rsync command to do the same would look like.
Silverstack shows no files to copy how to#
RELATED: How to Use rsync to Backup Your Data on LinuxĬonsidering that we have two directories dir_1, dir_2, and a file Test.txt in dir_1. However, it also allows copying files and directories on the same PC. The rsync command stands for “Remote Sync” and is primarily used to transfer files and directories between computers on the same network.
RELATED: 37 Important Linux Commands You Should Know Using the Rsync Command The output would look like this: 'Test_Example.txt' -> 'dir_1/Test_Example.txt
To display the output of the copy operation, you’d use the -v option.
For example, let’s assume that there’s a file Test_Example that needs to be copied to dir_1.
0 kommentar(er)
