I scheduled a package to run daily at night 9.30 pm (the package is suppose to load the data on daily basis and the data will put in to backup
once the package is executed and It wont allow the previous day data) and It worked fine until Friday,
due to some server problem the package get failed on Saturday, and it worked fine on Sunday. My question is whether the data of Saturday
will be loaded in to database if yes how, if no means I want to load the Saturday data if it is
possible means, how will you load the Saturday data and where will you get the Saturday files.
Need return value
Related
I have a Scheduler Job within Cloud Scheduler running to call a Cloud Function. Working as expected however I need to create multiple cron schedules for the same job, is this possible without recreating from scratch each one? There doesn't seem to be a Copy function.
Use Case:
Schedule 1 - Every 15 minutes Monday - Thursday
Schedule 2 - Every 15 minutes Friday SoD till Friday 22:00PM
Schedule 3 - Every 15 minutes Sunday 22:00PM till Sunday EoD
How can I achieve this, or do I just need to recreate all the schedules from scratch?
Posting this as a Community Wiki as it's based on #GuillaumeBlaquiere and #Al-dann comments.
At this point you going to need to recreate all of those schedules from scratch, however, you can automate the creation of new Jobs with a script, either with gcloud or terraform. This will make duplication, creation and deletion of Jobs easier and quicker as well as allow you to version it.
So here is a thing, I have some lawyer app, and he needs to set reminder for some case, that reminder could be tomorrow, next week, next month idk. I was thinking about using node-cron, thing is i dont know what will happen when my app restarts, I assume it will crash all my reminders, and the second thing is how much will I load my server if i got to much reminders, OR do u have some other advice for this solution, maybe something with setInterval and run it every hour or something like that?
node-cron is used to run code as you would with normal cron, but in JS :)
So even if your code is crushed and restarted it will look at time set by you to execute some code and will not crush reminders.
For example if you run some code with cron condition 0 0 1 * *, which means every month on 1st date at 00:00.
That means that even if your app is crushed at 15th of month and restarted at 20th of month, it will run your job at 1st of next month at 00:00.
Between for automatically restarting your app you can use forever or pm2 packages from NPM
Now about this question.
how much will I load my server if i got to much reminders
I don't think it will load your server. node-cron internally uses setInterval, which is not CPU consuming, so go and run your crons without fear.
Am using logback xml to configure logging. I want the logs to be rolled over on an hourly basis. How would the behaviour be when daylight saving occurs?When the clock is advanced by an hour the logfile corresponding to that hour, does it get skipped?
When the clock is reverted by an hour, does the hourly file get overwritten?
What is the way to work around this?
Yes..as pointed put by #volodya and #Matt, logging in UTC format would be the ideal solution,
I'm looking for a way to be able to set my app to launch and carry out certain functions depending on the time and day of week. The app needs to be able to set the time and days of week, then run a specific function depending on that time and date. For instance if I set the app to run 1 function 12:00pm every Saturday, and another 3:00pm every Sunday, they can be processed in the background somehow. Essentially I want it to run like a scheduled background, where I might run an incremental backup during the week and a full backup on the weekend.
I've searched all over and can't seem to find any leads.
Any help would be greatly appreciated!
Thanks.
Take a look at Local Notifications: http://developer.apple.com/library/ios/#documentation/NetworkingInternet/Conceptual/RemoteNotificationsPG/Introduction/Introduction.html#//apple_ref/doc/uid/TP40008194
MS SQL Server 2008 Standard, ShadowProtect Server Edition 4.0.0.5885 --
On Friday, our client discovered that records were missing from the database. I discovered that the Thursday night SQL backup contained all the missing records. User error is ruled out for multiple reasons.
All missing records fall within an 8-day range
The date range began 22 days before Friday and ended 14 days before Friday
All adds and all changes made during the 8-day range are missing from 14 separate tables
All missing records are present in the Thursday 11pm backup
The application logs show no unusual incidents as far as I can see.
I find nothing unusual in the Applications list in the MS SQL Server Event Viewer.
We are running ShadowProtect Server to make image backups of the 2 server drives every hour. The same sort of incident occurred 4 months ago.
ShadowProtect runs an hourly backup of the database.
One theory is that the ShadowProtect Server 4 disk image software, which runs hourly differential backups, somehow caused the data loss during its 9:00 am Friday backup. I am not aware of any other activity. other than normal user accesses, between the normal 11 pm Thursday database backup and the discovery of missing records on Friday.
Thank you for you help. As you can imagine, the client is very concerned.
If you want to know what is deleting the records or when they got deleted, the database should have audit tables set up that include the usernames and dates of changes. Then you can look at the audit logs to see when reords were deleted and by whom or what process. All databases that contain business critical information should have auditing. Unfortunately, after the event has happened is too late to find out who did it this time through auditing. You might be able to find someone third party product to look through the transaction logs and at least might find out what time the deletes happened if not who. You also should be doing transaction log backups every 15 minutes or so.
I'm not familar with the ShadowProtect server, but the missing data sounds exactly like a script was run (and cacade delete was turned on) and seems unlikely to be the ShadowProtect server. If it was interfering, I would expect a more random kind of change that one that can easily be done by a sql query. Do you allow direct access to your tables? You could have someone trying to harm the data or hide fradulent activities. Threats to the data are not always from outside sources or applications that would be in the event log. Who has access to the delete the data in the database on production? I would suspect a disgruntled employee.
We never did find out the cause of the lost records. We reinstalled the database in another MS SQL Server instance, upgraded the database to a new release, and migrated the data from the old database to the new one. That seems to have fixed the issue.
I had similar issue on VM. The error was was pointing to the database but SQL Server wasn't actually running. For some unknown reason SQL Server has stopped. It seems that VM was restarted and the service didn't start automatically.
After starting the service with Windows Administrative Tools, server was back on and the database was there