Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[ADSM\-L\]\s+HSM\s+for\s+Windows\s+additional\s+notice\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[ADSM\-L\]\s+HSM\s+for\s+Windows\s+additional\s+notice\s*$/: 2 ]

Total 2 documents matching your query.

1. Re: [ADSM-L] HSM for Windows additional notice (score: 1): Author: Josh Davis <xaminmo AT OMNITECH DOT NET>; Date: Mon, 9 Apr 2007 16:13:41 -0500; One correction - recall on properties happens for executable file types. Still need info on backup before migrate seeming to require HSM to use the same node name as the baclient. I'm at HSM 5.4.0.3; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2007-04/msg00151.html (11,951 bytes)
2. [ADSM-L] HSM for Windows additional notice (score: 1): Author: Josh Davis <xaminmo AT OMNITECH DOT NET>; Date: Mon, 9 Apr 2007 15:56:43 -0500; Notes about recall: Right click, properties If it's on a directory, it's ok. If it's on a migrated file, it forces a recall Notes about DSMFILEINFO: dsmfileinfo doesn't seem to accept wildcards dsmfi; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2007-04/msg00152.html (11,269 bytes)

Current List: 1 - 2
Page: [1]