Author: "Warren, Matthew (Retail)" <Matthew.Warren AT POWERGEN.CO DOT UK>
Date: Thu, 5 May 2005 16:09:29 +0100
Hallo *SM'ers Client o/s, SOLARIS SunOS 5.9 Dsmc 5.2.0.0 Dsmserv 5.2.2.3 on AIX 5.2.0.0 It appears incremental backup is missing/skipping filesystems Firstly, I am assured there were definitley many
Author: "Warren, Matthew (Retail)" <Matthew.Warren AT POWERGEN.CO DOT UK>
Date: Thu, 5 May 2005 16:24:09 +0100
The dsm.opt and dsm.sys files are generated each night and pushed out to the machines. The content of the dsm.sys and opt in question is; root@rhine-e# cd /opt/tivoli/tsm/client/ba/bin root@rhine-e#
Perhaps you are hitting a client options set on the TSM server? QUERY CLOPTS On Solaris clients, you might also check to make sure that the TSM config files in /opt/tivoli/tsm/client/ba/bin directory
Author: "Warren, Matthew (Retail)" <Matthew.Warren AT POWERGEN.CO DOT UK>
Date: Thu, 5 May 2005 16:33:36 +0100
We aren't using client option sets, but good idea I hadn't thought of them. The dsm.sys and dsm.opt are linked as follows; lrwxrwxrwx 1 root other 50 May 4 21:00 dsm.sys -> /app/scripts/config_files/
Author: "Warren, Matthew (Retail)" <Matthew.Warren AT POWERGEN.CO DOT UK>
Date: Thu, 5 May 2005 16:37:12 +0100
Ok, here's a copy of the include/exclude list on the machine; this is from the incl/excl file, NOT query inclexcl on the client. (although q inclexcl does give the same info, I have checked) root@rhi
Author: William Jean <wjean AT GLASSHOUSE DOT COM>
Date: Thu, 5 May 2005 11:40:47 -0400
Try excluding /etc/mnttab ________________________________ Hallo *SM'ers Client o/s, SOLARIS SunOS 5.9 Dsmc 5.2.0.0 Dsmserv 5.2.2.3 on AIX 5.2.0.0 It appears incremental backup is missing/skipping fi
Hmm, then indeed that does seem to be strange. The fact that the filespaces don't even show up in a "q fi" is really strange. By the looks of your filesystem /home is not an NFS mount, so they really
Author: "Warren, Matthew (Retail)" <Matthew.Warren AT POWERGEN.CO DOT UK>
Date: Fri, 6 May 2005 12:09:15 +0100
Hallo, And thanks for the suggestions, they prompted us to investigate a few avenues. We tracked it down to an issue with the 5.2.0.0 client on Solaris. Upgrading to 5.2.2.0 has fixed the problem - a