Search:

default settings for collocation when defining new storage pool is "group"
as moon-buddy told, it should be set to NO
update stg LTOPOOL1 collocate=no

Reclamation most probably will not help...

tsm server should be able to see this device as a local device -> yes
it should be able to do some operations on it -> yes
then i should have to define the path as mt3.2.0.0 -> first off, media...

a) insert "include" statement into stanza in dsm.sys
b) insert "inclexcl /your/path/to/exclude/list/file/inclexc.txt" in your dsm.sys stanza and insert "include" statement(s) in this file...

TSM must be able to "see" media changer device and tape device(s) from target location (located in head-office). It means you have to be able to store any data from TSM server to library in remote...

dedicated stg pool with high migration threshold set to 0 (or close to 0) - if it needs to be on tapes asap, otherwise normal threshold should be enough
next migration stg pool set to the one which...

you have to do it from within database, check http://www.dba-oracle.com/t_monitor_rman_script.htm

Can you image then the request for restore? "My file abc.xyz got lost during last week, I'm not sure on what day. Please restore it." How would you continue? Restore friday image, check the presence...

Which return code is returned?
Was the backup even attempted?
Were there any entries in db2diag.log from that time?
Are DSMI_* variables correctly set up?
Does user runing scheduler have...

Is the error repeating only with the same volume? Time replace it.
Is the error repeating also for other volumes? There might be problems with drive.

replace
echo $DATA2
with
echo "$DATA2"

Yes, that's correct. Moving data from deduplicated storage pool to non-deduplicated storage pool forces reconstruction of deduped data, so in your case in copy pool there will be non-deduplicated...

Return code 18 from TSM API stands for:

DSM_RS_ABORT_NO_MEMORY 18
Verify if there is enough memory available on server where are you performing the restore and/or settings of ulimit...

tapeutil is no more bundled with drivers. It was renamed to ITDT and have to be downloaded as standalone package from IBM website and installed separately. Then just replace tapeutil with itdt and...

vStorage backup server communication with VMware datastores is based on settings vmvstortransport. The default transport selection order is san:hotadd:nbdssl:nbd....

According to the IBM documentation, a snapshot typically needs 2-6% of file system space. Highly active file systems may require around 15% of space. (source:...

I assume the retrieve operations are not performed during night. So in the evening run:
step 1: update volume /dev/rtsmstglv6 access=readonly
step 2: move data /dev/rtsmstglv6
step 3: cancel the...

1024 is maximum number of tape devices on AIX which can be using Atape drivers

Atape driver is used for:
1. IBM Virtualization Engine TS7520
2. IBM Virtualization Engine TS7650
3. IBM System...

Check physical library whether the volume is/is not present - webgui, tapeutils, ...
q volume T05631 f=d
might show location (if set to Offsite)

If you run only incremental backups it can happens that you will end up having i.e. data from monday on one tape, from tuesday on another tape, from wednesday on enother tape etc and in case of...

You can use 'delete volhistory' if you are not using DRM and offsite vaulting.
Otherwise the tapes should be physically in library and after 'del volh' their status (q libvol) will be changed from...

To backup operating system Microsoft Server 2012 you need TSM Client v6.4
To backup databases on Microsoft SQL Server 2012 you need Data Protection for Databases v6.4
You need to have TSM server at...

You need at least TSM Client v6.4 to support Windows 2012 -> http://www-01.ibm.com/support/docview.wss?uid=swg21243309#TSMClientPlatforms
To have combatible versions of TSM Client vs TSM Server you...

Even on lower level...
You can have management class with exactly the same name and settings in many policy sets, i.e. in every policy set, every policy domain, every TSM server.
Only one policy...

Probably mismatch between settings in TSM server and underlying DB2
http://www-01.ibm.com/support/docview.wss?uid=swg21441744
Check if "db2 get db cfg for tsmdb1" reflect your changes in dsmserv.opt

If you want to use VSS snapshots then:
- don't let users modify too much data on disks during backup, i.e. schedule during night when there is much lower activity, if you can afford it stop...

In GUI you see creation/last modification date

Windows 7 is supported already by 5.5 client (not neccessary 6.x client but:

Windows 7, all editions (except Automated System Recovery (ASR)), all SPs supported. Client level 5.5.2.12 or higher...

q act s=BACKUPPOOL
q act s="update stg"
q act s="PROCESS: 31403"
and look what/who updated the stg pool

Error/warning messages occured during processing are logged in your dsmerror.log file including timestamp.

Probably your drives were not correctly recognized server with storage agent. Here is explanation for AIX "error numbers" you copied from actlog:
NXIO 6 No such device or address
BADF 9 Bad...

don't define / delete paths from TSM server to drives, leave only paths from storage agent to drives.

Is the vcenter running backup proxy? If yes, there are some issues while using backup vm issued against backup proxy server, i.e. backing up itself.

maximum txnbytelimit can be 2 GB, your setup propose for 10 GB O.o (quite big transaction, uh...)
ad memory allocation - 10 gb is still way too much, see first point

start by separating DB2 logs from data, create stg pool for logs (can be tape or disk->tape)

What is utilization of those filesystems? Are they full/empty?
Image backup doesn't transfer "empty" space.

you can simply "refresh" (only) scheduler using kill

ps -ef|grep "dsmc sched"
find the PID of process, ie 1234
as root issue command:
kill -HUP 1234

But first make sure there is no scheduled...

a) checkout LTO4 tapes manually via GUI into bulk
b) checkout libvol <libname> vollist=...L4,...L4 remove=bulk checklabel=no

reassign those LTO4 in bulk to LTO4 library.

From TSM Admin guide:

The process for selecting files to migrate is based on the space
consumed by a client node's files and on the setting for migration delay.
The server selects the files to...

Try to open dsmc with parameter -optfile=..\TDPSQL\dsm.opt (pointing to that TDPSQL opt file) and run query inclexcl to get list of included/excluded patterns.
It will also tell you on behalf of...

- after retention is over file has to be "expired" by expiration process (should be part of daily scripts)
- see first point. If file is stored on disk pool, file is deleted. If file is stored on...

No space in destination. Check maximum allowed scratch tapes (if tape pool)

if it doens't work move (physically) the volume out of library into I/O slots (bulk) and run
checkin IBM3494-05A search=bulk vollist=C00636 status=private

You need to restart TSM scheduler in order to reflect new changes in mounted filesystems.

If you have automated library with barcode scanner you can:
checkin IBM3494-05A search=yes vollist=C00636 checklabel=barcode

Backups under 1 node:
- Correct approach would be to define database aliases for db.
ie
PRD_MONTH, PRD_YEAR pointing to same database PRD
- Then you can backup them as different databases and...