Now we've seen different to this... But maybe it depends how you run mmbackup multiple times.
We have several nodes which are backing up via Spectrum Protect, and we thought it would be nice to have the client scheduler running on multiple nodes, we assumed it would only actually run one instance of the backup. Not so. We've seen two client schedulers kick off mmbackup (each then I think running across several nodes). Simon From: <[email protected]<mailto:[email protected]>> on behalf of Craig Wilson <[email protected]<mailto:[email protected]>> Reply-To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Date: Friday, 27 May 2016 at 11:32 To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: Re: [gpfsug-discuss] mmbackup - Two at a time? Hi Scott I've not tried this one 4.# branch as I'm still running 3.5 but on 3.5 you get a error message saying: mmbackup: Failed to obtain the local environment update lock. mmbackup: Command failed. Examine previous error messages to determine cause. The old mmbackup keeps running through. Kind Regards, Craig Wilson. HPC Systems Engineer OCF Plc. On 26 May 2016 at 16:57, Scott Cumbie <[email protected]<mailto:[email protected]>> wrote: Just wondering if anyone has a quick answer to this question. If mmbackup is running on a filesystem and a second mmbackup is executed on the same filesystem, what happens? Does the second one end because the first one is running? Thanks, Scott _______________________________________________ gpfsug-discuss mailing list gpfsug-discuss at spectrumscale.org<http://spectrumscale.org> http://gpfsug.org/mailman/listinfo/gpfsug-discuss
_______________________________________________ gpfsug-discuss mailing list gpfsug-discuss at spectrumscale.org http://gpfsug.org/mailman/listinfo/gpfsug-discuss
