Klaus,
It turns out that the behavior has, indeed, changed between PTF5
and PTF6 for IRIX--unfortunately, I hadn't noticed this, as it
totally changes our paradigm for home directory backups.
For a client using PTF 5, the following is the result of 'q
files':
Num Last Incr Date Type File Space Name
--- -------------- ---- ---------------
1 03/31/99 00:00:37 XFS /
1 03/31/99 00:00:37 XFS /
2 03/31/99 00:00:48 XFS /dashit1
3 00/00/00 00:00:00 AUTOFS /usr/home
4 01/21/99 23:47:24 XFS /usr/home/philrowe
(notice the AUTOFS /usr/home entry, with no backup time/date).
On a similarly equipped system, running PTF6:
Num Last Incr Date Type File Space Name
--- -------------- ---- ---------------
1 03/31/99 00:08:21 XFS /
1 03/31/99 00:08:21 XFS /
2 03/31/99 00:09:14 XFS /bembe1
3 01/21/99 23:49:36 XFS /usr/home/billh
Notice that '/usr/home/billh' hasn't had an incremental backup
since 1/21/99--the day we upgraded to PTF6 on this client.
What happens now is that an incremental of the VIRTUALMOUNTPOINT
/usr/home/billh results in no files being sent, but a
"successful backup" being reported by ADSM--a not altogether
useful thing.
-- Tom
Thomas A. La Porte
DreamWorks Feature Animation
tlaporte AT anim.dreamworks DOT com
On Wed, 31 Mar 1999, Klaus Steinberger wrote:
>On Thu, Mar 25, 1999 at 08:21:29AM -0800, Thomas A. La Porte wrote:
>> What version of the client are you using?
>3.1.06 on IRIX, the unsuported native Linux Version, and 3.1.0.6 on HP/UX.
>
>> We've found that using the VIRTUALMOUNTPOINT option works for us,
>> using SGI client (PTF 5 and 6). The VIRTUALMOUNTPOINT is made on
>> the mountpoint directory (in your case /home/xxx). We then create
>> a domain statement in the options file for each of the
>> VIRTUALMOUNTPOINT entries.
>It did not work for me, I tried Virtualmountpoint, as well as domain,
>and also the followsymbolic option. Nothing helps.
>
>> When you use this method, you end up with each home directory as
>> a separate filespace, which turns out to be a benefit for us as
>That would be Ok for me too, as I have /home/group/user, and I
>want to see /home/group as filespaces (the mountpoints are on this level).
>
>For example, I have the following in the dms.sys file on a machine (stripped
>down):
>
>defaultserver homes
>
>Servername local
>...... some options for local node
>
>Servername homes
>tcpserveraddress xxxxx
>tcpport xxxxx
>
>nodename global.physik.uni
>passwordaccess generate
>inclexcl /usr/adsm/etc/dsm.excl.homes
>schedlogretention 14
>schedmode prompted
>schedlogname /var/adm/dsmsched.log.homes
>virtualmountpoint /scratch/etphp01
>
>
>And in dsm.opt.homes (which is called by a wrapper script):
>
>tapeprompt no
>followsymbolic yes
>domain /scratch/etphp01
>
>"bdf -l" shows the following:
>
>/dev/vg00/lvol9 262144 214676 44535 83% /export/scratch/etphp01
>/export/scratch/etphp01
> 262144 214676 44535 83% /scratch/etphp01
>
>In "dsm" I /export/scratch/etphp01 in the local filespaces, but I do not
>see it as /scratch/export (also not in the network filespaces). The latter
>is the one I want of course, as from other machines this will be seen
>in this way. The global.physik.uni node is seen on any of our machines,
>and the user should see their files in the same filespace regardless on
>which machine they login.
>
>Sincerely,
>Klaus
>
>--
>Klaus Steinberger Beschleunigerlabor der TU und LMU Muenchen
>Phone: (+49 89)289 14287 Hochschulgelaende, D-85748 Garching, Germany
>FAX: (+49 89)289 14280 EMail: Klaus.Steinberger AT
>Physik.Uni-Muenchen DOT DE
>URL: http://www.bl.physik.tu-muenchen.de/~k2/
>In a world without fences and walls, who needs Windows and Gates?
>
|
