Unsolved

This post is more than 5 years old

29 Posts

1625

May 16th, 2011 06:00

Sorting backup data to pools with NMM 2.3, does not reflect settings in client resource.

Hi all,

I am testing NMM 2.3 - Exchange 2010 backup. When set pool in client resource, it is not accepted, it works only when configure data source in media pool resource. Online help in client resource configuration dialog say, this criteria overrides any other. It works fine with standard backups, but not NMM 2.3.

Is anybody observing the same behavior?

Martin

Pool - Media pool used for data target selection during scheduled backup of the save sets specified in this client. This attribute is supported on 7.6.1 or later clients. Backup may fail on older (pre-7.6.1) clients for non-NULL value. This pool selection overrides any other pool criteria assoicated with the group or save set for this client.

May 16th, 2011 07:00

Hi Martin,

For NMM 2.3 you cannot select a pool in the client configuration. Please note that, as NMM backups are VSS based (Snapshot) you need to check the box, in the group configuration "Snapshot Backup" then select the snapshot policy, and the pool to be used by that group.

Please check those settings and let us know if that helps.

Thank you.

Carlos.

29 Posts

May 17th, 2011 05:00

Thank you for quick response Carlos.

Does it mean, documentation is wrong? In the pool specified in save group goes not only snapshot metadata (.xml) but whole snapshot?

*******

7.6.2 online help

Snapshot Pool - The pool to which snapshot save set meta-information should be sent.

NMM2.3 - Admin Guide REV A02, page 57 "Configure a backup group"

Configure a backup pool for snapshot operations

Snapshots create metadata that is used in the management of snapshot operations

such as an instant recovery operation. Create a snapshot pool to store the save sets

that contain snapshot metadata.

*********

My save group SNAP1 has snapshot checkbox and pool selected (HOBPool1).

Client set pool testpool,  (but as you write it is not used). Save command is nsrsnap_vss_save and save set APPLICATIONS:\Microsoft Exchange 2010

In pools HOBPool1, HOBPool2 definition is group SNAP1 in Selection Criteria NOT specified.

Save command ist starting with this parameters:

Invoking command: "nsrsnap_vss_save.exe -A  optype=conventional  -A "NSR_SNAP_TYPE=vss"  -A "NSR_EXCH_CHECK=no"  -A "NSR_ALT_PATH=C:\nsr_mount_replica\"  -A "NSR_EXCH_RETAIN_SNAPSHOTS=yes"  -A NSR_PARENT_JOBID=2067180  -b testpool -c cz-hb-ex -g "SNAP1" -LL -m cz-hb-ex -s cz-hb-backup.cz.lasselsberger.com -t 1305633669 -l incr -q -W 78  -A snap_sessionid=1305633988  -A NSR_STRICT_SYNC=0 "APPLICATIONS:\Microsoft Exchange 2010

->> Backup is directed to pool Default, not HOBPool1 as specified in SNAP1 group definition.

*******

Second case, when:

In pool HOBPool2 definition IS group SNAP1 in Selection Criteria specified.

Invoking command: "nsrsnap_vss_save.exe -A  optype=conventional  -A "NSR_SNAP_TYPE=vss"  -A "NSR_EXCH_CHECK=no"  -A "NSR_ALT_PATH=C:\nsr_mount_replica\"  -A "NSR_EXCH_RETAIN_SNAPSHOTS=yes"  -A NSR_PARENT_JOBID=2067153  -b testpool -c cz-hb-ex -g "SNAP1" -LL -m cz-hb-ex -s cz-hb-backup.cz.lasselsberger.com -t 1305632442 -l incr -q -W 78  -A snap_sessionid=1305632816  -A NSR_STRICT_SYNC=0 "APPLICATIONS:\Microsoft Exchange 2010

->> Backup is directed to pool HOBPool2.

*******

Backups are not directed to pool configured in snapshot group, parameter is useless with NMM2.3. Pool selection is possible only via backup pool configuration - Data Source or Selection Criteria.

Or am I making something wrong?

Regards Martin.

May 18th, 2011 08:00

Hi Martin,

Please allow me to guide you step by step so we are on the same page. I'll try to use the same names that you use:

Pool name: HOBPool1

This pool has to have the group SNAP1 allowed to send data into it's devices.

Group name: SNAP1

This group will contain the NMM clients

This gorup will have the Snapshot Backup selected

This group will have the Snapshot Pool "HOBPool1" selected

This group will have the Snapshot Policy "Serverless Backup" selected

client name: cz-hb-ex (Understanding this is an stand-alone Exchange 2010 server)

This client will have the save set: APPLICATIONS:\Microsoft Exchange 2010

This client will have no Pool selected in the configuration (pool is already selected in the group)

This client will have any schedule set, although if there is one set in the group, the one in the group will be used.

This client will have the following Application Information:

NSR_SNAP_TYPE=vss

NSR_ALT_PATH=C:\nsr_mount_replica )this is the one you have already set however it can be modified to use any path residing in local disks, it's not supported to use any clustered disk for this path)

There are some other Application variables available, but I won't get into details as in this particular case we are talking about Pool issues and not backup/configuration issues. Please refer to NMM 2.3 Documentation for further information about the different variables available.

With that configuration the backup for client cz-hb-ex, in group SNAP1 should be using devices/tapes from pool HOBPool1

Please let me know if you need any further information.

Thank you.

Carlos.

29 Posts

May 19th, 2011 03:00

Hello Carlos,

it is exactly as you write with some remarks.

Client will have any of available pools selected or nothing ( I tested both variants).

Important:

Media pool HOBPool1 settings - Basic - Data Source - here is group SNAP1 NOT SELECTED, unchecked

Media pool HOBPool1 settings - Selection Criteria - only corresponding tape devices checked, Clients list. Save sets, Levels - NOTHING filled, nothing selected.

With this configuration should backups be saved to pool HOBPool1 and index to Default pool. But it is only to Default pool saved, HOBPool1 isn't used.

If you check in HOBPool1 settings SNAP1 as source, or fill client entry, then is snapshot saved to HOBPool1.

Regards Martin

May 19th, 2011 06:00

Hi Martin,

You need to check the box for the group SNAP1 in the pool HOBPool1.

The meaning of selecting groups within a pool, is to allow those groups to send data to the pool you are configuring, so in order to use pool HOBPool1 you need to check the box for SNAP1.

At the same time, the selection criteria for devices is restrictive it means that, if you don't check any device, that pool will try to use any device configured available, but if you select any device, you are setting a restriction for that pool to use only the devices you have selected.

In other words:

The groups selection is for configuration purposes (allow groups to use that pool)

The devices configuration is restrictive (to restrict which devices will be used by that pool).

Please let me know if you need any further information.

Thank you.

Carlos.

29 Posts

May 20th, 2011 01:00

Thank you Carlos for explanation. But if I add snap group SNAP1 to pool config HOBPool1, as you propose, then is the parameter "Snapshot pool" in group resource completely useless, whatever pool is filled, every time is backup directed to pool HOBPool1 (where group SNAP1 is selected as Data Source for this pool). My question is, how to achieve, what must be done, to make backups to pool selected in snapshot group resource? From my point of sight, settings in pool resource has precedence over this. It could probably work when I was able make snapshot group SNAP1 to member of more pools. But I am not able to configure it, every time when configure additional pool I am ending with message "Pool SNAP1 has overlapping criteria". What must I do, in order to "Snapshot Pool" in group resource is really active and functionally, if I switch here to another pool it will be really backup made to this pool?

With only Networker core backup (without snapshots, no module) is behaviour different. I need not specify save group in pool resource, it is sufficient choose the pool in client resource.

Martin

No Events found!

Top