EMC Networker 7.6 SP2 - groups of client resources

Do these clients in group1 and gorup2 have the same saveset?  I guess yes... while I can't see logic behind such setup, from NW perspective you have 2 same clients with backup of 2 same data sets. If you wish to force full backup on specific (same day), assign schedule to group (and not client) unless there are more clients in the group (as group schedule would override client's schedule). Also, remove force incremental (that option forces incremental backups for same data sets in period less than 24 hours and most likely that is exactly what is causing your "issue").

Hi,

Hrvoje Crvelin wrote: Do these clients in group1 and gorup2 have the same saveset?

Yes. these clients in group1 and gorup2 have the same saveset.

I can't see logic behind such setup

This configuration is only for testing.

So regarding my configuration, is it possible to do backup with the following configuration:

1. First Client resource for client: test001.domain.local

save set: C:\Temp

group: Group01

backup schedule on this client resource: full every day, incremental every 4 hours

media pool: pool01

2. Second Client resource for client: test001.domain.local

save set: C:\Temp

group: Group02

backup schedule on this client resource: full every day, incremental every 4 hours

media pool: pool02

I'm testing this confguration, because I want implement similar configuration in production, that's means:

a few client resources with one group (for example: group001) and save sets will be saving to media pool: pool001 (which contains AFTDs)

The same client resources (with the same save sets) with another group (for example: group002) and save sets will be saving to another media pool: pool002 (which contains tapes)

is above configuration will be correct ?

What you should do is following:

- Group001 as it is (pool, client, saveset, ect).

Then configure cloning to pool2 and that's it. You will use less resources, achieve the same and be more happy.

OK, but what about the following configuration:

For example:

the first group with one client resource:

I want to do full backup of SQL every day, and incrementral backups aobut every 4 hours and save save from this backup will be saving to AFTD.

so above configration will allow to very fast recovery in case of failure

the second group with one client resource:

and I want also to do the same SQL server to backup full every once a week (for example in sunday) and incremental i other days (from monday to friday) and save sets from this configuration will be saving to tape with retention and browse policy of one month so it will allows to have a recovery sql up to one  recent month

will it be correct configuration ?

You don't say for how long you retain data in first case.  And it does not matter because each time you make backup of SQL you are messing up with SQL sequence numbers. So you need to ask yourself following - for how long do I need this data? 1 day? 1 month? It's up to you, DBA, SLA or whatever/whoever, but there is one retention. Then, you can have this on tape or AFTD. It sounds as you use classic setup from several years ago with disk cache pool and physical tape repository on backend. You need to calculate how disk your need if you wish to keep it there for X time (where X is < less than your retention used). Usually you are limited by budget and available volume so you end up using staging with some threshold of 75-80% (this depends on frequency of cleanups and time required to complete cleanup opposed to time required to fill space above threshold). And that's how you do it. Again, one group only.