Unsolved
This post is more than 5 years old
3 Posts
0
1521
October 5th, 2018 10:00
Scripting level 0/1 (full/incr) networker backups in oracle
I've... had a reasonable pick through the documentation.
Pretty sure with some scripting we have for backups and a cronjob I could probably make this work (check backups, days since last 0/1, have some output, depending on output switch a file into the script the nsr client picks up from the DB host for running the backup, ignore the level 0/1 functionality in NSR and just run whatever backup the switched in script file tells it) but... is there anything innately build into NSR to check the number of days since the last level 0 and intelligently run a level 0 or level 1 backup as required? (So... >6 days since last lvl 0? Run lvl 0).
Currently if a scheduled level 0 is missed, level 1 backups will continue to be taken which may ultimately end up being useless with no base level full backup to roll forward from.
There's quite a bit in the pre/post scripting that looks promising but that I don't quite have a handle on. I'm coming at this from a DBA rather than from a backups ops perspective.
masonb
445 Posts
0
October 8th, 2018 01:00
Hello llamaalarmallama,
NetWorker does not have a function to run level full/1 if this backup fails or is not run for some reason. The notification from the failed backup is what we rely on for Backup Admins/Operators to take manual corrective action. The reason for constantly failing fulls should be investigated and corrected rather than workaround like this.
If this is missed for any reason then you are correct the schedule will continue with reliance on previous full, however as this full has dependent backups it will not be deleted as we know it is required - even after its retention period is passed. This safeguards against this type of issue being seen so you will always have the full backup any incremental backup is linked to unless manual action is taken to remove.
Set your notifications correctly and follow-up on corrective actions is a much more simple way to handle this.
You can check with mminfo for level full backups and date quite easily and build this into your Backup Admin procedures to ensure recent fulls are present or the failure/skip/omission reason looked at.
Regards,
Bill
ble1
2 Intern
•
14.3K Posts
0
October 9th, 2018 03:00
Can't you setup notification via Oracle Grid to see if RMAN backup failed? Also, in backup application you can set notification. From there you can set further which next backup you want to run.
llamaalarmallama
3 Posts
0
October 15th, 2018 16:00
The backup failure reasons/etc are... of course looked at. We're rather in our infancy using networker so... the configuration at the moment has 1 policy running several databases backups in series. If any of them fail, the whole policy stalls/fails and we get a large bunch of databases complaining of no backup.
As far as separating them out, I *think* the issue is one of scale. We're on... probably one of the largest oracle estates anywhere (about 4k production, 3k test) so, while it's not ideal, from the dba side of things I'm pondering what we can do to make things work a little smoother.
It seems... a little odd that networker is so ridged in this respect. A hard, inflexible schedule for backups seems to be rather asking for trouble with patch work/issues/etc all able to block a backup. While not every organisation will have the scripting we use to check backups, even looking at v$rman_backup_job_details/OEM/similar would give a good bit of feedback to networker and get a little more intelligence into the policy workflows (plenty of ways to skin that particular cat of course). Why not have a lvl 0/1 decided by the databases needs rather than a ridged schedule?
Edit: apologies for directing the reply to Hrvoje, more intended for William.
llamaalarmallama
3 Posts
0
August 10th, 2019 00:00
Sorry for coming back to and resurrecting a rather old post of mine.
I've continued being DBA, not given this too much more though.
However:
" Also, in backup application you can set notification. From there you can set further which next backup you want to run."
Would anyone be able to clarify this point.
So... set the notification that a backup has failed. Is there then any mechanism for NSR to take a different approach with it's next backup? Every other reply seems to intimate not and I'm probably just futilely hanging on a couple of words but... still looking for a way to crack this.
It isn't a case that failed backups are being ignored, if a backup server has issue... there's.... probably 20-100 backups effected as it's not a small estate. Re-running all of these by hand is rather pointlessly man-hours heavy.
crazyrov
4 Operator
•
1.3K Posts
0
August 11th, 2019 21:00
NetWorker does not have any inbuilt function that will apply remediation to any failed backups, this will be a manual process. The notification is to alert the backup/application administrator of a failed backup so that appropriate actions are taken by the respective team to fix the failure. Simply rerunning the backups might not be a fix to your backup issue if the underlying issue is resolved, I assume you have a dedicated backup operations team to look at backups if your IT landscape is that vast.