We execute mmbackup via a regular TSM client schedule with an incremental action, with a virtualmountpoint set to an empty, local "canary" directory. mmbackup runs as a preschedule command, and the client -domain parameter is set only to backup the canary directory. dsmc will backup the canary directory as a filespace only if mmbackup succeeds (exits with 0). We can then monitor the canary and infer the status of the associated GPFS filespace or fileset.
On Wed, Mar 25, 2020 at 10:01:04AM +0000, Jonathan Buzzard wrote: > > What is the best way of monitoring whether or not mmbackup has managed to > complete a backup successfully? > > Traditionally one use a TSM monitoring solution of your choice to make sure > nodes where backing up (I am assuming mmbackup is being used in conjunction > with TSM here). > > However mmbackup does not update the backup_end column in the filespaceview > table (at least in 4.2) which makes things rather more complicated. > > The best I can come up with is querying the events table to see if the > client schedule completed, but that gives a false sense of security as the > schedule completing does not mean the backup completed as far as I know. > > What solutions are you all using, or does mmbackup in 5.x update the > filespaceview table? -- -- Skylar Thompson (skyl...@u.washington.edu) -- Genome Sciences Department, System Administrator -- Foege Building S046, (206)-685-7354 -- University of Washington School of Medicine _______________________________________________ gpfsug-discuss mailing list gpfsug-discuss at spectrumscale.org http://gpfsug.org/mailman/listinfo/gpfsug-discuss
