-12-15
10:19:11:
> From: "Moyer, Joni M"
> To: ADSM-L@vm.marist.edu
> Date: 2010-12-15 10:21
> Subject: Re: Slow client backup
> Sent by: "ADSM: Dist Stor Manager"
>
> Hi Richard,
>
> It appears that there is a mixture of jfs, jfs2 and sybasedb. The
>
u] On Behalf Of
Richard Sims
Sent: Tuesday, December 14, 2010 3:59 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Slow client backup
Out of curiosity, is the file system JFS or JFS2? The former employs the old
traditional, inefficient, linear directory structure, while the latter
employees B-tree dat
Out of curiosity, is the file system JFS or JFS2? The former employs the old
traditional, inefficient, linear directory structure, while the latter
employees B-tree database structure for better performance.
Richard Sims
As other have indicated, journal based backups are a good thing to think about.
You could also look into increasing the resourceutilisation and maxnummp. To
make those work you may need to split up the filesystem (using
virtualmountpoint). Last, if jbb is not an option, look into incremental by
You can also try a journal based backup,
http://publib.boulder.ibm.com/infocenter/tsminfo/v6/index.jsp?topic=/com
.ibm.itsm.client.doc/c_bac_jbbwin.html
Maybe use / try Virtual volume mount concept to break it up in smaller
chunks assuming its one big vol
http://publib.boulder.ibm.com/infocente
I would investigate journal based backups for AIX.
http://publib.boulder.ibm.com/infocenter/tsminfo/v6/index.jsp?topic=/com.ibm.itsm.client.doc/c_bac_jbbunix.html
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Moyer,
Joni M
Sent: Tuesday, Dec
The only thing that has worked for us in these types of cases is to run a
selective backup rather than an incremental.
This way TSM just backs up every file rather than going through the examination
process.
This may or may not help you as I don't know the specifics of your systems.
JoeA
Joseph A
