We use a script that takes in a set of filesystem paths, gets a list of files in those paths, queries a given TSM node for already-archived files, and then generates a list of files that are in the former list but not the latter. It then passes that final list to "dsmc archive" via -filelist. In the event of a problem, the files in the active transaction will be lost but the files already committed are stored safely, and the script will pick up the archive where it left off.
For the most part, we use RETINIT=EVENT for our archives, so that at the end we can do SET EVENT and make sure all the files have the same retention. Note that you *do* have to be careful on restore/retrieve: if the client is killed in the middle of a restore/retrieve, you risk having a partial file on disk, that -REPLACE=YES or -REPLACE=IFNEWER will not replace. On Wed, Sep 21, 2016 at 08:21:58AM -0400, Zoltan Forray wrote: > A user was running a large archive and the server was accidentally rebooted. > > Am I correct that he must start all over again - there is no appending to > an existing archive? I assume the archive that was running is still > good/viable. -- -- Skylar Thompson (skyl...@u.washington.edu) -- Genome Sciences Department, System Administrator -- Foege Building S046, (206)-685-7354 -- University of Washington School of Medicine
