This effect is almost certainly due to hard drive contention and not caused by only one CPU being utilized. If you run top while the snapshot is executing, you are likely to see a high waiting for I/O (wio) percentage reported. CPU usage by a process can be "niced" by reducing CPU priority (command nice), and so can I/O priority (ionice). Try this:
1) Start the snapshot
2) Confirm slow SmartConsole performance
3) There should be two processes running that are related to the snapshot: xfsdump and xfsrestore. Determine their two process IDs (PIDs) via top or ps.
4) Confirm that their current I/O priority is 0 (best effort FIFO) - ionice -p PID1 ; ionice -p PID2
5) Set their I/O priority to idle (lowest possible): ionice -p PID1 -c 3; ionice -p PID2 -c 3
6) Retest performance and see if it has improved while snapshot is running
There is probably a way to have the snapshot I/O priority set to idle every time a snapshot is invoked but that will almost certainly need to be done by Check Point. Note that this will make the snapshot take longer to complete (potentially MUCH longer).
Attend my online "Be your Own TAC: Part Deux" CheckMates event
March 27th with sessions for both the EMEA and Americas time zones