Moderators ..please move arun's post to Solutions Enabler section.

Thanks

Thanks Dynamox - thread moved.
Julie

pretty much everything, SRDF/timefinder/VCDMB/device manipulation. I think by the default the log is set to keep 5 days worth of log info but you can bump that up to higher number ..as long as you have plenty of disk space where the log resides. Modify

SYMAPI_LOGFILE_RETENTION = 5

variable in symcli config file.

Agreed.So to be precise,I wouldnt be able to see the query commands run against the symapi_db.bin like "symcfg list","symmaskdb list assignment". So, I guess I could see only commands that dynamically contacts the Symmetrix to perform a change. In fact I can put it this way - anything that uses the symcli api will be logged in here, and those are nothing but the commands which will inturn be converted into SCSI commands by the symcli api ( library ). Am I right ?

Message was edited by:
arun2008

You can also set the debug mode to have a verbose/detailed info in the symapi log.
I can't remember the exact variable to use. I think it's something like SYMCLI_DEBUG=-1. something like that.

I don't remember me setting any retention period and the logs don't take up too much space. And if you want to keep them after all: zip them !

i just went through my logs and from what i can see the only things that get logged are actions that change array/device/masking parameters ..any kind of queries are not logged.

I stated SYMCLI_DEBUG=-1 (minus 1). As far as I know, it's the highest detail level.
There's something like SYMCLI_DEBUG_FILENAME variable so you can log the high detail into a different file.

setting symapi_debug=-1 will typically only be done at the request of EMC support to provide additional information on a failing operation for EMC engineering to diagnose. This is not something a customer will want to do unless support have explicitly asked for this information.