Hi,

NSR_SAVESET_RETENTION and NSR_SAVESET_BROWSE only work with client initiated 
backups.

If you are running a server initiated backup ( group)  Nw will use the 
parameters configured on the client.

jee
 



On Wednesday 05 Dec 2012 06:21:04 mikehorizon wrote:
> Facts:
> - backup online DB2 using conf file
> - the GUI Networker shows multiple entries of the DB2 client. Highest
> retention: 10 years, highest browse time: 3 months. - content of NMDB2 conf
> file:
> NSR_CLIENT=client1
> NSR_SERVER=server1
> NSR_DATA_VOLUME_POOL="Daily"
> NSR_LOG_VOLUME_POOL="Daily"
> NSR_DEBUG_LEVEL=1
> NSR_DEBUG_FILE=/nsr/applogs/client1db2inst1_api_db2.log
> NSR_LIBNSRDB2_DEBUG_LEVEL=0
> NSR_LIBNSRDB2_DEBUG_FILE=/nsr/applogs/client1db2inst1_api_db2sql.log
> NSR_SAVESET_RETENTION="2 months"
> NSR_SAVESET_BROWSE="2 months"
> NSR_HARD_SESSION_LIMIT=4
> DB2_VENDOR_LIB_PATH=/usr/lib/libnsrdb2.o
> DB2INSTANCE=client1db2inst1
> DB2_PARALLELISM=2
> DB2_NUM_BUFFERS=2
> DB2_SESSIONS=4
> DB2_ALIAS=base1
> DB2_NODE_NAME=db2node1
> DB2_USR=inst1
> DB2_OPTIONS=DB2BACKUP_ONLINE,
> DB2BACKUP_INCLUDE_LOGS
> DB2_PSWD=password
> 
> 
> Problem: the saveset of the DB2 online backup has 10 years retention and 3
> months browse time instead of the values specified in the NMDB2 conf file:
> 2 months. The rest of the parameters in NMDB2 conf file are taken into
> consideration, but not NSR_SAVESET_RETENTION and NSR_SAVESET_BROWSE.
> 
> Anyone has any idea why?
> 
> Thanks in advance.
> 
> +----------------------------------------------------------------------
> 
> |This was sent by mihai.girba AT gmail DOT com via Backup Central.
> |Forward SPAM to abuse AT backupcentral DOT com.
> 
> +----------------------------------------------------------------------