5 Posts

October 14th, 2012 10:00

I think you are using backup of both active and passive databases.

1. Check whether Group which you have created for Exchange backups is added in the desired media pool or not.

2. Refresh service for RMAgent and check if it is started and automatic.

1.7K Posts

October 17th, 2012 03:00

Hi Sgupta,

Are you running the backup for the 2 physical nodes at the same time in the same group? If so then you need to change this variable:

NSR_EXCH2010_BACKUP=all

If running the backup for more than one DAG node at a time, then you need to set either active or passive, if you set all and run backup for more than one node it will fail as one Exchange DB can be backed up ONLY once at a time.

Also ensure you have created a client entry, but not scheduled for backup nor included in any group, for the DAG itself, in this case you need to create a client entry (with FQDN) for name dagapollo.imcl.com. Ensure you add all the aliases correctly within the Alias field in the client configuration.

Also ensure that the snapshot pool you have selected for the group has the group selected in the "Data Source. Groups" field of the pool, and also ensure there are devices available for that pool.

Thank you.

Carlos.

October 23rd, 2012 03:00

Hi,

If you are using

NSR_EXCH2010_BACKUP=all

It causes fails . Try to backup only one database with the NSR_EXCH2010_BACKUP=passive or active.( It depends on your dbs status) If you can backup succesfully you have to split your save set for active and passive dbs .

Also if you can run this command on dag client and share the output with us.

nsrsnap_vss_save.exe -? -v

544 Posts

October 23rd, 2012 04:00

Hi SGupta,

These error messages "may" indicates either a problem with name resolution or a wrong configuration of the client entries including pools configuartion.

Please ensure the following:

1- The client entries are created properly and that all the possible aliases are included within the "Alias" field in the client configuration. (FQDN & Shortname)

2- NetWorker server is able to resolve the names properly for the Exchange 2010 servers and vice versa.

3- If you have multihomed NIC in Exchange servers, ensure that configuration and Name Resolution works fine for the appropriate Interface.

4- Check that the pool is correctly configured for the group, check if the pool selected in the group configuration, Below the Snapshot policy has selected that group checked in the Selection criteria field in the pool configuration.

Hope this helps,

Ahmed Bahaa

November 12th, 2013 00:00

Update the application information in client

NSR_SNAP_TYPE=vss

NSR_ALT_PATH =N:\snap

NSR_EXCH2010_BACKUP=all | active | passive

NSR_EXCH2010_DAG=

NSR_IGNORE_MISSING_SYSTEM_FILES=yes

Update the application info in DAG client

NSR_SNAP_TYPE=vss

NSR_ALT_PATH =N:\snap

Check Microsoft Exchange Writer and Microsoft Exchange Replication Writer is stable in exchange node by running command vssadmin list writers

check there are enough shadow storage space

Vssadmin list shadowstorage

Check the services in client

Replication Manager Client for RMAgentPS

Replication Manager Exchange Interface - should run from exchange admin account

check nasrsnap_vss_save -? completing successfully in exchange node

No Events found!

Top