Re: Decommision VM?

Data in filespaces gets expired. Filespaces by itself will not get removed automaticly. Op 3 okt. 2016 19:32 schreef "David Ehresman" : > >q copyg it-vme active standard > > > > PolicyPolicyMgmt Copy Version- Version- Retain Retain > > Domain

Re: disadvantages / limitations to using Exchange restores from VE backup?

Stefan, I do not use the application level backup included with TSM for VE. If we can judge its use by the number of responses to this thread, it doesn't appear many others use it either. I would strongly recommend you install it into a test environment for a month and see how both backups

TSM for VE vs VMware VDP

Anyone done a comparison of these two? We just finished upgrading our VMware environment to v6 (vrom 5.5) and were looking at installing the latest TSM for VE but with latest updates to VDP were wondering if it would be a better/easier route? -- *Zoltan Forray* TSM Software & Hardware

Re: Decommision VM?

>q copyg it-vme active standard PolicyPolicyMgmt Copy Version- Version- Retain Retain DomainSet Name Class Group s Data s DataExtraOnly NameName NameExists Deleted Versions Version - - -

Re: Decommision VM?

The "decommission vm" command is supposed to inactivate all active backups for the specified TSMVE VM.. So they should expire after the retd period for the management class. David -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Thomas

Re: Decommision VM?

could share the output for: query copygroup ???? Bests regards 2016-10-03 11:49 GMT-05:00 David Ehresman : > I decommissioned a VM on 9/1/2016. We have a 30 day retention of data. > The filespace still has not been removed even tho it is now 10/3/2016.

Re: Decommision VM?

The 30 day retention period for a specific backup copy starts when TSM discovers that the corresponding file on the client system's disk has been deleted or updated. TSM never got the opportunity to make that discovery for backup copies of the files on the client system's disk at the time of

setting up a linux datamover for tsm for ve

Ok, I am missing something obvious. Trying to set up a data mover. We are currently on client 6.4.2. Have installed the tsm client, and vmware enablement file. Still getting tsm> ba vm javatestdeploy ANS9383E Required files for VMware vStorage virtual machine backup could not be found. Run the

Decommision VM?

I decommissioned a VM on 9/1/2016. We have a 30 day retention of data. The filespace still has not been removed even tho it is now 10/3/2016. Why not? Output from a q file shows the filespace is decommissioned. Platform: TDP VMware

Re: re-initializing a tsm instance

Hey David, I went through the below steps with IBM support while testing TSM 7.1.6 Login as instance owner 1: db2stop force ipclean cd /home/tsminst1/ /opt/tivoli/tsm/server/bin/dsmserv removedb tsmdb1 2: after remove db, cleanup all your logs dir and dbdir and ensure they are clean: ls -al

Re: re-initializing a tsm instance

Hi David! If I remember correctly you have to remove all references to the existing database by using the dsmserv removedb command. This removes the database from the registry and physically removes the database files. Afterwards you have to empty the archive log and archive failover log

re-initializing a tsm instance

Is there a procedure for re-initializing a tsm instance? I want to reuse existing tsm db and log filespaces but re-initialize it as a fresh empty instance. I'm thinking I can just erase all the files in the db and log directories and then rerun the initial initialize gui. Am I missing