Item Subject: Text_1
     Well, let me add my 2 cents worth...

     In implementing SAP I also noticed that THE BACKED UP FILES DON'T SHOW
     UP VIA THE NORMAL CHECKS.

     *** Did you assign a node name other than the actual node in the API
     code ? ? and what about the userid ? ?

     I noticed that SAP (if you don't know about SAP be glad) has code to
     backup and restore the databases associated with it and they use the
     instance name for the node name and (instance)adm for the userid...
     this might have been a customization option but no matter what when in
     ADSM I'm not sure if what I have been able to find is what I'm looking
     for.  ex. ip 12.34.56.78 has name netnode1.dom1.dom2.dom3 and on that
     machine there is code which refers to itself as MY1 and associated
     userid of my1adm  (NOTE THE CASE... it will make a difference) so... I
     fire up dsm from 'netnode1' and get my list of files (and I don't see
     what I'm looking for) then I use "untilities" (?) to set userid and
     node... I use id:my1adm and node:MY1  I get a refreshed/updated/new
     list of files... Some dates are not shown so I'm not quite sure what
     is going on BUT this poop is rather new to me and I can't just issue a
     restore to see what will happen (this dang place is 7x24)
     I do know that the (api) code to restore the databases does bring the
     needed files back.  (I would have experimented with it had I figured
     out how to find the files at an earlier date)
     *** conclusion: I just assumed it was a security feature !  Guessed
     that if someone was going to the time of creating special code there
     was probably a good reason.

     Talk about shock though... we were using straight full backups at
     first... (the ol' don't implement everything at once..) and all the
     data was there... then when we went to implement the SAP
     backup/restore interfaces and we made a fresh backup and we went to
     bring back a couple of files (via the standard GUI & default names) I
     got a real sick feeling at first when NOTHING was found!  I'm starting
     to relax a little because so far ADSM has not let us down :-)
     We have had a few implementation screw ups (SAP that is) and machine
     failures AND ADSM has pulled us through every time (knock on wood)

     Keep me posted on what you find out, if you would please...

     later
          Dwight