Awesome, thanks all. Looks like FirstJobId is what I need. We know what the final job id was used for the final job.
Thanks! ---------------- Mike Hanby mhanby @ uab.edu Systems Analyst II - Enterprise IT Research Computing Services The University of Alabama at Birmingham From: slurm-users <slurm-users-boun...@lists.schedmd.com> on behalf of Brian Johanson <bjoha...@psc.edu> Reply-To: Slurm User Community List <slurm-users@lists.schedmd.com> Date: Monday, December 24, 2018 at 10:17 AM To: "slurm-users@lists.schedmd.com" <slurm-users@lists.schedmd.com> Subject: Re: [slurm-users] Restore Last JOBID After Reinstall of Slurm Master Node? If that is lost, you can manually set it in slurm.conf with FirstJobId -b On 12/24/2018 1:09 AM, Sean Caron wrote: On Mon, Dec 24, 2018 at 12:13 AM Hanby, Mike <mha...@uab.edu<mailto:mha...@uab.edu>> wrote: Howdy, We installed a new server to take over the duties of the Slurm master. I imported our accounting database into MySQL, copied config files etc.. Apparently I missed the “file” that contains the last (or is it next) JOBID to assign to the next job. The first job submitted to the new master started at 1. Where is this information stored / can I manually set it so that we aren’t starting over / battling duplicate JOBIDs in the accounting information? Thanks, MIke Hi Mike, You need to copy the files from your configured StateSaveLocation to the new controller instance to preserve the job IDs and etc. Best, Sean