Hi, I'm doing some tests with the internal scheduler and it seems that it will do something strange in some circumstance.
It seems that if I start the gui but don't login to the browser interface the scheduling do not start so if I reboot the backup server and don't login to the gui I will get no backup job starting (not good at all).
More then this if I connect to the gui and there's some job that should have started in the past (when the gui scheduler was shutted down) it will start the backup job immediately and this is also not good because I have for example some oracle database that will do offline backup (shutting down and restarting oracle) and in this way It could happen that I get the database shutted down during working hour.
This is the step I've done to reproduce it (I have 1 configuration file only):
1) I've scheduled a backup to happen at 12.59.
2) At 12.56 and I shutted down the gui and started back it, waited until 13.03 and the backup was not run.
3) At this time I logged on the gui and as soon as I logged into the gui the backup started.
Is this the normal behaviour, a bug or there's something I've misconfigured ?
The snapcreator is version 3.4.0 installed under redhat linux 5.
Yes I am sorry to say this is a bug in both SC 3.3.0 and SC 3.4.0 (but wasnt reported or found till after release of SC 3.4.0). BURT 516935 has been created for this issue. The problem is that we use Quartz for our scheduler and we only start the Quartz process when someone logs or attempts to log into the GUI. This BURT has been fixed (starting Quartz when Jetty / GUI starts not when someone tries to log-in) and we will as far as I know be releasing a 3.4p1 (no confirmed date yet, we want to wait a few weeks to see what other bugs surface) with this fix as well as some others. The release notes are also being updated with this bug and some other's that were reported.
1. After restarting GUI, log-in once so scheduler starts
2. Dont use SC Internal Scheduler instead use crontab (UNIX)
3. Dont use SC Internal Scheduler instead use task-manager (Windows)
Hi Keith, thanks for the fast answer. We had the problem with 3.3.0 but we didn't check what was causing it because we was not using it, just testing so we never discovered that the problem was that it was needed to login into the product.
Anything about the other "issue" regarding the start of all past jobs? It seems not correct or at least I think it could be better to have a config option/startup option to define if when the gui start it should start all the past jobs or should wait until the next run cycle...
Do you think this can be solved/implemented too?
Regarding the workaround, so you think it's possible in some way to access a webpage on the server using something like wget to login automatically via script?
In my opinion the better will be, if possible, an option on every job that will allow or deny (just a checkbox) the automatic run of the job if it was not run at the last scheduled time (in case of a backup server failure).
With an option like this it will be possible to decide how to run each job in case of failure so, for example, offline database jobs will not be run while online database jobs or "high priority" backup jobs can be run just after the server restart in case of failure.
I hope the fix will be out soon we would like to start configuring all the backup of our dev/test Oracle Database server with SC3.4.0 but we do nightly offline backup so I would not like to risk that if the server restart for any reason I will get all the database shutted down during the day...
The time to resolve those 2 issue seems really long ... 2 more months for the first and 5 months for the job restarting options (without which restarting snapmanager gui and working with offline database backup will result in all database going down for backup ...).
No way to try to push those 2 issue at the developer attention for a hotfix release or something like that?
The product is really nice but those 2 issue, at least for my database administrator are a no-go for going in production with the product...
The more NGS cases the faster the fix can be made available, right now the scheduler issues arent viewed as super critical because you can use cron, task manager, or any other scheduling system to schedule SC. Though I agree would be really nice to provide a patch quicker.
It's not the coding, it is the process behind products that always takes the longest time.
Hi Keith, just some help to open the case with NGS... on NOW support site when I go to open a case I should put a serial number or choose between one of the serial number we have registered... should I choose a storage to open the case for Snap Creator or what?