Quote (nuvo @ Feb 25 2017 06:57pm)
What is actually running on this windows server you want to start/stop every day? Do your employees remote to it and work on it?
I am asking because such start/stop cycles -especially if done that way cannot be very good to it. Data loss is likely (they likely "pull the plug", not shutdown gracefully). And what if one of your employees is running 2 minutes late to save changes? What about backups? What if one day they take a little longer and are interrupted by your start/stop cycle?
All I'm saying is that this seems quite dangerous. The main server you're talking about, it's VPS or dedicated? If you run business, honestly, sometimes it's not worth it to save $50 :)
we all work remotely on there between 8am - 6pm
but all of our offices closes at 6pm, and i have backups scheduled between 6 -7pm, and then the server runs a scheduled batch file to shut down after the server finishes a backup
i believe google vm is vps?
honestly the only task i need the cron tab to do is just start my server in the morning because no one is really authorized to start it every morning besides me
Quote (AbDuCt @ Feb 25 2017 07:10pm)
Not to mention it's likely easier to stop the remote software service on the vm rather take the entire thing offline.
Most providers provide LISH or some other way to get into the server if ssh and the like are disabled.
im shutting it down thru a batch file so it should be safe?