Hi all,
A client is to restore something from multiple cartridges (regardless of
being collocated or not). Server mounts the first cartridge and the
restoration process starts . Does TSM server prepare (mount) the next
cartridge before it is actually needed if there are enough tape drives in
the l
Try this APAR:
IC63373: DB2 CONFIGURATION PARAMETER NUM_LOG_SPAN DOES NOT GET UPDATED
CORRECTLY WHEN THE ACTIVELOGSIZE IS CHANGED IN DSMSERV.OPT
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Zoltan Forray/AC/VCU
Sent: Monday, April 05, 2010 12
I haven't paid much attention to the CPU/Memory usage. There are only
5-really active and 24-semi active clients on this box. The biggest issue
is the DB load since there are over 100M objects for the 5-active clients.
I think the recommendation for memory is at least 8GB.
I just received 2-new
I've got a Win2K3 TSM server on 6.1.3.1.
Backup load is 2-3 TB per day, 160 daily client schedules, mostly
Windows , Linux, and SQL..
DB is ~200GB, 1 full per day works fine.
Nothing odd about DB backups on this platform IFF you have
ALLOWREORGTABLE NO
in dsmserv.opt, which is a workaround for an
>> On Mon, 5 Apr 2010 10:43:26 -0400, Zoltan Forray/AC/VCU
>> said:
> I schedule 3-FULL DB BACKUPS and DAILY VOLHIST BACKUPS on my lone V6
> server. This is the only way I have been able to keep my sanity
3 fulls a day? Owie.
I'm currently doing 1-2 fulls a week. This is nicht gut.
Applyi
A crucial point is the DB backups MUST BE FULL - Incrementals no longer
clear the logs!
In a previous discussion on this topic, it was determined you must also
perform corresponding VOLHIST backups.
I schedule 3-FULL DB BACKUPS and DAILY VOLHIST BACKUPS on my lone V6
server. This is the only w
>> On Fri, 2 Apr 2010 15:15:47 -0700, Dale Jolliff
>> said:
[...]
> http://www-01.ibm.com/support/docview.wss?uid=swg21214963
[...]
> Can anyone from IBM confirm that FILE device class over NFS is
> explicitly NOT supported?
Are you working a problem, or are you contemplating a planned conf
The TSM logfiles are indeed 500GB in size, as you noticed. Are there more than
20? All in you activelog directory? Is this a separate, dedicated, filesystem,
as recommended? You can increase the size of the active log by changing the
activelogsize parameter in your dsmserv.opt, but I doubt that
Hi,
this is a TSM defect in this version. The only way to reduce this space is
doing 2 DB Backups. In any case, I suggest you upgrade to 6.1.3.2
Regards,
Fran
- Mensaje original
De: Gibin
Para: ADSM-L@VM.MARIST.EDU
Enviado: lun,5 abril, 2010 06:37
Asunto: TSM Active Log --- Trou
