SSDs should work well for the DB and active log. As for the filesystem,
you'll want to use ext4. I don't know that IBM has documented filesystem
restrictions for DB2 wrt TSM, but certainly for standalone DB2 they
recommend only ext2/3 (and presumably now ext4) and reiserfs due to their
direct I/O
Robert:
According to this document:
http://www-01.ibm.com/support/knowledgecenter/SSGSG7_7.1.1/com.ibm.itsm.perf.doc/t_perf_diskos_lnx.html
- Use Linux Logical Volume Manager (LVM) to create logical volumes on
the disk LUNs for all disks that are used for Tivoli Storage Manager
Hi,
Maybe if you restore the vm with a new name...
Before check these values for your backup
select * from summary_extended where sub_entity='vmane'
De :McWilliams, Eric emcwilli...@medsynergies.com
A : ADSM-L@VM.MARIST.EDU,
Date : 2015-03-23 16:39
Objet : [ADSM-L] Restore error
Hello to all
TSM server version 7.1.1.100
I wonder if I can relocate my DB and ACTIVELOG in the same step .
? In dsmserv.opt change ACTIVELOGDirectoryH:\tsmlog (NEW
location)
? dsmserv restore db todate=today on=dbdir.file
(dbdir.file NEW
Hello
Another question about this , is if I need before the dsmserv restore db
command to do:
dsmserv removedb TSMDB1 ?
Best Regards
Robert
Hello to all
TSM server version 7.1.1.100
I wonder if I can relocate my DB and ACTIVELOG in the same step .
? In dsmserv.opt change
I haven't received any replies so I thought I would re-post.
Please forgive me if you've see the post already.
Is there any way to recover from this error? I'm trying to restore a full vm.
I deleted the vm but before I could get the tape back to do a restore someone
created a new vm with the
