https://wiki.umiacs.umd.edu/umiacs/api.php?action=feedcontributions&feedformat=atom&user=WrichmanUMIACS - User contributions [en]2026-05-09T18:41:30ZUser contributionsMediaWiki 1.43.7https://wiki.umiacs.umd.edu/umiacs/index.php?title=SLURM&diff=9520SLURM2020-12-18T17:21:03Z<p>Wrichman: </p>
<hr />
<div>=Simple Linux Utility for Resource Management (SLURM)=<br />
SLURM is an open-source workload manager designed for Linux clusters of all sizes. It provides three key functions. First, it allocates exclusive or non-exclusive access to resources (computer nodes) to users for some duration of time so they can perform work. Second, it provides a framework for starting, executing, and monitoring work (typically a parallel job) on a set of allocated nodes. Finally, it arbitrates contention for resources by managing a queue of pending work.<br />
<br />
==Documentation==<br />
:[[SLURM/JobSubmission | Submitting Jobs]]<br />
:[[SLURM/JobStatus | Checking Job Status]]<br />
:[[SLURM/ClusterStatus | Checking Cluster Status]]<br />
:[http://slurm.schedmd.com/documentation.html Official Documentation]<br />
:[http://slurm.schedmd.com/faq.html FAQ]<br />
<br />
==Commands==<br />
Below are some of the common commands used in Slurm. Further information on how to use these commands is found in the documentation linked above. To see all flags available for a command, please check the command's manual by using <code>man $COMMAND</code> on the command line.<br />
<br />
====srun====<br />
srun runs a parallel job on a cluster managed by Slurm. If necessary, it will first create a resource allocation in which to run the parallel job.<br />
<br />
====salloc====<br />
salloc allocates a Slurm job allocation, which is a set of resources (nodes), possibly with some set of constraints (e.g. number of processors per node). When salloc successfully obtains the requested allocation, it then runs the command specified by the user. Finally, when the user specified command is complete, salloc relinquishes the job allocation. If no command is specified, salloc runs the user's default shell.<br />
<br />
====sbatch====<br />
sbatch submits a batch script to Slurm. The batch script may be given to sbatch through a file name on the command line, or if no file name is specified, sbatch will read in a script from standard input. The batch script may contain options preceded with "#SBATCH" before any executable commands in the script.<br />
<br />
====squeue====<br />
squeue views job and job step information for jobs managed by Slurm.<br />
<br />
====scancel====<br />
scancel signals or cancels jobs, job arrays, or job steps. An arbitrary number of jobs or job steps may be signaled using job specification filters or a space separated list of specific job and/or job step IDs.<br />
<br />
====sacct====<br />
sacct displays job accounting data stored in the job accounting log file or Slurm database in a variety of forms for your analysis. The sacct command displays information on jobs, job steps, status, and exitcodes by default. You can tailor the output with the use of the --format= option to specify the fields to be shown.<br />
<br />
====sstat====<br />
sstat displays job status information for your analysis. The sstat command displays information pertaining to CPU, Task, Node, Resident Set Size (RSS) and Virtual Memory (VM). You can tailor the output with the use of the --fields= option to specify the fields to be shown.<br />
<br />
==Modules==<br />
If you are trying to use [[Modules | GNU Modules]] in a Slurm job, please read the section of our [[Modules]] documentation on [[Modules#Modules_in_Non-Interactive_Shell_Sessions | non-interactive shell sessions]].<br />
<br />
==Running Jupyter Notebook on a Compute Node==<br />
The steps to run a Jupyter Notebook from a compute node are listed below.<br />
<br />
<h6>Setting up Python Virtual Environment</h6><br />
In order to set up your python virtual environment, you'll first want to follow the steps listed [https://wiki.umiacs.umd.edu/umiacs/index.php/PythonVirtualEnv here] to create a Python virtual environment on the compute node you are assigned. Then, activate it using the steps listed [https://wiki.umiacs.umd.edu/umiacs/index.php/PythonVirtualEnv#Activating_the_VirtualEnv here]. Next, install Jupyter using pip by following the steps [https://jupyter.readthedocs.io/en/latest/install/notebook-classic.html#alternative-for-experienced-python-users-installing-jupyter-with-pip here].<br />
<br />
<h6> Running Jupyter Notebook </h6><br />
After you've set up the python virtual environment, run the following commands on the compute node you are assigned:<br />
<pre><br />
jupyter notebook --no-browser --port=8889 --ip=0.0.0.0<br />
</pre><br />
This will start running the notebook on port 8889. <b>Note:</b> You must keep this shell window open to be able to connect.<br />
Then, on your local machine, run <br />
<pre><br />
ssh -N -f -L localhost:8888:$(NODENAME):8889 $(USERNAME)@$(SUBMISSIONNODE).umiacs.umd.edu<br />
</pre> <br />
This will tunnel port 8889 from the compute node to port 8888 on your local machine, using the $(SUBMISSIONNODE) as an intermediate node. Make sure to replace $(NODENAME) with the name of the compute node you are assigned, $(USERNAME) with your username, and $(SUBMISSIONNODE) with the name of the submission node you want to use. For example, <code>esloate@clipsub00.umiacs.umd.edu</code>. Also, if the ports mentioned above are not working, then you can replace them with whatever port you'd like, just make sure to change it in the command you ran on the compute node. You can then open a web browser and type in <code>localhost:8888</code> to access the notebook. <b>Note:</b> You must be on a machine connected to the UMIACS network or connected to our [[Network/VPN | VPN]] in order to access the Jupyter notebook.<br />
<br />
<br />
=Quick Guide to translate PBS/Torque to SLURM=<br />
<br />
{| class="wikitable"<br />
|+User commands<br />
|-<br />
!<br />
!PBS/Torque<br />
!SLURM<br />
|-<br />
!Job submission<br />
|qsub [filename]<br />
|sbatch [filename]<br />
|-<br />
!Job deletion<br />
|qdel [job_id]<br />
|scancel [job_id]<br />
|-<br />
!Job status (by job)<br />
|qstat [job_id] <br />
|squeue --job [job_id]<br />
|-<br />
!Full job status (by job)<br />
|qstat -f [job_id]<br />
|scontrol show job [job_id]<br />
|-<br />
!Job status (by user)<br />
|qstat -u [username]<br />
|squeue --user=[username]<br />
|}<br />
<br />
{| class="wikitable"<br />
|+Environment variables<br />
|-<br />
!<br />
!PBS/Torque <br />
!SLURM<br />
|-<br />
!Job ID<br />
|$PBS_JOBID<br />
|$SLURM_JOBID<br />
|-<br />
!Submit Directory<br />
|$PBS_O_WORKDIR<br />
|$SLURM_SUBMIT_DIR<br />
|-<br />
!Node List <br />
|$PBS_NODEFILE<br />
|$SLURM_JOB_NODELIST<br />
|}<br />
<br />
{| class="wikitable"<br />
|+Job specification<br />
|-<br />
!<br />
!PBS/Torque <br />
!SLURM<br />
|-<br />
!Script directive<br />
|#PBS<br />
|#SBATCH<br />
|-<br />
!Job Name <br />
| -N [name]<br />
| --job-name=[name] OR -J [name]<br />
|-<br />
!Node Count<br />
| -l nodes=[count]<br />
| --nodes=[min[-max]] OR -N [min[-max]]<br />
|-<br />
!CPU Count<br />
| -l ppn=[count]<br />
| --ntasks-per-node=[count]<br />
|-<br />
!CPUs Per Task<br />
|<br />
| --cpus-per-task=[count]<br />
|-<br />
!Memory Size<br />
| -l mem=[MB] <br />
| --mem=[MB] OR --mem-per-cpu=[MB]<br />
|-<br />
!Wall Clock Limit<br />
| -l walltime=[hh:mm:ss]<br />
| --time=[min] OR --time=[days-hh:mm:ss]<br />
|-<br />
!Node Properties<br />
| -l nodes=4:ppn=8:[property]<br />
| --constraint=[list]<br />
|-<br />
!Standard Output File<br />
| -o [file_name]<br />
| --output=[file_name] OR -o [file_name]<br />
|-<br />
!Standard Error File<br />
| -e [file_name]<br />
| --error=[file_name] OR -e [file_name]<br />
|-<br />
!Combine stdout/stderr<br />
| -j oe (both to stdout)<br />
|(Default if you don't specify --error)<br />
|-<br />
!Job Arrays<br />
| -t [array_spec]<br />
| --array=[array_spec] OR -a [array_spec]<br />
|-<br />
!Delay Job Start<br />
| -a [time]<br />
| --begin=[time]<br />
|}</div>Wrichmanhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=SLURM&diff=9518SLURM2020-12-15T22:27:52Z<p>Wrichman: </p>
<hr />
<div>=Simple Linux Utility for Resource Management (SLURM)=<br />
SLURM is an open-source workload manager designed for Linux clusters of all sizes. It provides three key functions. First, it allocates exclusive or non-exclusive access to resources (computer nodes) to users for some duration of time so they can perform work. Second, it provides a framework for starting, executing, and monitoring work (typically a parallel job) on a set of allocated nodes. Finally, it arbitrates contention for resources by managing a queue of pending work.<br />
<br />
==Documentation==<br />
:[[SLURM/JobSubmission | Submitting Jobs]]<br />
:[[SLURM/JobStatus | Checking Job Status]]<br />
:[[SLURM/ClusterStatus | Checking Cluster Status]]<br />
:[http://slurm.schedmd.com/documentation.html Official Documentation]<br />
:[http://slurm.schedmd.com/faq.html FAQ]<br />
<br />
==Commands==<br />
Below are some of the common commands used in Slurm. Further information on how to use these commands is found in the documentation linked above. To see all flags available for a command, please check the command's manual by using <code>man $COMMAND</code> on the command line.<br />
<br />
====srun====<br />
srun runs a parallel job on a cluster managed by Slurm. If necessary, it will first create a resource allocation in which to run the parallel job.<br />
<br />
====salloc====<br />
salloc allocates a Slurm job allocation, which is a set of resources (nodes), possibly with some set of constraints (e.g. number of processors per node). When salloc successfully obtains the requested allocation, it then runs the command specified by the user. Finally, when the user specified command is complete, salloc relinquishes the job allocation. If no command is specified, salloc runs the user's default shell.<br />
<br />
====sbatch====<br />
sbatch submits a batch script to Slurm. The batch script may be given to sbatch through a file name on the command line, or if no file name is specified, sbatch will read in a script from standard input. The batch script may contain options preceded with "#SBATCH" before any executable commands in the script.<br />
<br />
====squeue====<br />
squeue views job and job step information for jobs managed by Slurm.<br />
<br />
====scancel====<br />
scancel signals or cancels jobs, job arrays, or job steps. An arbitrary number of jobs or job steps may be signaled using job specification filters or a space separated list of specific job and/or job step IDs.<br />
<br />
====sacct====<br />
sacct displays job accounting data stored in the job accounting log file or Slurm database in a variety of forms for your analysis. The sacct command displays information on jobs, job steps, status, and exitcodes by default. You can tailor the output with the use of the --format= option to specify the fields to be shown.<br />
<br />
====sstat====<br />
sstat displays job status information for your analysis. The sstat command displays information pertaining to CPU, Task, Node, Resident Set Size (RSS) and Virtual Memory (VM). You can tailor the output with the use of the --fields= option to specify the fields to be shown.<br />
<br />
==Modules==<br />
If you are trying to use [[Modules | GNU Modules]] in a Slurm job, please read the section of our [[Modules]] documentation on [[Modules#Modules_in_Non-Interactive_Shell_Sessions | non-interactive shell sessions]].<br />
<br />
==Running Jupyter Notebook on a Compute Node==<br />
The steps to run a Jupyter Notebook from a compute node are listed below.<br />
<br />
<h6>Setting up Python Virtual Environment</h6><br />
In order to set up your python virtual environment, you'll first want to follow the steps listed [https://wiki.umiacs.umd.edu/umiacs/index.php/PythonVirtualEnv here] to create a Python virtual environment on the compute node you are assigned. Then, activate it using the steps listed [https://wiki.umiacs.umd.edu/umiacs/index.php/PythonVirtualEnv#Activating_the_VirtualEnv here]. Next, install Jupyter using pip by following the steps [https://jupyter.readthedocs.io/en/latest/install/notebook-classic.html#alternative-for-experienced-python-users-installing-jupyter-with-pip here].<br />
<br />
<h6> Running Jupyter Notebook </h6><br />
After you've set up the python virtual environment, run the following commands on the compute node you are assigned:<br />
<pre><br />
jupyter notebook --no-browser --port=8889 --ip=0.0.0.0<br />
</pre><br />
This will start running the notebook on port 8889. <b>Note:</b> You must keep this shell window open to be able to connect.<br />
Then, on your local machine, run <br />
<pre><br />
ssh -N -f -L localhost:8888:$(NODENAME):8889 $(USERNAME)@$(CLUSTERNAME).umiacs.umd.edu<br />
</pre> <br />
This will tunnel port 8889 from the compute node to port 8888 on your local machine, using the $(CLUSTERNAME) node as an intermediate node. Make sure to replace $(NODENAME) with the name of the compute node you are assigned, $(USERNAME) with your username, and $(CLUSTERNAME) with the name of the compute cluster you are using. For example, <code>esloate@clipsub00.umiacs.umd.edu</code>. Also, if the ports mentioned above are not working, then you can replace them with whatever port you'd like, just make sure to change it in the command you ran on the compute node. You can then open a web browser and type in <code>localhost:8888</code> to access the notebook. <b>Note:</b> You must be on a machine connected to the UMIACS network or connected to our [[Network/VPN | VPN]] in order to access the Jupyter notebook.<br />
<br />
<br />
=Quick Guide to translate PBS/Torque to SLURM=<br />
<br />
{| class="wikitable"<br />
|+User commands<br />
|-<br />
!<br />
!PBS/Torque<br />
!SLURM<br />
|-<br />
!Job submission<br />
|qsub [filename]<br />
|sbatch [filename]<br />
|-<br />
!Job deletion<br />
|qdel [job_id]<br />
|scancel [job_id]<br />
|-<br />
!Job status (by job)<br />
|qstat [job_id] <br />
|squeue --job [job_id]<br />
|-<br />
!Full job status (by job)<br />
|qstat -f [job_id]<br />
|scontrol show job [job_id]<br />
|-<br />
!Job status (by user)<br />
|qstat -u [username]<br />
|squeue --user=[username]<br />
|}<br />
<br />
{| class="wikitable"<br />
|+Environment variables<br />
|-<br />
!<br />
!PBS/Torque <br />
!SLURM<br />
|-<br />
!Job ID<br />
|$PBS_JOBID<br />
|$SLURM_JOBID<br />
|-<br />
!Submit Directory<br />
|$PBS_O_WORKDIR<br />
|$SLURM_SUBMIT_DIR<br />
|-<br />
!Node List <br />
|$PBS_NODEFILE<br />
|$SLURM_JOB_NODELIST<br />
|}<br />
<br />
{| class="wikitable"<br />
|+Job specification<br />
|-<br />
!<br />
!PBS/Torque <br />
!SLURM<br />
|-<br />
!Script directive<br />
|#PBS<br />
|#SBATCH<br />
|-<br />
!Job Name <br />
| -N [name]<br />
| --job-name=[name] OR -J [name]<br />
|-<br />
!Node Count<br />
| -l nodes=[count]<br />
| --nodes=[min[-max]] OR -N [min[-max]]<br />
|-<br />
!CPU Count<br />
| -l ppn=[count]<br />
| --ntasks-per-node=[count]<br />
|-<br />
!CPUs Per Task<br />
|<br />
| --cpus-per-task=[count]<br />
|-<br />
!Memory Size<br />
| -l mem=[MB] <br />
| --mem=[MB] OR --mem-per-cpu=[MB]<br />
|-<br />
!Wall Clock Limit<br />
| -l walltime=[hh:mm:ss]<br />
| --time=[min] OR --time=[days-hh:mm:ss]<br />
|-<br />
!Node Properties<br />
| -l nodes=4:ppn=8:[property]<br />
| --constraint=[list]<br />
|-<br />
!Standard Output File<br />
| -o [file_name]<br />
| --output=[file_name] OR -o [file_name]<br />
|-<br />
!Standard Error File<br />
| -e [file_name]<br />
| --error=[file_name] OR -e [file_name]<br />
|-<br />
!Combine stdout/stderr<br />
| -j oe (both to stdout)<br />
|(Default if you don't specify --error)<br />
|-<br />
!Job Arrays<br />
| -t [array_spec]<br />
| --array=[array_spec] OR -a [array_spec]<br />
|-<br />
!Delay Job Start<br />
| -a [time]<br />
| --begin=[time]<br />
|}</div>Wrichmanhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=SLURM&diff=9517SLURM2020-12-15T22:24:09Z<p>Wrichman: </p>
<hr />
<div>=Simple Linux Utility for Resource Management (SLURM)=<br />
SLURM is an open-source workload manager designed for Linux clusters of all sizes. It provides three key functions. First, it allocates exclusive or non-exclusive access to resources (computer nodes) to users for some duration of time so they can perform work. Second, it provides a framework for starting, executing, and monitoring work (typically a parallel job) on a set of allocated nodes. Finally, it arbitrates contention for resources by managing a queue of pending work.<br />
<br />
==Documentation==<br />
:[[SLURM/JobSubmission | Submitting Jobs]]<br />
:[[SLURM/JobStatus | Checking Job Status]]<br />
:[[SLURM/ClusterStatus | Checking Cluster Status]]<br />
:[http://slurm.schedmd.com/documentation.html Official Documentation]<br />
:[http://slurm.schedmd.com/faq.html FAQ]<br />
<br />
==Commands==<br />
Below are some of the common commands used in Slurm. Further information on how to use these commands is found in the documentation linked above. To see all flags available for a command, please check the command's manual by using <code>man $COMMAND</code> on the command line.<br />
<br />
====srun====<br />
srun runs a parallel job on a cluster managed by Slurm. If necessary, it will first create a resource allocation in which to run the parallel job.<br />
<br />
====salloc====<br />
salloc allocates a Slurm job allocation, which is a set of resources (nodes), possibly with some set of constraints (e.g. number of processors per node). When salloc successfully obtains the requested allocation, it then runs the command specified by the user. Finally, when the user specified command is complete, salloc relinquishes the job allocation. If no command is specified, salloc runs the user's default shell.<br />
<br />
====sbatch====<br />
sbatch submits a batch script to Slurm. The batch script may be given to sbatch through a file name on the command line, or if no file name is specified, sbatch will read in a script from standard input. The batch script may contain options preceded with "#SBATCH" before any executable commands in the script.<br />
<br />
====squeue====<br />
squeue views job and job step information for jobs managed by Slurm.<br />
<br />
====scancel====<br />
scancel signals or cancels jobs, job arrays, or job steps. An arbitrary number of jobs or job steps may be signaled using job specification filters or a space separated list of specific job and/or job step IDs.<br />
<br />
====sacct====<br />
sacct displays job accounting data stored in the job accounting log file or Slurm database in a variety of forms for your analysis. The sacct command displays information on jobs, job steps, status, and exitcodes by default. You can tailor the output with the use of the --format= option to specify the fields to be shown.<br />
<br />
====sstat====<br />
sstat displays job status information for your analysis. The sstat command displays information pertaining to CPU, Task, Node, Resident Set Size (RSS) and Virtual Memory (VM). You can tailor the output with the use of the --fields= option to specify the fields to be shown.<br />
<br />
==Modules==<br />
If you are trying to use [[Modules | GNU Modules]] in a Slurm job, please read the section of our [[Modules]] documentation on [[Modules#Modules_in_Non-Interactive_Shell_Sessions | non-interactive shell sessions]].<br />
<br />
==Running Jupyter Notebook on a Compute Node==<br />
The steps to run a Jupyter Notebook from a compute node are listed below.<br />
<br />
<h6>Setting up Python Virtual Environment</h6><br />
In order to set up your python virtual environment, you'll first want to follow the steps listed [https://wiki.umiacs.umd.edu/umiacs/index.php/PythonVirtualEnv here] to create a Python virtual environment on the compute node you are assigned. Then, activate it using the steps listed [https://wiki.umiacs.umd.edu/umiacs/index.php/PythonVirtualEnv#Activating_the_VirtualEnv here]. Next, install Jupyter using pip by following the steps [https://jupyter.readthedocs.io/en/latest/install/notebook-classic.html#alternative-for-experienced-python-users-installing-jupyter-with-pip here].<br />
<br />
<h6> Running Jupyter Notebook </h6><br />
After you've set up the python virtual environment, run the following commands on the compute node you are assigned:<br />
<pre><br />
jupyter notebook --no-browser --port=8889 --ip=0.0.0.0<br />
</pre><br />
This will start running the notebook on port 8889. <b>Note:</b> You must keep this shell window open to be able to connect.<br />
Then, on your local machine, run <br />
<pre><br />
ssh -N -f -L localhost:8888:$(NODENAME):8889 $(USERNAME)@$(CLUSTERNAME).umiacs.umd.edu<br />
</pre> <br />
This will tunnel port 8889 from the compute node to port 8888 on your local machine, using the (CLUSTERNAME)sub00 node as an intermediate node. Make sure to replace $(NODENAME) with the name of the compute node you are assigned, $(USERNAME) with your username, and $(CLUSTERNAME) with the name of the compute cluster you are using. For example, <code>esloate@clipsub00.umiacs.umd.edu</code>. Also, if the ports mentioned above are not working, then you can replace them with whatever port you'd like, just make sure to change it in the command you ran on the compute node. You can then open a web browser and type in <code>localhost:8888</code> to access the notebook. <b>Note:</b> You must be on a machine connected to the UMIACS network or connected to our [[Network/VPN | VPN]] in order to access the Jupyter notebook.<br />
<br />
<br />
=Quick Guide to translate PBS/Torque to SLURM=<br />
<br />
{| class="wikitable"<br />
|+User commands<br />
|-<br />
!<br />
!PBS/Torque<br />
!SLURM<br />
|-<br />
!Job submission<br />
|qsub [filename]<br />
|sbatch [filename]<br />
|-<br />
!Job deletion<br />
|qdel [job_id]<br />
|scancel [job_id]<br />
|-<br />
!Job status (by job)<br />
|qstat [job_id] <br />
|squeue --job [job_id]<br />
|-<br />
!Full job status (by job)<br />
|qstat -f [job_id]<br />
|scontrol show job [job_id]<br />
|-<br />
!Job status (by user)<br />
|qstat -u [username]<br />
|squeue --user=[username]<br />
|}<br />
<br />
{| class="wikitable"<br />
|+Environment variables<br />
|-<br />
!<br />
!PBS/Torque <br />
!SLURM<br />
|-<br />
!Job ID<br />
|$PBS_JOBID<br />
|$SLURM_JOBID<br />
|-<br />
!Submit Directory<br />
|$PBS_O_WORKDIR<br />
|$SLURM_SUBMIT_DIR<br />
|-<br />
!Node List <br />
|$PBS_NODEFILE<br />
|$SLURM_JOB_NODELIST<br />
|}<br />
<br />
{| class="wikitable"<br />
|+Job specification<br />
|-<br />
!<br />
!PBS/Torque <br />
!SLURM<br />
|-<br />
!Script directive<br />
|#PBS<br />
|#SBATCH<br />
|-<br />
!Job Name <br />
| -N [name]<br />
| --job-name=[name] OR -J [name]<br />
|-<br />
!Node Count<br />
| -l nodes=[count]<br />
| --nodes=[min[-max]] OR -N [min[-max]]<br />
|-<br />
!CPU Count<br />
| -l ppn=[count]<br />
| --ntasks-per-node=[count]<br />
|-<br />
!CPUs Per Task<br />
|<br />
| --cpus-per-task=[count]<br />
|-<br />
!Memory Size<br />
| -l mem=[MB] <br />
| --mem=[MB] OR --mem-per-cpu=[MB]<br />
|-<br />
!Wall Clock Limit<br />
| -l walltime=[hh:mm:ss]<br />
| --time=[min] OR --time=[days-hh:mm:ss]<br />
|-<br />
!Node Properties<br />
| -l nodes=4:ppn=8:[property]<br />
| --constraint=[list]<br />
|-<br />
!Standard Output File<br />
| -o [file_name]<br />
| --output=[file_name] OR -o [file_name]<br />
|-<br />
!Standard Error File<br />
| -e [file_name]<br />
| --error=[file_name] OR -e [file_name]<br />
|-<br />
!Combine stdout/stderr<br />
| -j oe (both to stdout)<br />
|(Default if you don't specify --error)<br />
|-<br />
!Job Arrays<br />
| -t [array_spec]<br />
| --array=[array_spec] OR -a [array_spec]<br />
|-<br />
!Delay Job Start<br />
| -a [time]<br />
| --begin=[time]<br />
|}</div>Wrichmanhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=SLURM&diff=9514SLURM2020-12-11T15:39:00Z<p>Wrichman: </p>
<hr />
<div>=Simple Linux Utility for Resource Management (SLURM)=<br />
SLURM is an open-source workload manager designed for Linux clusters of all sizes. It provides three key functions. First, it allocates exclusive or non-exclusive access to resources (computer nodes) to users for some duration of time so they can perform work. Second, it provides a framework for starting, executing, and monitoring work (typically a parallel job) on a set of allocated nodes. Finally, it arbitrates contention for resources by managing a queue of pending work.<br />
<br />
==Documentation==<br />
:[[SLURM/JobSubmission | Submitting Jobs]]<br />
:[[SLURM/JobStatus | Checking Job Status]]<br />
:[[SLURM/ClusterStatus | Checking Cluster Status]]<br />
:[http://slurm.schedmd.com/documentation.html Official Documentation]<br />
:[http://slurm.schedmd.com/faq.html FAQ]<br />
<br />
==Commands==<br />
Below are some of the common commands used in Slurm. Further information on how to use these commands is found in the documentation linked above. To see all flags available for a command, please check the command's manual by using <code>man $COMMAND</code> on the command line.<br />
<br />
====srun====<br />
srun runs a parallel job on a cluster managed by Slurm. If necessary, it will first create a resource allocation in which to run the parallel job.<br />
<br />
====salloc====<br />
salloc allocates a Slurm job allocation, which is a set of resources (nodes), possibly with some set of constraints (e.g. number of processors per node). When salloc successfully obtains the requested allocation, it then runs the command specified by the user. Finally, when the user specified command is complete, salloc relinquishes the job allocation. If no command is specified, salloc runs the user's default shell.<br />
<br />
====sbatch====<br />
sbatch submits a batch script to Slurm. The batch script may be given to sbatch through a file name on the command line, or if no file name is specified, sbatch will read in a script from standard input. The batch script may contain options preceded with "#SBATCH" before any executable commands in the script.<br />
<br />
====squeue====<br />
squeue views job and job step information for jobs managed by Slurm.<br />
<br />
====scancel====<br />
scancel signals or cancels jobs, job arrays, or job steps. An arbitrary number of jobs or job steps may be signaled using job specification filters or a space separated list of specific job and/or job step IDs.<br />
<br />
====sacct====<br />
sacct displays job accounting data stored in the job accounting log file or Slurm database in a variety of forms for your analysis. The sacct command displays information on jobs, job steps, status, and exitcodes by default. You can tailor the output with the use of the --format= option to specify the fields to be shown.<br />
<br />
====sstat====<br />
sstat displays job status information for your analysis. The sstat command displays information pertaining to CPU, Task, Node, Resident Set Size (RSS) and Virtual Memory (VM). You can tailor the output with the use of the --fields= option to specify the fields to be shown.<br />
<br />
==Modules==<br />
If you are trying to use [[Modules | GNU Modules]] in a Slurm job, please read the section of our [[Modules]] documentation on [[Modules#Modules_in_Non-Interactive_Shell_Sessions | non-interactive shell sessions]].<br />
<br />
==Running Jupyter Notebook on a Compute Node==<br />
The steps to run a Jupyter Notebook from a compute node are listed below.<br />
<br />
<h6>Setting up Python Virtual Environment</h6><br />
In order to set up your python virtual environment, you'll first want to follow the steps listed [https://wiki.umiacs.umd.edu/umiacs/index.php/PythonVirtualEnv here] to create a Python virtual environment on the compute node you are assigned. Then, activate it using the steps listed [https://wiki.umiacs.umd.edu/umiacs/index.php/PythonVirtualEnv#Activating_the_VirtualEnv here]. Next, install Jupyter using pip by following the steps [https://jupyter.readthedocs.io/en/latest/install/notebook-classic.html#alternative-for-experienced-python-users-installing-jupyter-with-pip here].<br />
<br />
<h6> Running Jupyter Notebook </h6><br />
After you've set up the python virtual environment, run the following commands on the compute node you are assigned:<br />
<pre><br />
jupyter notebook --no-browser --port=8889 --ip=0.0.0.0<br />
</pre><br />
This will start running the notebook on port 8889. <b>Note:</b> You must keep this shell window open to be able to connect.<br />
Then, on your local machine, run <br />
<pre><br />
ssh -N -f -L localhost:8888:$(NODENAME):8889 $(USERNAME)@$(CLUSTERNAME)sub00.umiacs.umd.edu<br />
</pre> <br />
This will tunnel port 8889 from the compute node to port 8888 on your local machine, using the (CLUSTERNAME)sub00 node as an intermediate node. Make sure to replace $(NODENAME) with the name of the compute node you are assigned, $(USERNAME) with your username, and $(CLUSTERNAME) with the name of the compute cluster you are using. For example, <code>esloate@clipsub00.umiacs.umd.edu</code>. Also, if the ports mentioned above are not working, then you can replace them with whatever port you'd like, just make sure to change it in the command you ran on the compute node. You can then open a web browser and type in <code>localhost:8888</code> to access the notebook. <b>Note:</b> You must be on a machine connected to the UMIACS network or connected to our [[Network/VPN | VPN]] in order to access the Jupyter notebook.<br />
<br />
<br />
=Quick Guide to translate PBS/Torque to SLURM=<br />
<br />
{| class="wikitable"<br />
|+User commands<br />
|-<br />
!<br />
!PBS/Torque<br />
!SLURM<br />
|-<br />
!Job submission<br />
|qsub [filename]<br />
|sbatch [filename]<br />
|-<br />
!Job deletion<br />
|qdel [job_id]<br />
|scancel [job_id]<br />
|-<br />
!Job status (by job)<br />
|qstat [job_id] <br />
|squeue --job [job_id]<br />
|-<br />
!Full job status (by job)<br />
|qstat -f [job_id]<br />
|scontrol show job [job_id]<br />
|-<br />
!Job status (by user)<br />
|qstat -u [username]<br />
|squeue --user=[username]<br />
|}<br />
<br />
{| class="wikitable"<br />
|+Environment variables<br />
|-<br />
!<br />
!PBS/Torque <br />
!SLURM<br />
|-<br />
!Job ID<br />
|$PBS_JOBID<br />
|$SLURM_JOBID<br />
|-<br />
!Submit Directory<br />
|$PBS_O_WORKDIR<br />
|$SLURM_SUBMIT_DIR<br />
|-<br />
!Node List <br />
|$PBS_NODEFILE<br />
|$SLURM_JOB_NODELIST<br />
|}<br />
<br />
{| class="wikitable"<br />
|+Job specification<br />
|-<br />
!<br />
!PBS/Torque <br />
!SLURM<br />
|-<br />
!Script directive<br />
|#PBS<br />
|#SBATCH<br />
|-<br />
!Job Name <br />
| -N [name]<br />
| --job-name=[name] OR -J [name]<br />
|-<br />
!Node Count<br />
| -l nodes=[count]<br />
| --nodes=[min[-max]] OR -N [min[-max]]<br />
|-<br />
!CPU Count<br />
| -l ppn=[count]<br />
| --ntasks-per-node=[count]<br />
|-<br />
!CPUs Per Task<br />
|<br />
| --cpus-per-task=[count]<br />
|-<br />
!Memory Size<br />
| -l mem=[MB] <br />
| --mem=[MB] OR --mem-per-cpu=[MB]<br />
|-<br />
!Wall Clock Limit<br />
| -l walltime=[hh:mm:ss]<br />
| --time=[min] OR --time=[days-hh:mm:ss]<br />
|-<br />
!Node Properties<br />
| -l nodes=4:ppn=8:[property]<br />
| --constraint=[list]<br />
|-<br />
!Standard Output File<br />
| -o [file_name]<br />
| --output=[file_name] OR -o [file_name]<br />
|-<br />
!Standard Error File<br />
| -e [file_name]<br />
| --error=[file_name] OR -e [file_name]<br />
|-<br />
!Combine stdout/stderr<br />
| -j oe (both to stdout)<br />
|(Default if you don't specify --error)<br />
|-<br />
!Job Arrays<br />
| -t [array_spec]<br />
| --array=[array_spec] OR -a [array_spec]<br />
|-<br />
!Delay Job Start<br />
| -a [time]<br />
| --begin=[time]<br />
|}</div>Wrichmanhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=SLURM&diff=9513SLURM2020-12-11T15:36:39Z<p>Wrichman: </p>
<hr />
<div>=Simple Linux Utility for Resource Management (SLURM)=<br />
SLURM is an open-source workload manager designed for Linux clusters of all sizes. It provides three key functions. First, it allocates exclusive or non-exclusive access to resources (computer nodes) to users for some duration of time so they can perform work. Second, it provides a framework for starting, executing, and monitoring work (typically a parallel job) on a set of allocated nodes. Finally, it arbitrates contention for resources by managing a queue of pending work.<br />
<br />
==Documentation==<br />
:[[SLURM/JobSubmission | Submitting Jobs]]<br />
:[[SLURM/JobStatus | Checking Job Status]]<br />
:[[SLURM/ClusterStatus | Checking Cluster Status]]<br />
:[http://slurm.schedmd.com/documentation.html Official Documentation]<br />
:[http://slurm.schedmd.com/faq.html FAQ]<br />
<br />
==Commands==<br />
Below are some of the common commands used in Slurm. Further information on how to use these commands is found in the documentation linked above. To see all flags available for a command, please check the command's manual by using <code>man $COMMAND</code> on the command line.<br />
<br />
====srun====<br />
srun runs a parallel job on a cluster managed by Slurm. If necessary, it will first create a resource allocation in which to run the parallel job.<br />
<br />
====salloc====<br />
salloc allocates a Slurm job allocation, which is a set of resources (nodes), possibly with some set of constraints (e.g. number of processors per node). When salloc successfully obtains the requested allocation, it then runs the command specified by the user. Finally, when the user specified command is complete, salloc relinquishes the job allocation. If no command is specified, salloc runs the user's default shell.<br />
<br />
====sbatch====<br />
sbatch submits a batch script to Slurm. The batch script may be given to sbatch through a file name on the command line, or if no file name is specified, sbatch will read in a script from standard input. The batch script may contain options preceded with "#SBATCH" before any executable commands in the script.<br />
<br />
====squeue====<br />
squeue views job and job step information for jobs managed by Slurm.<br />
<br />
====scancel====<br />
scancel signals or cancels jobs, job arrays, or job steps. An arbitrary number of jobs or job steps may be signaled using job specification filters or a space separated list of specific job and/or job step IDs.<br />
<br />
====sacct====<br />
sacct displays job accounting data stored in the job accounting log file or Slurm database in a variety of forms for your analysis. The sacct command displays information on jobs, job steps, status, and exitcodes by default. You can tailor the output with the use of the --format= option to specify the fields to be shown.<br />
<br />
====sstat====<br />
sstat displays job status information for your analysis. The sstat command displays information pertaining to CPU, Task, Node, Resident Set Size (RSS) and Virtual Memory (VM). You can tailor the output with the use of the --fields= option to specify the fields to be shown.<br />
<br />
==Modules==<br />
If you are trying to use [[Modules | GNU Modules]] in a Slurm job, please read the section of our [[Modules]] documentation on [[Modules#Modules_in_Non-Interactive_Shell_Sessions | non-interactive shell sessions]].<br />
<br />
==Running Jupyter Notebook on a Compute Node==<br />
The steps to run a Jupyter Notebook from a compute node are listed below.<br />
<br />
<h6>Setting up Python Virtual Environment</h6><br />
In order to set up your python virtual environment, you'll first want to follow the steps listed [https://wiki.umiacs.umd.edu/umiacs/index.php/PythonVirtualEnv here] to create a Python virtual environment on the compute node you are assigned. Then, activate it using the steps listed [https://wiki.umiacs.umd.edu/umiacs/index.php/PythonVirtualEnv#Activating_the_VirtualEnv here]. Next, install Jupyter using pip by following the steps [https://jupyter.readthedocs.io/en/latest/install/notebook-classic.html#alternative-for-experienced-python-users-installing-jupyter-with-pip here].<br />
<br />
<h6> Running Jupyter Notebook </h6><br />
After you've set up the python virtual environment, run the following commands on the compute node you are assigned:<br />
<pre><br />
jupyter notebook --no-browser --port=8889 --ip=0.0.0.0<br />
</pre><br />
This will start running the notebook on port 8889. <b>Note:</b> You must keep this shell window open to be able to connect.<br />
Then, on your local machine, run <br />
<pre><br />
ssh -N -f -L localhost:8888:$(NODENAME):8889 $(USERNAME)@$(CLUSTERNAME)sub00.umiacs.umd.edu<br />
</pre> <br />
This will tunnel port 8889 from the compute node to port 8888 on your local machine, using the (CLUSTERNAME)sub00 node as an intermediate node. Make sure to replace $(NODENAME) with the name of the compute node you are assigned, $(USERNAME) with your username, and $(CLUSTERNAME) with the name of the compute cluster you are using. For example, esloate@clipsub00.umiacs.umd.edu. Also, if the ports mentioned above are not working, then you can replace them with whatever port you'd like, just make sure to change it in the command you ran on the compute node. You can then open a web browser and type in <code>localhost:8888</code> to access the notebook. <b>Note:</b> You must be on a machine connected to the UMIACS network or connected to our [[Network/VPN | VPN]] in order to access the Jupyter notebook.<br />
<br />
<br />
=Quick Guide to translate PBS/Torque to SLURM=<br />
<br />
{| class="wikitable"<br />
|+User commands<br />
|-<br />
!<br />
!PBS/Torque<br />
!SLURM<br />
|-<br />
!Job submission<br />
|qsub [filename]<br />
|sbatch [filename]<br />
|-<br />
!Job deletion<br />
|qdel [job_id]<br />
|scancel [job_id]<br />
|-<br />
!Job status (by job)<br />
|qstat [job_id] <br />
|squeue --job [job_id]<br />
|-<br />
!Full job status (by job)<br />
|qstat -f [job_id]<br />
|scontrol show job [job_id]<br />
|-<br />
!Job status (by user)<br />
|qstat -u [username]<br />
|squeue --user=[username]<br />
|}<br />
<br />
{| class="wikitable"<br />
|+Environment variables<br />
|-<br />
!<br />
!PBS/Torque <br />
!SLURM<br />
|-<br />
!Job ID<br />
|$PBS_JOBID<br />
|$SLURM_JOBID<br />
|-<br />
!Submit Directory<br />
|$PBS_O_WORKDIR<br />
|$SLURM_SUBMIT_DIR<br />
|-<br />
!Node List <br />
|$PBS_NODEFILE<br />
|$SLURM_JOB_NODELIST<br />
|}<br />
<br />
{| class="wikitable"<br />
|+Job specification<br />
|-<br />
!<br />
!PBS/Torque <br />
!SLURM<br />
|-<br />
!Script directive<br />
|#PBS<br />
|#SBATCH<br />
|-<br />
!Job Name <br />
| -N [name]<br />
| --job-name=[name] OR -J [name]<br />
|-<br />
!Node Count<br />
| -l nodes=[count]<br />
| --nodes=[min[-max]] OR -N [min[-max]]<br />
|-<br />
!CPU Count<br />
| -l ppn=[count]<br />
| --ntasks-per-node=[count]<br />
|-<br />
!CPUs Per Task<br />
|<br />
| --cpus-per-task=[count]<br />
|-<br />
!Memory Size<br />
| -l mem=[MB] <br />
| --mem=[MB] OR --mem-per-cpu=[MB]<br />
|-<br />
!Wall Clock Limit<br />
| -l walltime=[hh:mm:ss]<br />
| --time=[min] OR --time=[days-hh:mm:ss]<br />
|-<br />
!Node Properties<br />
| -l nodes=4:ppn=8:[property]<br />
| --constraint=[list]<br />
|-<br />
!Standard Output File<br />
| -o [file_name]<br />
| --output=[file_name] OR -o [file_name]<br />
|-<br />
!Standard Error File<br />
| -e [file_name]<br />
| --error=[file_name] OR -e [file_name]<br />
|-<br />
!Combine stdout/stderr<br />
| -j oe (both to stdout)<br />
|(Default if you don't specify --error)<br />
|-<br />
!Job Arrays<br />
| -t [array_spec]<br />
| --array=[array_spec] OR -a [array_spec]<br />
|-<br />
!Delay Job Start<br />
| -a [time]<br />
| --begin=[time]<br />
|}</div>Wrichmanhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=SLURM&diff=9512SLURM2020-12-09T18:23:30Z<p>Wrichman: Added information about using Jupyter Notebook on a compute node</p>
<hr />
<div>=Simple Linux Utility for Resource Management (SLURM)=<br />
SLURM is an open-source workload manager designed for Linux clusters of all sizes. It provides three key functions. First, it allocates exclusive or non-exclusive access to resources (computer nodes) to users for some duration of time so they can perform work. Second, it provides a framework for starting, executing, and monitoring work (typically a parallel job) on a set of allocated nodes. Finally, it arbitrates contention for resources by managing a queue of pending work.<br />
<br />
==Documentation==<br />
:[[SLURM/JobSubmission | Submitting Jobs]]<br />
:[[SLURM/JobStatus | Checking Job Status]]<br />
:[[SLURM/ClusterStatus | Checking Cluster Status]]<br />
:[http://slurm.schedmd.com/documentation.html Official Documentation]<br />
:[http://slurm.schedmd.com/faq.html FAQ]<br />
<br />
==Commands==<br />
Below are some of the common commands used in Slurm. Further information on how to use these commands is found in the documentation linked above. To see all flags available for a command, please check the command's manual by using <code>man $COMMAND</code> on the command line.<br />
<br />
====srun====<br />
srun runs a parallel job on a cluster managed by Slurm. If necessary, it will first create a resource allocation in which to run the parallel job.<br />
<br />
====salloc====<br />
salloc allocates a Slurm job allocation, which is a set of resources (nodes), possibly with some set of constraints (e.g. number of processors per node). When salloc successfully obtains the requested allocation, it then runs the command specified by the user. Finally, when the user specified command is complete, salloc relinquishes the job allocation. If no command is specified, salloc runs the user's default shell.<br />
<br />
====sbatch====<br />
sbatch submits a batch script to Slurm. The batch script may be given to sbatch through a file name on the command line, or if no file name is specified, sbatch will read in a script from standard input. The batch script may contain options preceded with "#SBATCH" before any executable commands in the script.<br />
<br />
====squeue====<br />
squeue views job and job step information for jobs managed by Slurm.<br />
<br />
====scancel====<br />
scancel signals or cancels jobs, job arrays, or job steps. An arbitrary number of jobs or job steps may be signaled using job specification filters or a space separated list of specific job and/or job step IDs.<br />
<br />
====sacct====<br />
sacct displays job accounting data stored in the job accounting log file or Slurm database in a variety of forms for your analysis. The sacct command displays information on jobs, job steps, status, and exitcodes by default. You can tailor the output with the use of the --format= option to specify the fields to be shown.<br />
<br />
====sstat====<br />
sstat displays job status information for your analysis. The sstat command displays information pertaining to CPU, Task, Node, Resident Set Size (RSS) and Virtual Memory (VM). You can tailor the output with the use of the --fields= option to specify the fields to be shown.<br />
<br />
==Modules==<br />
If you are trying to use [[Modules | GNU Modules]] in a Slurm job, please read the section of our [[Modules]] documentation on [[Modules#Modules_in_Non-Interactive_Shell_Sessions | non-interactive shell sessions]].<br />
<br />
==Running Jupyter Notebook on a Compute Node==<br />
In order to run Jupyter Notebook on a compute node, you first need to set up a python virtual environment.<br />
<br />
<h6>Setting up Python Virtual Environment</h6><br />
In order to set up your python virtual environment, you'll first want to follow the steps listed [https://wiki.umiacs.umd.edu/umiacs/index.php/PythonVirtualEnv here] to create a Python virtual environment on the compute node you are assigned. Then, activate it using the steps listed [https://wiki.umiacs.umd.edu/umiacs/index.php/PythonVirtualEnv#Activating_the_VirtualEnv here]. Next, install Jupyter using pip by following the steps [https://jupyter.readthedocs.io/en/latest/install/notebook-classic.html#alternative-for-experienced-python-users-installing-jupyter-with-pip here].<br />
<br />
<h6> Running Jupyter Notebook </h6><br />
After you've set up the python virtual environment, run the following commands on the compute node you are assigned:<br />
<pre><br />
jupyter notebook --no-browser --port=8889 --ip=0.0.0.0<br />
</pre><br />
This will start running the notebook on port 8889. <b>Note:</b> You must keep this shell window open to be able to connect.<br />
Then, on your local machine, run <br />
<pre><br />
ssh -N -f -L localhost:8888:$(NODENAME):8889 $(USERNAME)@$(CLUSTERNAME)sub00.umiacs.umd.edu<br />
</pre> <br />
This will tunnel port 8889 from the compute node to port 8888 on your local machine, using the (CLUSTERNAME)sub00 node as an intermediate node. Make sure to replace $(NODENAME) with the name of the compute node you are assigned, $(USERNAME) with your username, and $(CLUSTERNAME) with the name of the compute cluster you are using. For example, esloate@clipsub00.umiacs.umd.edu. Also, if the ports mentioned above are not working, then you can replace them with whatever port you'd like, just make sure to change it in the command you ran on the compute node. You can then open a web browser and type in <code>localhost:8888</code> to access the notebook. <b>Note:</b> You must be on a machine connected to the UMIACS network or connected to our [[Network/VPN | VPN]] in order to access the Jupyter notebook.<br />
<br />
<br />
=Quick Guide to translate PBS/Torque to SLURM=<br />
<br />
{| class="wikitable"<br />
|+User commands<br />
|-<br />
!<br />
!PBS/Torque<br />
!SLURM<br />
|-<br />
!Job submission<br />
|qsub [filename]<br />
|sbatch [filename]<br />
|-<br />
!Job deletion<br />
|qdel [job_id]<br />
|scancel [job_id]<br />
|-<br />
!Job status (by job)<br />
|qstat [job_id] <br />
|squeue --job [job_id]<br />
|-<br />
!Full job status (by job)<br />
|qstat -f [job_id]<br />
|scontrol show job [job_id]<br />
|-<br />
!Job status (by user)<br />
|qstat -u [username]<br />
|squeue --user=[username]<br />
|}<br />
<br />
{| class="wikitable"<br />
|+Environment variables<br />
|-<br />
!<br />
!PBS/Torque <br />
!SLURM<br />
|-<br />
!Job ID<br />
|$PBS_JOBID<br />
|$SLURM_JOBID<br />
|-<br />
!Submit Directory<br />
|$PBS_O_WORKDIR<br />
|$SLURM_SUBMIT_DIR<br />
|-<br />
!Node List <br />
|$PBS_NODEFILE<br />
|$SLURM_JOB_NODELIST<br />
|}<br />
<br />
{| class="wikitable"<br />
|+Job specification<br />
|-<br />
!<br />
!PBS/Torque <br />
!SLURM<br />
|-<br />
!Script directive<br />
|#PBS<br />
|#SBATCH<br />
|-<br />
!Job Name <br />
| -N [name]<br />
| --job-name=[name] OR -J [name]<br />
|-<br />
!Node Count<br />
| -l nodes=[count]<br />
| --nodes=[min[-max]] OR -N [min[-max]]<br />
|-<br />
!CPU Count<br />
| -l ppn=[count]<br />
| --ntasks-per-node=[count]<br />
|-<br />
!CPUs Per Task<br />
|<br />
| --cpus-per-task=[count]<br />
|-<br />
!Memory Size<br />
| -l mem=[MB] <br />
| --mem=[MB] OR --mem-per-cpu=[MB]<br />
|-<br />
!Wall Clock Limit<br />
| -l walltime=[hh:mm:ss]<br />
| --time=[min] OR --time=[days-hh:mm:ss]<br />
|-<br />
!Node Properties<br />
| -l nodes=4:ppn=8:[property]<br />
| --constraint=[list]<br />
|-<br />
!Standard Output File<br />
| -o [file_name]<br />
| --output=[file_name] OR -o [file_name]<br />
|-<br />
!Standard Error File<br />
| -e [file_name]<br />
| --error=[file_name] OR -e [file_name]<br />
|-<br />
!Combine stdout/stderr<br />
| -j oe (both to stdout)<br />
|(Default if you don't specify --error)<br />
|-<br />
!Job Arrays<br />
| -t [array_spec]<br />
| --array=[array_spec] OR -a [array_spec]<br />
|-<br />
!Delay Job Start<br />
| -a [time]<br />
| --begin=[time]<br />
|}</div>Wrichmanhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=CrowdStrike&diff=9505CrowdStrike2020-12-02T16:53:50Z<p>Wrichman: Updated antivirus tools and included information about online vs offline scans</p>
<hr />
<div>== Free malware/virus removal tools ==<br />
For non-UMIACS supported systems, there are several virus and malware protection and removal tools available. This page lists and describes some of them. <br />
<br><b>Note:</b> these are just a few of the many available anti-virus removal tools. One can always search the internet for a well-reputed anti-virus program and use that instead.<br />
<br />
== Online vs Offline Scanners ==<br />
There are two types of malware/virus removal tools, online and offline. The main difference between the two is that offline scans work outside of your computer's operating system. This can provide an alternate means for detecting and mitigating threats that may use various tactics to hide from your installed antivirus. On the other hand, online scanners can detect most problems while also being easier to use. Most online scanners have better interfaces than their offline counterparts, and they are usually easier to set up and run. Thus, the best way to remove malware or a virus would be to first try an online scanner and see if the issue still persists. If the online scanner did not fix the problem, then you should try an offline scanner. Below are some links to various online and offline scanners.<br />
<br />
<h3>Online Scanners</h3><br />
<ul><br />
*<li> [http://www.f-secure.com/en/web/home_global/online-scanner F-Secure Online Scan]</li><br />
The online scanner helps to get rid of viruses and spyware that may cause problems on your PC.<br />
*<li> [https://www.malwarebytes.org/mwb-download/ Malwarebytes]</li><br />
This free version is limited, but can also perform malware and virus scans.<br />
*<li> [http://www.superantispyware.com/superantispyware.html SUPERAntiSpyware]</li><br />
This free version is also limited but performs multiple different malware scans such as installed or internet spyware/adware.<br />
*<li> [http://www.kaspersky.com/antivirus-removal-tool?form=1 Kaspersky virus removal tool]</li><br />
This provides a virus scan with updated virus definitions.<br />
</ul><br />
<br />
<h3>Offline/Bootable Scanners</h3><br />
<ul><br />
* <li>[http://support.kaspersky.com/viruses/rescuedisk#downloads Kaspersky Rescue Disk] </li><br />
This is an offline scan that works with all operating systems.<br />
*<li>[https://support.microsoft.com/en-us/windows/help-protect-my-pc-with-microsoft-defender-offline-9306d528-64bf-4668-5b80-ff533f183d6c Microsoft Defender Offline]</li><br />
This offline scan only works with machines using Windows 7, 8.1, or 10.<br />
</ul><br />
<br />
==UMIACS-Supported Machines==<br />
All UMIACS-supported machines have F-Secure Client Security installed. Follow the steps below to run a manual scan using F-Secure on a UMIACS-supported machine.<br />
<h3> How to a run manual F-Secure Scan </h3><br />
<ol><br />
<li> Open F-Secure Client Security by searching it in the search bar.<br />
<br>[[Image:FSecureWindowsSearch.png|500px|]]</li><br />
<li> This should make a a pop up screen. If it doesn't, try clicking the up arrow in the bottom right and selecting the F-Secure icon. <br> [[Image:FSecureMenu.png|500px|]]</li><br />
<li> Click on the Scan option on the right side of the window. This should make a pop up with a list of options.<br />
<br> [[Image:FSecureIconMenu.png|500px|]]</li><br />
<li> Click either virus and spyware scan or full computer scan <br />
<ul><li>Virus and Spyware Scan: Searches common places where malware can be found. This makes it faster, but it may miss some hidden malware.</li><br />
<li>Full Computer Scan: Scans all internal/external hard drives for malware. This makes it more thorough than the malware scan, but it can take a long time to complete.</li></ul></li><br />
<li> After choosing an option, another screen should pop up that shows the progress of the scan. <br />
<br> [[Image:FSecureScanInProgress.png|500px|]]</li><br />
<li> Once the scan is complete, it will provide a report stating whether any malware was found. If if did find malware, then it will show you the number of files it removed. <br />
<br> [[Image:FSecureScanComplete.png|500px|]]</li><br />
<li> Hit the finish button to close the scan window and complete the scan. </li><br />
</ol></div>Wrichmanhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=CrowdStrike&diff=9504CrowdStrike2020-12-02T16:05:03Z<p>Wrichman: </p>
<hr />
<div>== Free malware/virus removal tools ==<br />
For non-UMIACS supported systems, there are several virus and malware protection and removal tools available. This page lists and describes some of them.<br />
<ol><br />
<li> F-Secure<br />
* [http://www.f-secure.com/en/web/labs_global/removal-tools/-/carousel/view/142 Bootable Scan]<br />
If your computer no longer starts due to malware corrupting the operating system, or you suspect the security software has been compromised, this bootable cd can securely boot up the computer and check the programs installed. The Rescue CD can also be used for more advanced repair and data recovery operations.<br />
* [http://www.f-secure.com/en/web/home_global/online-scanner Online Scan]</li><br />
Similar to the bootable scan, the online scanner helps to get rid of viruses and spyware that may cause problems on your PC.<br />
<li> [https://www.malwarebytes.org/mwb-download/ Malwarebytes]</li><br />
This free version is limited, but can also perform malware and virus scans.<br />
<li> [http://www.superantispyware.com/superantispyware.html SUPERAntiSpyware]</li><br />
This free version is also limited but performs multiple different malware scans such installed or internet spyware/adware.<br />
<li> [http://www.kaspersky.com/antivirus-removal-tool?form=1 Kaspersky virus removal tool]</li><br />
This provides a virus scan with updated virus definitions.<br />
</ol><br />
<br />
== Other "offline" (bootable) Scanners ==<br />
Offline/bootable scanners work without loading your operating system, and can provide an alternate means for detecting and mitigating threats that may use various tactics to hide from your favorite installed AV suite.<br />
* [http://support.kaspersky.com/viruses/rescuedisk#downloads Kaspersky Rescue Disk]<br />
* [http://www.bitdefender.com/support/how-to-create-a-bitdefender-rescue-cd-627.html BitDefender Rescue CD]<br />
* [https://www.f-secure.com/en/web/labs_global/rescue-cd F-Secure Rescue CD]<br />
<br />
== How to a run manual F-Secure Scan ==<br />
<ol><br />
<li> Open F-Secure Client Security by searching it in the windows search bar. Note: only UMIACS-supported machines will have this version of F-Secure Client Security.<br />
<br>[[Image:FSecureWindowsSearch.png|500px|]]</li><br />
<li> This should make a a pop up screen. If it doesn't, try clicking the up arrow in the bottom right and selecting the F-Secure icon. <br> [[Image:FSecureMenu.png|500px|]]</li><br />
<li> Click on the Scan option on the right side of the window. This should make a pop up with a list of options.<br />
<br> [[Image:FSecureIconMenu.png|500px|]]</li><br />
<li> Click either virus and spyware scan or full computer scan <br />
<ul><li>Virus and Spyware Scan: Searches common places where malware can be found. This makes it faster, but it may miss some hidden malware.</li><br />
<li>Full Computer Scan: Scans all internal/external hard drives for malware. This makes it more thorough than the malware scan, but it can take a long time to complete.</li></ul></li><br />
<li> After choosing an option, another screen should pop up that shows the progress of the scan. <br />
<br> [[Image:FSecureScanInProgress.png|500px|]]</li><br />
<li> Once the scan is complete, it will provide a report stating whether any malware was found. If if did find malware, then it will show you the number of files it removed. <br />
<br> [[Image:FSecureScanComplete.png|500px|]]</li><br />
<li> Hit the finish button to close the scan window and complete the scan. </li><br />
</ol></div>Wrichmanhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=Snapshots&diff=9502Snapshots2020-11-25T18:52:17Z<p>Wrichman: Adjusted Isilon filer example</p>
<hr />
<div>Snapshots are a implementation of [http://en.wikipedia.org/wiki/Copy-on-write copy-on-write] that allows for a file system to quickly take a point-in-time copy of the file system and provide access to the data through a .snapshot directory. Snapshots provide a fast, user-accessible way to recover data that has been accidentally deleted or corrupted within a recent time window -- rather than having to retrieve the data from comparatively slow tape backups. They also help to span the time gap between full backups.<br />
<br />
We provide [[Snapshots]] on our ZFS, [[Snapshots:FluidFS | FluidFS]], and Isilon filers to certain file systems. If you are ever unsure if a particular volume has Snapshots enabled, please contact the [[HelpDesk | Help Desk]].<br />
<br />
==Snapshot Retention Policy==<br />
Our core file systems in the department are on a 4 hour snapshot cycle. <br />
<br />
{| class="wikitable"<br />
!Snapshot Name<br />
!Retention Length<br />
!When is it taken?<br />
|-<br />
|'''Hourly'''<br />
|24-32 hours<br />
|Every day 12am, 4am, 8am, 12pm, 4pm<br />
|-<br />
|'''Daily'''<br />
|2 days<br />
|Every day 8pm or 12am<br />
|-<br />
|'''Weekly'''<br />
|1 week<br />
|Every Saturday 8pm or Sunday 12am<br />
|}<br />
<br />
In other words, we retain up to either 6 or 8 hourly snapshots, 2 daily snapshots and 1 weekly snapshot. Hourly snapshots may be superseded by daily snapshots, and daily snapshots may be superseded by the weekly snapshot.<br />
<br />
==Snapshot Restoring==<br />
<br />
If you have deleted a file by mistake and you need to get it back, you can use the snapshots directory to recopy the file.<br />
<br />
This directory can typically be found in your home directory. It generally will not be visible, even when viewing hidden directories.<br />
<br />
'''It will be either''':<br />
<br />
* .snapshots for the [[Snapshots:FluidFS | FluidFS]] filer<br />
* .zfs/snapshot for the ZFS filer<br />
* .snapshot for the Isilon filer<br />
<br />
The inside of one of these will look something like this on a FluidFS filesystem:<br />
<pre><br />
sattwood@zaphod:~$ pwd<br />
/nfshomes/sattwood<br />
sattwood@zaphod:~$ cd .snapshots<br />
sattwood@zaphod:~/.snapshots$ ls<br />
daily_2018_06_14__20_00 hourly_2018_06_14__12_00 hourly_2018_06_15__04_00 weekly_2018_06_09__20_00<br />
daily_2018_06_15__20_00 hourly_2018_06_14__16_00 hourly_2018_06_15__08_00 <br />
hourly_2018_06_14__08_00 hourly_2018_06_14__00_00 hourly_2018_06_15__12_00 <br />
</pre><br />
Or this, on a ZFS filesystem:<br />
<pre><br />
sattwood@swirl:~$ pwd<br />
/nmhomes/sattwood<br />
sattwood@swirl:~$ cd .zfs/snapshot<br />
sattwood@swirl:~/.zfs/snapshot$ ls<br />
zfs-auto-snap_daily-2018-06-13-01h00 zfs-auto-snap_hourly-2018-05-28-00h00<br />
zfs-auto-snap_daily-2018-06-14-01h00 zfs-auto-snap_hourly-2018-05-29-00h00<br />
zfs-auto-snap_daily-2018-06-15-01h00 zfs-auto-snap_hourly-2018-06-03-16h00<br />
zfs-auto-snap_hourly-2018-05-24-00h00 zfs-auto-snap_hourly-2018-06-10-08h00<br />
zfs-auto-snap_hourly-2018-05-25-00h00 zfs-auto-snap_hourly-2018-06-15-12h00<br />
zfs-auto-snap_hourly-2018-05-26-00h00 zfs-auto-snap_weekly-2018-06-09-03h00<br />
</pre><br />
Or this, on an Isilon filesystem:<br />
<pre><br />
sattwood@coffee:~$ pwd<br />
/nfshomes/sattwood<br />
sattwood@coffee:~$ cd .snapshot<br />
sattwood@coffee:~/.snapshot$ ls<br />
nfshomes_2018-06-14_00:00 nfshomes_2018-06-15_04:00<br />
nfshomes_2018-06-14_16:00 nfshomes_2018-06-15_08:00<br />
nfshomes_2018-06-14_20:00 nfshomes_2018-06-15_12:00<br />
nfshomes_2018-06-15_00:00 Weekly_nfshomes_2018-06-10_00:00<br />
</pre><br />
For an example of file restoration, please see [[Snapshots:Example | this page]].<br />
<br />
<br />
[[Category:Snapshots]]<br />
__NOTOC__</div>Wrichmanhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=Snapshots&diff=9501Snapshots2020-11-25T18:48:17Z<p>Wrichman: Fixed Isilon filer details</p>
<hr />
<div>Snapshots are a implementation of [http://en.wikipedia.org/wiki/Copy-on-write copy-on-write] that allows for a file system to quickly take a point-in-time copy of the file system and provide access to the data through a .snapshot directory. Snapshots provide a fast, user-accessible way to recover data that has been accidentally deleted or corrupted within a recent time window -- rather than having to retrieve the data from comparatively slow tape backups. They also help to span the time gap between full backups.<br />
<br />
We provide [[Snapshots]] on our ZFS, [[Snapshots:FluidFS | FluidFS]], and Isilon filers to certain file systems. If you are ever unsure if a particular volume has Snapshots enabled, please contact the [[HelpDesk | Help Desk]].<br />
<br />
==Snapshot Retention Policy==<br />
Our core file systems in the department are on a 4 hour snapshot cycle. <br />
<br />
{| class="wikitable"<br />
!Snapshot Name<br />
!Retention Length<br />
!When is it taken?<br />
|-<br />
|'''Hourly'''<br />
|24-32 hours<br />
|Every day 12am, 4am, 8am, 12pm, 4pm<br />
|-<br />
|'''Daily'''<br />
|2 days<br />
|Every day 8pm or 12am<br />
|-<br />
|'''Weekly'''<br />
|1 week<br />
|Every Saturday 8pm or Sunday 12am<br />
|}<br />
<br />
In other words, we retain up to either 6 or 8 hourly snapshots, 2 daily snapshots and 1 weekly snapshot. Hourly snapshots may be superseded by daily snapshots, and daily snapshots may be superseded by the weekly snapshot.<br />
<br />
==Snapshot Restoring==<br />
<br />
If you have deleted a file by mistake and you need to get it back, you can use the snapshots directory to recopy the file.<br />
<br />
This directory can typically be found in your home directory. It generally will not be visible, even when viewing hidden directories.<br />
<br />
'''It will be either''':<br />
<br />
* .snapshots for the [[Snapshots:FluidFS | FluidFS]] filer<br />
* .zfs/snapshot for the ZFS filer<br />
* .snapshot for the Isilon filer<br />
<br />
The inside of one of these will look something like this on a FluidFS filesystem:<br />
<pre><br />
sattwood@zaphod:~$ pwd<br />
/nfshomes/sattwood<br />
sattwood@zaphod:~$ cd .snapshots<br />
sattwood@zaphod:~/.snapshots$ ls<br />
daily_2018_06_14__20_00 hourly_2018_06_14__12_00 hourly_2018_06_15__04_00 weekly_2018_06_09__20_00<br />
daily_2018_06_15__20_00 hourly_2018_06_14__16_00 hourly_2018_06_15__08_00 <br />
hourly_2018_06_14__08_00 hourly_2018_06_14__00_00 hourly_2018_06_15__12_00 <br />
</pre><br />
Or this, on a ZFS filesystem:<br />
<pre><br />
sattwood@swirl:~$ pwd<br />
/nmhomes/sattwood<br />
sattwood@swirl:~$ cd .zfs/snapshot<br />
sattwood@swirl:~/.zfs/snapshot$ ls<br />
zfs-auto-snap_daily-2018-06-13-01h00 zfs-auto-snap_hourly-2018-05-28-00h00<br />
zfs-auto-snap_daily-2018-06-14-01h00 zfs-auto-snap_hourly-2018-05-29-00h00<br />
zfs-auto-snap_daily-2018-06-15-01h00 zfs-auto-snap_hourly-2018-06-03-16h00<br />
zfs-auto-snap_hourly-2018-05-24-00h00 zfs-auto-snap_hourly-2018-06-10-08h00<br />
zfs-auto-snap_hourly-2018-05-25-00h00 zfs-auto-snap_hourly-2018-06-15-12h00<br />
zfs-auto-snap_hourly-2018-05-26-00h00 zfs-auto-snap_weekly-2018-06-09-03h00<br />
</pre><br />
Or this, on an Isilon filesystem:<br />
<pre><br />
sattwood@coffee:~$ pwd<br />
/nfshomes/sattwood<br />
sattwood@coffee:~$ cd .snapshot<br />
sattwood@coffee:~/.snapshot$ ls<br />
nfshomes_2018-06-14_00:00 nfshomes_2018-06-15_04:00<br />
nfshomes_2018-06-14_16:00 nfshomes_2018-06-15_08:00<br />
nfshomes_2018-06-14_20:00 nfshomes_2018-06-15_12:00<br />
</pre><br />
For an example of file restoration, please see [[Snapshots:Example | this page]].<br />
<br />
<br />
[[Category:Snapshots]]<br />
__NOTOC__</div>Wrichmanhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=CrowdStrike&diff=9500CrowdStrike2020-11-25T17:30:51Z<p>Wrichman: Updated screenshots for instructions for a manual F-secure scan</p>
<hr />
<div>== Free malware/virus removal tools ==<br />
For non-UMIACS supported systems, there are several virus and malware protection and removal tools available. This page lists and describes some of them.<br />
<ol><br />
<li> F-Secure<br />
* [http://www.f-secure.com/en/web/labs_global/removal-tools/-/carousel/view/142 Bootable Scan]<br />
If your computer no longer starts due to malware corrupting the operating system, or you suspect the security software has been compromised, this bootable cd can securely boot up the computer and check the programs installed. The Rescue CD can also be used for more advanced repair and data recovery operations.<br />
* [http://www.f-secure.com/en/web/home_global/online-scanner Online Scan]</li><br />
Similar to the bootable scan, the online scanner helps to get rid of viruses and spyware that may cause problems on your PC.<br />
<li> [https://www.malwarebytes.org/mwb-download/ Malwarebytes]</li><br />
This free version is limited, but can also perform malware and virus scans.<br />
<li> [http://www.superantispyware.com/superantispyware.html SUPERAntiSpyware]</li><br />
This free version is also limited but performs multiple different malware scans such installed or internet spyware/adware.<br />
<li> [http://www.kaspersky.com/antivirus-removal-tool?form=1 Kaspersky virus removal tool]</li><br />
This provides a virus scan with updated virus definitions.<br />
</ol><br />
<br />
== Other "offline" (bootable) Scanners ==<br />
Offline/bootable scanners work without loading your operating system, and can provide an alternate means for detecting and mitigating threats that may use various tactics to hide from your favorite installed AV suite.<br />
* [http://support.kaspersky.com/viruses/rescuedisk#downloads Kaspersky Rescue Disk]<br />
* [http://www.bitdefender.com/support/how-to-create-a-bitdefender-rescue-cd-627.html BitDefender Rescue CD]<br />
* [https://www.f-secure.com/en/web/labs_global/rescue-cd F-Secure Rescue CD]<br />
<br />
== How to a run manual F-Secure Scan ==<br />
<ol><br />
<li> Open F-Secure Server Security by searching it in the windows search bar. <br />
<br>[[Image:FSecureWindowsSearch.png|500px|]]</li><br />
<li> This should make a a pop up screen. If it doesn't, try clicking the up arrow in the bottom right and selecting the F-Secure icon. <br> [[Image:FSecureMenu.png|500px|]]</li><br />
<li> Click on the Scan option on the right side of the window. This should make a pop up with a list of options.<br />
<br> [[Image:FSecureIconMenu.png|500px|]]</li><br />
<li> Click either virus and spyware scan or full computer scan <br />
<ul><li>Virus and Spyware Scan: Searches common places where malware can be found. This makes it faster, but it may miss some hidden malware.</li><br />
<li>Full Computer Scan: Scans all internal/external hard drives for malware. This makes it more thorough than the malware scan, but it can take a long time to complete.</li></ul></li><br />
<li> After choosing an option, another screen should pop up that shows the progress of the scan. <br />
<br> [[Image:FSecureScanInProgress.png|500px|]]</li><br />
<li> Once the scan is complete, it will provide a report stating whether any malware was found. If if did find malware, then it will show you the number of files it removed. <br />
<br> [[Image:FSecureScanComplete.png|500px|]]</li><br />
<li> Hit the finish button to close the scan window and complete the scan. </li><br />
</ol></div>Wrichmanhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=CrowdStrike&diff=9494CrowdStrike2020-11-25T16:58:44Z<p>Wrichman: Added instructions on how to complete a manual scan using F-Secure</p>
<hr />
<div>== Free malware/virus removal tools ==<br />
For non-UMIACS supported systems, there are several virus and malware protection and removal tools available. This page lists and describes some of them.<br />
<ol><br />
<li> F-Secure<br />
* [http://www.f-secure.com/en/web/labs_global/removal-tools/-/carousel/view/142 Bootable Scan]<br />
If your computer no longer starts due to malware corrupting the operating system, or you suspect the security software has been compromised, this bootable cd can securely boot up the computer and check the programs installed. The Rescue CD can also be used for more advanced repair and data recovery operations.<br />
* [http://www.f-secure.com/en/web/home_global/online-scanner Online Scan]</li><br />
Similar to the bootable scan, the online scanner helps to get rid of viruses and spyware that may cause problems on your PC.<br />
<li> [https://www.malwarebytes.org/mwb-download/ Malwarebytes]</li><br />
This free version is limited, but can also perform malware and virus scans.<br />
<li> [http://www.superantispyware.com/superantispyware.html SUPERAntiSpyware]</li><br />
This free version is also limited but performs multiple different malware scans such installed or internet spyware/adware.<br />
<li> [http://www.kaspersky.com/antivirus-removal-tool?form=1 Kaspersky virus removal tool]</li><br />
This provides a virus scan with updated virus definitions.<br />
</ol><br />
<br />
== Other "offline" (bootable) Scanners ==<br />
Offline/bootable scanners work without loading your operating system, and can provide an alternate means for detecting and mitigating threats that may use various tactics to hide from your favorite installed AV suite.<br />
* [http://support.kaspersky.com/viruses/rescuedisk#downloads Kaspersky Rescue Disk]<br />
* [http://www.bitdefender.com/support/how-to-create-a-bitdefender-rescue-cd-627.html BitDefender Rescue CD]<br />
* [https://www.f-secure.com/en/web/labs_global/rescue-cd F-Secure Rescue CD]<br />
<br />
== How to a run manual F-Secure Scan ==<br />
<ol><br />
<li> Open F-Secure Server Security by searching it in the windows search bar. <br />
<br>[[Image:FSecureWindowsSearch.png|500px|]]</li><br />
<li> This should make a a pop up screen. If it doesn't, try clicking the up arrow in the bottom left and selecting the F-Secure icon. <br> [[Image:FSecureMenu.png|500px|]]</li><br />
<li> Click on the icon in the bottom left (the magnifying glass with a bug in the middle). This should make a pop up with a list of options.<br />
<br> [[Image:FSecureScanMenu.png|500px|]]</li><br />
<li> Click either malware scan or full computer scan <br />
<ul><li>Malware Scan: Searches common places where malware can be found. This makes it faster, but it may miss some hidden malware.</li><br />
<li>Full Computer Scan: Scans all internal/external hard drives for malware. This makes it more thorough than the malware scan, but it can take a long time to complete.</li></ul></li><br />
<li> After choosing an option, another screen should pop up that shows the progress of the scan. <br />
<br> [[Image:FSecureScanInProgress.png|500px|]]</li><br />
<li> Once the scan is complete, it will either show a green check (as shown below) to indicate that no malware was found or it will show you a list of harmful items. <br />
<br> [[Image:FSecureScanComplete.png|500px|]]</li><br />
<li> If harmful items were found, then select the handle all option to start the cleaning process. </li><br />
<li> Once it is done cleaning the files, it will show you a report stating the final results and the number of harmful items that were cleaned. </li><br />
</ol></div>Wrichmanhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=Snapshots&diff=9450Snapshots2020-11-16T19:29:59Z<p>Wrichman: Changed Isilon example to try and better represent what the user would see</p>
<hr />
<div>Snapshots are a implementation of [http://en.wikipedia.org/wiki/Copy-on-write copy-on-write] that allows for a file system to quickly take a point-in-time copy of the file system and provide access to the data through a .snapshot directory. Snapshots provide a fast, user-accessible way to recover data that has been accidentally deleted or corrupted within a recent time window -- rather than having to retrieve the data from comparatively slow tape backups. They also help to span the time gap between full backups.<br />
<br />
We provide [[Snapshots]] on our ZFS, [[Snapshots:FluidFS | FluidFS]], and Isilon filers to certain file systems. If you are ever unsure if a particular volume has Snapshots enabled, please contact the [[HelpDesk | Help Desk]].<br />
<br />
==Snapshot Retention Policy==<br />
Our core file systems in the department are on a 4 hour snapshot cycle. <br />
<br />
{| class="wikitable"<br />
!Snapshot Name<br />
!Retention Length<br />
!When is it taken?<br />
|-<br />
|'''Hourly'''<br />
|24-32 hours<br />
|Every day 12am, 4am, 8am, 12pm, 4pm<br />
|-<br />
|'''Daily'''<br />
|2 days<br />
|Every day 8pm or 12am<br />
|-<br />
|'''Weekly'''<br />
|1 week<br />
|Every Saturday 8pm or Sunday 12am<br />
|}<br />
<br />
In other words, we retain up to either 6 or 8 hourly snapshots, 2 daily snapshots and 1 weekly snapshot. Hourly snapshots may be superseded by daily snapshots, and daily snapshots may be superseded by the weekly snapshot.<br />
<br />
==Snapshot Restoring==<br />
<br />
If you have deleted a file by mistake and you need to get it back, you can use the snapshots directory to recopy the file.<br />
<br />
This directory can typically be found in your home directory. It generally will not be visible, even when viewing hidden directories.<br />
<br />
'''It will be either''':<br />
<br />
* .snapshots for the [[Snapshots:FluidFS | FluidFS]] filer<br />
* .zfs/snapshot for the ZFS filer<br />
* ifs/.snapshot for the Isilon filer<br />
<br />
The inside of one of these will look something like this on a FluidFS filesystem:<br />
<pre><br />
sattwood@zaphod:~$ pwd<br />
/nfshomes/sattwood<br />
sattwood@zaphod:~$ cd .snapshots<br />
sattwood@zaphod:~/.snapshots$ ls<br />
daily_2018_06_14__20_00 hourly_2018_06_14__12_00 hourly_2018_06_15__04_00 weekly_2018_06_09__20_00<br />
daily_2018_06_15__20_00 hourly_2018_06_14__16_00 hourly_2018_06_15__08_00 <br />
hourly_2018_06_14__08_00 hourly_2018_06_14__00_00 hourly_2018_06_15__12_00 <br />
</pre><br />
Or this, on a ZFS filesystem:<br />
<pre><br />
sattwood@swirl:~$ pwd<br />
/nmhomes/sattwood<br />
sattwood@swirl:~$ cd .zfs/snapshot<br />
sattwood@swirl:~/.zfs/snapshot$ ls<br />
zfs-auto-snap_daily-2018-06-13-01h00 zfs-auto-snap_hourly-2018-05-28-00h00<br />
zfs-auto-snap_daily-2018-06-14-01h00 zfs-auto-snap_hourly-2018-05-29-00h00<br />
zfs-auto-snap_daily-2018-06-15-01h00 zfs-auto-snap_hourly-2018-06-03-16h00<br />
zfs-auto-snap_hourly-2018-05-24-00h00 zfs-auto-snap_hourly-2018-06-10-08h00<br />
zfs-auto-snap_hourly-2018-05-25-00h00 zfs-auto-snap_hourly-2018-06-15-12h00<br />
zfs-auto-snap_hourly-2018-05-26-00h00 zfs-auto-snap_weekly-2018-06-09-03h00<br />
</pre><br />
Or this, on an Isilon filesystem:<br />
<pre><br />
sattwood@vimur:~$ pwd<br />
/nfshomes/sattwood<br />
sattwood@vimur:~$ cd ifs/.snapshot<br />
sattwood@vimur:~/ifs/.snapshot$ ls<br />
Snapshot2018Jun04 Snapshot2018Jun05 Snapshot2018Jun06 Snapshot2018Jun07<br />
</pre><br />
For an example of file restoration, please see [[Snapshots:Example | this page]].<br />
<br />
<br />
[[Category:Snapshots]]<br />
__NOTOC__</div>Wrichmanhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=Snapshots:Example&diff=9447Snapshots:Example2020-11-09T19:36:49Z<p>Wrichman: </p>
<hr />
<div>Note that in this example, the directory ".snapshots" could also be ".zfs/snapshot" or "ifs/.snapshot" depending on the filer serving your host. You can try to 'ls' one and if it doesn't exist try one of the others.<br />
<br />
----<br />
<br />
Changing to my virtual environment directory.<br />
<pre><br />
sattwood@zaphod:~/virtualenv$ pwd<br />
/nfshomes/sattwood/virtualenv<br />
</pre><br />
I see that I have a python file called '''virtualenv.py'''.<br />
<pre><br />
sattwood@zaphod:~/virtualenv$ ls<br />
appveyor.yml bin docs MANIFEST.in scripts setup.py tox.ini virtualenv.py<br />
AUTHORS.txt CONTRIBUTING.rst LICENSE.txt README.rst setup.cfg tests virtualenv_embedded virtualenv_support<br />
</pre><br />
<pre><br />
sattwood@zaphod:~/virtualenv$ ls -lah virtualenv.py<br />
-rwxrwxr-x. 1 sattwood sattwood 98K Jun 12 13:54 virtualenv.py<br />
</pre><br />
I will remove it from the current file system.<br />
<pre><br />
sattwood@zaphod:~/virtualenv$ rm virtualenv.py<br />
</pre><br />
As you can see it no longer is there.<br />
<pre><br />
sattwood@zaphod:~/virtualenv$ ls<br />
appveyor.yml bin docs MANIFEST.in scripts setup.py tox.ini virtualenv_support<br />
AUTHORS.txt CONTRIBUTING.rst LICENSE.txt README.rst setup.cfg tests virtualenv_embedded<br />
</pre><br />
I am going to go into the most recent hourly snapshot, in this case: '''hourly_2018_06_15__12_00'''<br />
<pre><br />
sattwood@zaphod:~/virtualenv$ ls /nfshomes/sattwood/.snapshots<br />
daily_2018_06_13__00_00 hourly_2018_06_14__04_00 hourly_2018_06_14__16_00 hourly_2018_06_15__08_00<br />
daily_2018_06_14__00_00 hourly_2018_06_14__08_00 hourly_2018_06_14__20_00 hourly_2018_06_15__12_00<br />
daily_2018_06_15__00_00 hourly_2018_06_14__12_00 hourly_2018_06_15__04_00 weekly_2018_06_09__00_00<br />
</pre><br />
<pre><br />
sattwood@zaphod:~/virtualenv$ cd /nfshomes/sattwood/.snapshots/hourly_2018_06_15__12_00/virtualenv<br />
</pre><br />
As you can see the file is still here.<br />
<pre><br />
sattwood@zaphod:~/.snapshots/hourly_2018_06_15__12_00/virtualenv$ ls<br />
appveyor.yml bin docs MANIFEST.in scripts setup.py tox.ini virtualenv.py<br />
AUTHORS.txt CONTRIBUTING.rst LICENSE.txt README.rst setup.cfg tests virtualenv_embedded virtualenv_support<br />
</pre><br />
I copy it back to the original directory.<br />
<pre><br />
sattwood@zaphod:~/.snapshots/hourly_2018_06_15__12_00/virtualenv$ cp virtualenv.py /nfshomes/sattwood/virtualenv/<br />
</pre><br />
Change back to the original directory.<br />
<pre><br />
sattwood@zaphod:~/.snapshots/hourly_2018_06_15__12_00/virtualenv$ cd /nfshomes/sattwood/virtualenv/<br />
</pre><br />
And it is back.<br />
<pre><br />
sattwood@zaphod:~/virtualenv$ ls<br />
appveyor.yml bin docs MANIFEST.in scripts setup.py tox.ini virtualenv.py<br />
AUTHORS.txt CONTRIBUTING.rst LICENSE.txt README.rst setup.cfg tests virtualenv_embedded virtualenv_support<br />
</pre><br />
<br />
<br />
<br />
[[Category:Snapshots]]<br />
__NOTOC__</div>Wrichmanhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=Snapshots:Example&diff=9446Snapshots:Example2020-11-09T19:36:09Z<p>Wrichman: Fixed minor type</p>
<hr />
<div>Note that in this example, the directory ".snapshots" could also be ".zfs/snapshot" or "ifs/.snapshot" depending on the filer serving your host. You can try to 'ls' one and if it doesn't exist try the other.<br />
<br />
----<br />
<br />
Changing to my virtual environment directory.<br />
<pre><br />
sattwood@zaphod:~/virtualenv$ pwd<br />
/nfshomes/sattwood/virtualenv<br />
</pre><br />
I see that I have a python file called '''virtualenv.py'''.<br />
<pre><br />
sattwood@zaphod:~/virtualenv$ ls<br />
appveyor.yml bin docs MANIFEST.in scripts setup.py tox.ini virtualenv.py<br />
AUTHORS.txt CONTRIBUTING.rst LICENSE.txt README.rst setup.cfg tests virtualenv_embedded virtualenv_support<br />
</pre><br />
<pre><br />
sattwood@zaphod:~/virtualenv$ ls -lah virtualenv.py<br />
-rwxrwxr-x. 1 sattwood sattwood 98K Jun 12 13:54 virtualenv.py<br />
</pre><br />
I will remove it from the current file system.<br />
<pre><br />
sattwood@zaphod:~/virtualenv$ rm virtualenv.py<br />
</pre><br />
As you can see it no longer is there.<br />
<pre><br />
sattwood@zaphod:~/virtualenv$ ls<br />
appveyor.yml bin docs MANIFEST.in scripts setup.py tox.ini virtualenv_support<br />
AUTHORS.txt CONTRIBUTING.rst LICENSE.txt README.rst setup.cfg tests virtualenv_embedded<br />
</pre><br />
I am going to go into the most recent hourly snapshot, in this case: '''hourly_2018_06_15__12_00'''<br />
<pre><br />
sattwood@zaphod:~/virtualenv$ ls /nfshomes/sattwood/.snapshots<br />
daily_2018_06_13__00_00 hourly_2018_06_14__04_00 hourly_2018_06_14__16_00 hourly_2018_06_15__08_00<br />
daily_2018_06_14__00_00 hourly_2018_06_14__08_00 hourly_2018_06_14__20_00 hourly_2018_06_15__12_00<br />
daily_2018_06_15__00_00 hourly_2018_06_14__12_00 hourly_2018_06_15__04_00 weekly_2018_06_09__00_00<br />
</pre><br />
<pre><br />
sattwood@zaphod:~/virtualenv$ cd /nfshomes/sattwood/.snapshots/hourly_2018_06_15__12_00/virtualenv<br />
</pre><br />
As you can see the file is still here.<br />
<pre><br />
sattwood@zaphod:~/.snapshots/hourly_2018_06_15__12_00/virtualenv$ ls<br />
appveyor.yml bin docs MANIFEST.in scripts setup.py tox.ini virtualenv.py<br />
AUTHORS.txt CONTRIBUTING.rst LICENSE.txt README.rst setup.cfg tests virtualenv_embedded virtualenv_support<br />
</pre><br />
I copy it back to the original directory.<br />
<pre><br />
sattwood@zaphod:~/.snapshots/hourly_2018_06_15__12_00/virtualenv$ cp virtualenv.py /nfshomes/sattwood/virtualenv/<br />
</pre><br />
Change back to the original directory.<br />
<pre><br />
sattwood@zaphod:~/.snapshots/hourly_2018_06_15__12_00/virtualenv$ cd /nfshomes/sattwood/virtualenv/<br />
</pre><br />
And it is back.<br />
<pre><br />
sattwood@zaphod:~/virtualenv$ ls<br />
appveyor.yml bin docs MANIFEST.in scripts setup.py tox.ini virtualenv.py<br />
AUTHORS.txt CONTRIBUTING.rst LICENSE.txt README.rst setup.cfg tests virtualenv_embedded virtualenv_support<br />
</pre><br />
<br />
<br />
<br />
[[Category:Snapshots]]<br />
__NOTOC__</div>Wrichmanhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=Snapshots:Example&diff=9445Snapshots:Example2020-11-09T19:35:50Z<p>Wrichman: Added details on Isilon filer</p>
<hr />
<div>Note that in this example, the directory ".snapshots" could also be ".zfs/snapshot" or "ifs/.snapshot/" depending on the filer serving your host. You can try to 'ls' one and if it doesn't exist try the other.<br />
<br />
----<br />
<br />
Changing to my virtual environment directory.<br />
<pre><br />
sattwood@zaphod:~/virtualenv$ pwd<br />
/nfshomes/sattwood/virtualenv<br />
</pre><br />
I see that I have a python file called '''virtualenv.py'''.<br />
<pre><br />
sattwood@zaphod:~/virtualenv$ ls<br />
appveyor.yml bin docs MANIFEST.in scripts setup.py tox.ini virtualenv.py<br />
AUTHORS.txt CONTRIBUTING.rst LICENSE.txt README.rst setup.cfg tests virtualenv_embedded virtualenv_support<br />
</pre><br />
<pre><br />
sattwood@zaphod:~/virtualenv$ ls -lah virtualenv.py<br />
-rwxrwxr-x. 1 sattwood sattwood 98K Jun 12 13:54 virtualenv.py<br />
</pre><br />
I will remove it from the current file system.<br />
<pre><br />
sattwood@zaphod:~/virtualenv$ rm virtualenv.py<br />
</pre><br />
As you can see it no longer is there.<br />
<pre><br />
sattwood@zaphod:~/virtualenv$ ls<br />
appveyor.yml bin docs MANIFEST.in scripts setup.py tox.ini virtualenv_support<br />
AUTHORS.txt CONTRIBUTING.rst LICENSE.txt README.rst setup.cfg tests virtualenv_embedded<br />
</pre><br />
I am going to go into the most recent hourly snapshot, in this case: '''hourly_2018_06_15__12_00'''<br />
<pre><br />
sattwood@zaphod:~/virtualenv$ ls /nfshomes/sattwood/.snapshots<br />
daily_2018_06_13__00_00 hourly_2018_06_14__04_00 hourly_2018_06_14__16_00 hourly_2018_06_15__08_00<br />
daily_2018_06_14__00_00 hourly_2018_06_14__08_00 hourly_2018_06_14__20_00 hourly_2018_06_15__12_00<br />
daily_2018_06_15__00_00 hourly_2018_06_14__12_00 hourly_2018_06_15__04_00 weekly_2018_06_09__00_00<br />
</pre><br />
<pre><br />
sattwood@zaphod:~/virtualenv$ cd /nfshomes/sattwood/.snapshots/hourly_2018_06_15__12_00/virtualenv<br />
</pre><br />
As you can see the file is still here.<br />
<pre><br />
sattwood@zaphod:~/.snapshots/hourly_2018_06_15__12_00/virtualenv$ ls<br />
appveyor.yml bin docs MANIFEST.in scripts setup.py tox.ini virtualenv.py<br />
AUTHORS.txt CONTRIBUTING.rst LICENSE.txt README.rst setup.cfg tests virtualenv_embedded virtualenv_support<br />
</pre><br />
I copy it back to the original directory.<br />
<pre><br />
sattwood@zaphod:~/.snapshots/hourly_2018_06_15__12_00/virtualenv$ cp virtualenv.py /nfshomes/sattwood/virtualenv/<br />
</pre><br />
Change back to the original directory.<br />
<pre><br />
sattwood@zaphod:~/.snapshots/hourly_2018_06_15__12_00/virtualenv$ cd /nfshomes/sattwood/virtualenv/<br />
</pre><br />
And it is back.<br />
<pre><br />
sattwood@zaphod:~/virtualenv$ ls<br />
appveyor.yml bin docs MANIFEST.in scripts setup.py tox.ini virtualenv.py<br />
AUTHORS.txt CONTRIBUTING.rst LICENSE.txt README.rst setup.cfg tests virtualenv_embedded virtualenv_support<br />
</pre><br />
<br />
<br />
<br />
[[Category:Snapshots]]<br />
__NOTOC__</div>Wrichmanhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=Snapshots&diff=9444Snapshots2020-11-09T19:34:17Z<p>Wrichman: Fixed minor typo</p>
<hr />
<div>Snapshots are a implementation of [http://en.wikipedia.org/wiki/Copy-on-write copy-on-write] that allows for a file system to quickly take a point-in-time copy of the file system and provide access to the data through a .snapshot directory. Snapshots provide a fast, user-accessible way to recover data that has been accidentally deleted or corrupted within a recent time window -- rather than having to retrieve the data from comparatively slow tape backups. They also help to span the time gap between full backups.<br />
<br />
We provide [[Snapshots]] on our ZFS, [[Snapshots:FluidFS | FluidFS]], and Isilon filers to certain file systems. If you are ever unsure if a particular volume has Snapshots enabled, please contact the [[HelpDesk | Help Desk]].<br />
<br />
==Snapshot Retention Policy==<br />
Our core file systems in the department are on a 4 hour snapshot cycle. <br />
<br />
{| class="wikitable"<br />
!Snapshot Name<br />
!Retention Length<br />
!When is it taken?<br />
|-<br />
|'''Hourly'''<br />
|24-32 hours<br />
|Every day 12am, 4am, 8am, 12pm, 4pm<br />
|-<br />
|'''Daily'''<br />
|2 days<br />
|Every day 8pm or 12am<br />
|-<br />
|'''Weekly'''<br />
|1 week<br />
|Every Saturday 8pm or Sunday 12am<br />
|}<br />
<br />
In other words, we retain up to either 6 or 8 hourly snapshots, 2 daily snapshots and 1 weekly snapshot. Hourly snapshots may be superseded by daily snapshots, and daily snapshots may be superseded by the weekly snapshot.<br />
<br />
==Snapshot Restoring==<br />
<br />
If you have deleted a file by mistake and you need to get it back, you can use the snapshots directory to recopy the file.<br />
<br />
This directory can typically be found in your home directory. It generally will not be visible, even when viewing hidden directories.<br />
<br />
'''It will be either''':<br />
<br />
* .snapshots for the [[Snapshots:FluidFS | FluidFS]] filer<br />
* .zfs/snapshot for the ZFS filer<br />
* ifs/.snapshot for the Isilon filer<br />
<br />
The inside of one of these will look something like this on a FluidFS filesystem:<br />
<pre><br />
sattwood@zaphod:~$ pwd<br />
/nfshomes/sattwood<br />
sattwood@zaphod:~$ cd .snapshots<br />
sattwood@zaphod:~/.snapshots$ ls<br />
daily_2018_06_14__20_00 hourly_2018_06_14__12_00 hourly_2018_06_15__04_00 weekly_2018_06_09__20_00<br />
daily_2018_06_15__20_00 hourly_2018_06_14__16_00 hourly_2018_06_15__08_00 <br />
hourly_2018_06_14__08_00 hourly_2018_06_14__00_00 hourly_2018_06_15__12_00 <br />
</pre><br />
Or this, on a ZFS filesystem:<br />
<pre><br />
sattwood@swirl:~$ pwd<br />
/nmhomes/sattwood<br />
sattwood@swirl:~$ cd .zfs/snapshot<br />
sattwood@swirl:~/.zfs/snapshot$ ls<br />
zfs-auto-snap_daily-2018-06-13-01h00 zfs-auto-snap_hourly-2018-05-28-00h00<br />
zfs-auto-snap_daily-2018-06-14-01h00 zfs-auto-snap_hourly-2018-05-29-00h00<br />
zfs-auto-snap_daily-2018-06-15-01h00 zfs-auto-snap_hourly-2018-06-03-16h00<br />
zfs-auto-snap_hourly-2018-05-24-00h00 zfs-auto-snap_hourly-2018-06-10-08h00<br />
zfs-auto-snap_hourly-2018-05-25-00h00 zfs-auto-snap_hourly-2018-06-15-12h00<br />
zfs-auto-snap_hourly-2018-05-26-00h00 zfs-auto-snap_weekly-2018-06-09-03h00<br />
</pre><br />
Or this, on an Isilon filesystem:<br />
<pre><br />
sattwood@vimur:~$ pwd<br />
/nfshomes/sattwood<br />
sattwood@vimur:~$ cd ifs/.snapshot<br />
sattwood@vimur:~/ifs/.snapshot$ ls<br />
daily_2018_06_14__20_00 hourly_2018_06_14__12_00 hourly_2018_06_15__04_00 weekly_2018_06_09__20_00<br />
daily_2018_06_15__20_00 hourly_2018_06_14__16_00 hourly_2018_06_15__08_00 <br />
hourly_2018_06_14__08_00 hourly_2018_06_14__00_00 hourly_2018_06_15__12_00<br />
</pre><br />
For an example of file restoration, please see [[Snapshots:Example | this page]].<br />
<br />
<br />
[[Category:Snapshots]]<br />
__NOTOC__</div>Wrichmanhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=Snapshots&diff=9443Snapshots2020-11-09T19:33:08Z<p>Wrichman: Added more details for an Isilon filesystem</p>
<hr />
<div>Snapshots are a implementation of [http://en.wikipedia.org/wiki/Copy-on-write copy-on-write] that allows for a file system to quickly take a point-in-time copy of the file system and provide access to the data through a .snapshot directory. Snapshots provide a fast, user-accessible way to recover data that has been accidentally deleted or corrupted within a recent time window -- rather than having to retrieve the data from comparatively slow tape backups. They also help to span the time gap between full backups.<br />
<br />
We provide [[Snapshots]] on our ZFS, [[Snapshots:FluidFS | FluidFS]], and Isilon filers to certain file systems. If you are ever unsure if a particular volume has Snapshots enabled, please contact the [[HelpDesk | Help Desk]].<br />
<br />
==Snapshot Retention Policy==<br />
Our core file systems in the department are on a 4 hour snapshot cycle. <br />
<br />
{| class="wikitable"<br />
!Snapshot Name<br />
!Retention Length<br />
!When is it taken?<br />
|-<br />
|'''Hourly'''<br />
|24-32 hours<br />
|Every day 12am, 4am, 8am, 12pm, 4pm<br />
|-<br />
|'''Daily'''<br />
|2 days<br />
|Every day 8pm or 12am<br />
|-<br />
|'''Weekly'''<br />
|1 week<br />
|Every Saturday 8pm or Sunday 12am<br />
|}<br />
<br />
In other words, we retain up to either 6 or 8 hourly snapshots, 2 daily snapshots and 1 weekly snapshot. Hourly snapshots may be superseded by daily snapshots, and daily snapshots may be superseded by the weekly snapshot.<br />
<br />
==Snapshot Restoring==<br />
<br />
If you have deleted a file by mistake and you need to get it back, you can use the snapshots directory to recopy the file.<br />
<br />
This directory can typically be found in your home directory. It generally will not be visible, even when viewing hidden directories.<br />
<br />
'''It will be either''':<br />
<br />
* .snapshots for the [[Snapshots:FluidFS | FluidFS]] filer<br />
* .zfs/snapshot for the ZFS filer<br />
* ifs/.snapshot for the Isilon filer<br />
<br />
The inside of one of these will look something like this on a FluidFS filesystem:<br />
<pre><br />
sattwood@zaphod:~$ pwd<br />
/nfshomes/sattwood<br />
sattwood@zaphod:~$ cd .snapshots<br />
sattwood@zaphod:~/.snapshots$ ls<br />
daily_2018_06_14__20_00 hourly_2018_06_14__12_00 hourly_2018_06_15__04_00 weekly_2018_06_09__20_00<br />
daily_2018_06_15__20_00 hourly_2018_06_14__16_00 hourly_2018_06_15__08_00 <br />
hourly_2018_06_14__08_00 hourly_2018_06_14__00_00 hourly_2018_06_15__12_00 <br />
</pre><br />
Or this, on a ZFS filesystem:<br />
<pre><br />
sattwood@swirl:~$ pwd<br />
/nmhomes/sattwood<br />
sattwood@swirl:~$ cd .zfs/snapshot<br />
sattwood@swirl:~/.zfs/snapshot$ ls<br />
zfs-auto-snap_daily-2018-06-13-01h00 zfs-auto-snap_hourly-2018-05-28-00h00<br />
zfs-auto-snap_daily-2018-06-14-01h00 zfs-auto-snap_hourly-2018-05-29-00h00<br />
zfs-auto-snap_daily-2018-06-15-01h00 zfs-auto-snap_hourly-2018-06-03-16h00<br />
zfs-auto-snap_hourly-2018-05-24-00h00 zfs-auto-snap_hourly-2018-06-10-08h00<br />
zfs-auto-snap_hourly-2018-05-25-00h00 zfs-auto-snap_hourly-2018-06-15-12h00<br />
zfs-auto-snap_hourly-2018-05-26-00h00 zfs-auto-snap_weekly-2018-06-09-03h00<br />
</pre><br />
Or this, on an Isilon filesystem:<br />
<pre><br />
sattwood@vimur:~$ pwd<br />
/nfshomes/sattwood<br />
sattwood@vimur:~$ cd ifs/.snapshot<br />
sattwood@vimur:~/.snapshots$ ls<br />
daily_2018_06_14__20_00 hourly_2018_06_14__12_00 hourly_2018_06_15__04_00 weekly_2018_06_09__20_00<br />
daily_2018_06_15__20_00 hourly_2018_06_14__16_00 hourly_2018_06_15__08_00 <br />
hourly_2018_06_14__08_00 hourly_2018_06_14__00_00 hourly_2018_06_15__12_00<br />
</pre><br />
For an example of file restoration, please see [[Snapshots:Example | this page]].<br />
<br />
<br />
[[Category:Snapshots]]<br />
__NOTOC__</div>Wrichman