SQL DB backup not to overlap transaction log - Is there a way ?

You can have client (single one) and have client assigned to two groups (or workflows in NW9).  From client (workflow in NW9) you control backup level (better said you override in NW8 and in NW9 you must specify that client can't override settings).  Time of execution you control at group level (workflow in NW9).

That's exactly how we run our transaction log backups, our environment calls for a trnlog backup every 15 minutes.

Which we have one policy driving those backups, and another that runs Full / Cumulative Backups on a nightly basis.

We run NMM 9.1 with Server 9.1.1.

On 8.2 and before we had to create 2 groups, and schedule the times accordingly.

Thanks Hrvoje,

Networker 8.X is the environment.

But here I dont want the same client to overlap the schedules, suppose if I put them in 2 different groups(NW8.2) like it is scheduled today. The log backups will definitely overlap during the start time and duration of full backup group. I am using Force incremental to avoid this however I am not able to control the start time of Full as it is happening full level backup as first backup of 24hrs and rest all runs are incremental. Is there a way to tune the full backup time in force incremental enabled group ?

Thanks fmgtech,

But when you say you schedule the group timings accordingly in 8.X environment, my question is how you would avoid your incremental backup not to overlap full DB backup because your incrementals are scheduled to run every 1hr or 2hrs ??

There might be a better way to do this, but how we had it configured we would execute a .cmd or.ps1 that ran an hour before going into Full (Group Back Up).  This script was run on the actual nw server itself through Task Scheduler.

nsradmin -s

print type:nsr group; name:

Update Autostart; Disabled

y

When the Backup Full group finished executing we had a post-cmd to enable the translog group.

nsradmin -s

print type:nsr group; name:

Update Autostart; Enabled

y

I do not recall seeing a skip functionality for certain times in Networker 8.2.  Again there may be a completely different way of handling this, but if I recall correctly that is how I configured to run dual groups and not have the overlap.

In my case I run TLOG every 1h.  What I normally do is to place TLOG let's say at X:35 while DB group for clients inside would have start of their DB backups at (Y:05).  My SQL DBs might be smallish so most of them would be finished by the time DB group runs.  But even if and when not, NMM has introduced checks and makes this possible so that it does not mess up with restores (in some earlier versions that was possible, especially with NMSQL which I believe only in latest patch releases back then had it addressed).

If you wish to switch off TLOG while DB is running, then you would need to have pre/post commands where via nsradmin you could disable TLOG client before DB backup starts and enable it after DB backup has completed.

Thankyou All,

For now, what I have done is: Scheduled the Single Group : Full & Translog backup from same group with Force Incremental enabled. So my purpose of not letting it overlap is solved however the problem is with scheduling the Full level time (when to take Full Backup of DB). It by default triggers Full as first backup in 24 hrs so suppose my group is scheduled to start at 5 PM and I want my SQL log backups to happen every 30 mins so the first backup at midnight 00:00 is going to be Full and rest all will be incrementals.