Author: Michael Garnebode <Michael_Garnebode AT WESTLB DOT DE>
Date: Mon, 8 Nov 1999 15:24:24 +0100
Hi all, my customer had a problem with his nt command-script. Hi start's the dsmc.exe in a script. The script is scheduled with the adsm-scheduler-service. When this backup-script is running in the b
Author: Glen Churchfield <glenc AT NETIONSYSTEMS DOT COM>
Date: Mon, 8 Nov 1999 20:47:39 -0500
By starting dsmc.exe from a script, you're defeating one purpose of the scheduler service which is that it runs as a system task which isn't disrupted by user login and logout. Why not just run the b
One option is to run it as a service, then it doesn't matter if anyone is logged in or not. You also have it randomly change its password, then you can start the service and forget about it. Michael
To establish it as a service perform the following: /password:yourpassword /autostart:yes You can then verify the schedule by looking at dsmsched.log. Kelly J. Lipp Storage Solutions Specialists, Inc
Author: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
Date: Sun, 04 Oct 2015 17:37:11 -0500
One option is to run it as a service, then it doesn't matter if anyone is logged in or not. You also have it randomly change its password, then you can start the service and forget about it. Michael
Author: Michael Garnebode <Michael_Garnebode AT WESTLB DOT DE>
Date: Mon, 8 Nov 1999 18:37:23 +0100
We run the scheduler at service. We define a schedule to start the *.cmd file with the dsmc.exe command. My customer say:" The schedule started ok but when the backup is running and a administrator i