<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:clearspace="http://www.jivesoftware.com/xmlns/clearspace/rss" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:opensearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>Availability : Proven Practice: Integrating Tivoli Storage Manager 5.5 with VCB 1.1 : Comments</title>
    <link>http://viops.vmware.com/home/docs/DOC-1124#comments</link>
    <description>Comments on : Proven Practice: Integrating Tivoli Storage Manager 5.5 with VCB 1.1</description>
    <language>en</language>
    <pubDate>Fri, 09 Jan 2009 11:42:40 GMT</pubDate>
    <generator>Clearspace 2.0.8 (http://jivesoftware.com/products/clearspace/)</generator>
    <dc:date>2009-01-09T11:42:40Z</dc:date>
    <dc:language>en</dc:language>
    <item>
      <title>RE: Proven Practice: Integrating Tivoli Storage Manager 5.5 with VCB 1.1</title>
      <link>http://viops.vmware.com/home/docs/DOC-1124#comments-1395</link>
      <description>&lt;div class='jive-rendered-content'&gt;&lt;p&gt;Hi Chris,&lt;/p&gt;&lt;p&gt;If you are doing file-level backups, you also can, with TSM 5.5, integrate it with VCB without TSM VCB Integration Modules.&lt;/p&gt;&lt;p&gt;You have 4 new parameters in TSM BAClient dsm.opt which are VMCHOST, VMCUSER, VMCPWD, VMLIST, and a new dsmc command option, "backup vm".&lt;/p&gt;&lt;p&gt;One advantage to me is, you create a tsm node for each virtual machine you want to backup, like in a physical environment, then you grant authority to the proxy node (VCB/TSM). When you backup, the tsm client parses a command that invokes VCB, all mount points to the VM are mounted in C:/mnt and the backup is done. Now the advantage, each filespace, you have backed up, belonging to each VM are under is tsm node and not in the VCB tsm node. If you want to restore just a single file, and if you have installed and only configured dsm.opt, you have the possibility to restore directly in the VM. One other thing is, if you decommission a VM and want to delete all its backups, you just have to delete its own filespaces.&lt;/p&gt;&lt;/div&gt;</description>
      <pubDate>Fri, 09 Jan 2009 11:42:40 GMT</pubDate>
      <author>mcfm</author>
      <guid>http://viops.vmware.com/home/docs/DOC-1124#comments-1395</guid>
      <dc:date>2009-01-09T11:42:40Z</dc:date>
      <clearspace:dateToText>10 months, 2 weeks ago</clearspace:dateToText>
    </item>
    <item>
      <title>RE: Proven Practice: Integrating Tivoli Storage Manager 5.5 with VCB 1.1</title>
      <link>http://viops.vmware.com/home/docs/DOC-1124#comments-1396</link>
      <description>&lt;div class='jive-rendered-content'&gt;&lt;p&gt;@mcfm, that is a great comment - do you think you might be able to write your practice up?  Just a series of steps... you don't &lt;em&gt;have&lt;/em&gt; to include screenshots, but it helps...  perhaps you have this in a word doc or something, which you could attach to a new viops doc?  &lt;/p&gt;&lt;/div&gt;</description>
      <pubDate>Fri, 09 Jan 2009 15:20:50 GMT</pubDate>
      <author>schambers</author>
      <guid>http://viops.vmware.com/home/docs/DOC-1124#comments-1396</guid>
      <dc:date>2009-01-09T15:20:50Z</dc:date>
      <clearspace:dateToText>10 months, 2 weeks ago</clearspace:dateToText>
    </item>
    <item>
      <title>RE: Proven Practice: Integrating Tivoli Storage Manager 5.5 with VCB 1.1</title>
      <link>http://viops.vmware.com/home/docs/DOC-1124#comments-1397</link>
      <description>&lt;div class='jive-rendered-content'&gt;&lt;p&gt;Steve I don't have that documented, but I will manage that.&lt;/p&gt;&lt;/div&gt;</description>
      <pubDate>Fri, 09 Jan 2009 18:05:29 GMT</pubDate>
      <author>mcfm</author>
      <guid>http://viops.vmware.com/home/docs/DOC-1124#comments-1397</guid>
      <dc:date>2009-01-09T18:05:29Z</dc:date>
      <clearspace:dateToText>10 months, 2 weeks ago</clearspace:dateToText>
    </item>
    <item>
      <title>RE: Proven Practice: Integrating Tivoli Storage Manager 5.5 with VCB 1.1</title>
      <link>http://viops.vmware.com/home/docs/DOC-1124#comments-1403</link>
      <description>&lt;div class='jive-rendered-content'&gt;&lt;p&gt;Well boy's what fantastic timing, as a company managing multiple VMware installations that are currently backed up with CA ARCServe, which is causing us problems and we are looking at making use of Tivoli.&lt;/p&gt;&lt;p&gt;I have a lot of experience with backup platforms as would be REALLY keen to keep track of this and make use of the excellent document you have posted here.&lt;/p&gt;&lt;p&gt;I am just waiting for our IBM man to get in touch about some eval software, and so am just gathering information for my trial install.&lt;/p&gt;&lt;p&gt;Please keen me up-to-date with any ideas and I’d love any tips etc.&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;Thanks&lt;/p&gt;&lt;p&gt;Again&lt;/p&gt;&lt;p&gt;Steve&lt;/p&gt;&lt;p&gt;&lt;img dynsrc="#" href="#" lowsrc="#" src="http://viops.vmware.com/home/images/emoticons/wink.gif"/&gt;&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;/div&gt;</description>
      <pubDate>Fri, 16 Jan 2009 15:13:52 GMT</pubDate>
      <author>Steve</author>
      <guid>http://viops.vmware.com/home/docs/DOC-1124#comments-1403</guid>
      <dc:date>2009-01-16T15:13:52Z</dc:date>
      <clearspace:dateToText>10 months, 1 week ago</clearspace:dateToText>
    </item>
    <item>
      <title>RE: Proven Practice: Integrating Tivoli Storage Manager 5.5 with VCB 1.1</title>
      <link>http://viops.vmware.com/home/docs/DOC-1124#comments-1436</link>
      <description>&lt;div class='jive-rendered-content'&gt;&lt;p&gt;Thanks Miguel for the great explanation. &lt;/p&gt;&lt;p&gt;I am preparing to my first installaton. Besides your explanation, there are very few comments on the topic in the web. I've found only:&lt;/p&gt;&lt;p&gt;   1. a notice that options that you mentioned (VMCHost, VM.. ) are used by the TSM to automatically pass virtualfsname, virtualhostname etc so that the backup/restore is more seamless. Backup vm also runs transparently for us all pre and post schedules related to snapshots . Correct?&lt;/p&gt;&lt;p&gt;   2. a notice that the c:\mnt is hardcoded regardless of any integration stuff like config.js etc.&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;I am especially curious what scripts are called by 'dsmc backup vm' command, and how to pass parameters to vcbmounter, what are all config files in the end to end process, how to call also VM tools for applications quiescing etc.&lt;/p&gt;&lt;p&gt;Another question would be how to dynamically call a group VMs (group could be defined by IP alias? or could be 'all' VMs?)&lt;/p&gt;&lt;p&gt;Looking forward to any posts..&lt;/p&gt;&lt;/div&gt;</description>
      <pubDate>Fri, 30 Jan 2009 01:05:45 GMT</pubDate>
      <author>barvos</author>
      <guid>http://viops.vmware.com/home/docs/DOC-1124#comments-1436</guid>
      <dc:date>2009-01-30T01:05:45Z</dc:date>
      <clearspace:dateToText>9 months, 3 weeks ago</clearspace:dateToText>
    </item>
  </channel>
</rss>

