When stacked the switches are all managed by the master stack member. Any command issued to the master unit is applied to the entire stack. If you make a console connection to a non-master unit, it will ask you to connect to the stack master.  During the copy process, you will not be able to issue any other commands, but the switch stays up and the command does not cause the stack to reboot. Here is what the process looks like. [IMAGE]  
Hi, Apologies if this is a simple question but I've made some VLAN and user account changes via serial cable on my PC6224 stack (3 switches). I see that the command to save these changes to the non-volatile ram / startup config is: I also assume this can be done via the WebUI via: [IMAGE] My question is: Does saving / copying the running config to the startup config cause the switch to reboot? Can I perform this command during production without fear of the switches / stack restarting? Also, If I connect to the master switch in my stack via serial cable and run the copy running-config startup-config command, does this apply to the entire stack and save the running config to every switch or does this command need to be run on each switch? Thanks in advance.
PowerConnect 6224 - Save Running Config - Reboot Required?