<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Backing up Multiple Virtual Connect Configurations in BladeSystem - General</title>
    <link>https://community.hpe.com/t5/bladesystem-general/backing-up-multiple-virtual-connect-configurations/m-p/5921287#M31796</link>
    <description>&lt;P&gt;&lt;STRONG&gt;Question from Reginald's customer:&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;************&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Customer was wondering what is HP’s best practice recommendation or method of backing up multiple VC configurations across large population of multiple enclosures/domains? We talked to them about using the CLI interface/scripts and were not too thrilled on having to write their own procedures. The customer indicated that they’ve automated this process for their Cisco switches using tools like SolarWinds. Can we use a tool like SolarWinds to backup our enclosure/domain configurations and if not what is the recommended process?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;*************&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Input from Steve:&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;****************&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Reggie,&amp;nbsp; A process I have used with my customers is to use VCSU to back up the domain config.&amp;nbsp; It will create a backup file for each domain.&amp;nbsp; The backup file name also contains the date, so multiple backups can be stored in the same directory.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Example;&lt;/P&gt;
&lt;P&gt;vcsu -a configbackup -i 192.168.0.100 -u Administrator -p password –vcu Administrator -vcp password&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Create a batch file with one line per VC domain.&lt;/P&gt;
&lt;P&gt;vcsu -a configbackup -i 192.168.0.100 -u Administrator -p password –vcu Administrator -vcp password&lt;/P&gt;
&lt;P&gt;vcsu -a configbackup -i 192.168.0.101 -u Administrator -p password –vcu Administrator -vcp password&lt;/P&gt;
&lt;P&gt;vcsu -a configbackup -i 192.168.0.102 -u Administrator -p password –vcu Administrator -vcp password&lt;/P&gt;
&lt;P&gt;vcsu -a configbackup -i 192.168.0.103 -u Administrator -p password –vcu Administrator -vcp password&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Then see if Solar Winds can schedule and launch the batch file.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Also, if they have SIM, it could likely launch the back up.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;*************&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Other comments or suggestions?&lt;/STRONG&gt;&lt;/P&gt;</description>
    <pubDate>Thu, 03 Jan 2013 19:48:38 GMT</pubDate>
    <dc:creator>chuckk281</dc:creator>
    <dc:date>2013-01-03T19:48:38Z</dc:date>
    <item>
      <title>Backing up Multiple Virtual Connect Configurations</title>
      <link>https://community.hpe.com/t5/bladesystem-general/backing-up-multiple-virtual-connect-configurations/m-p/5921287#M31796</link>
      <description>&lt;P&gt;&lt;STRONG&gt;Question from Reginald's customer:&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;************&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Customer was wondering what is HP’s best practice recommendation or method of backing up multiple VC configurations across large population of multiple enclosures/domains? We talked to them about using the CLI interface/scripts and were not too thrilled on having to write their own procedures. The customer indicated that they’ve automated this process for their Cisco switches using tools like SolarWinds. Can we use a tool like SolarWinds to backup our enclosure/domain configurations and if not what is the recommended process?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;*************&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Input from Steve:&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;****************&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Reggie,&amp;nbsp; A process I have used with my customers is to use VCSU to back up the domain config.&amp;nbsp; It will create a backup file for each domain.&amp;nbsp; The backup file name also contains the date, so multiple backups can be stored in the same directory.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Example;&lt;/P&gt;
&lt;P&gt;vcsu -a configbackup -i 192.168.0.100 -u Administrator -p password –vcu Administrator -vcp password&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Create a batch file with one line per VC domain.&lt;/P&gt;
&lt;P&gt;vcsu -a configbackup -i 192.168.0.100 -u Administrator -p password –vcu Administrator -vcp password&lt;/P&gt;
&lt;P&gt;vcsu -a configbackup -i 192.168.0.101 -u Administrator -p password –vcu Administrator -vcp password&lt;/P&gt;
&lt;P&gt;vcsu -a configbackup -i 192.168.0.102 -u Administrator -p password –vcu Administrator -vcp password&lt;/P&gt;
&lt;P&gt;vcsu -a configbackup -i 192.168.0.103 -u Administrator -p password –vcu Administrator -vcp password&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Then see if Solar Winds can schedule and launch the batch file.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Also, if they have SIM, it could likely launch the back up.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;*************&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Other comments or suggestions?&lt;/STRONG&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 03 Jan 2013 19:48:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/backing-up-multiple-virtual-connect-configurations/m-p/5921287#M31796</guid>
      <dc:creator>chuckk281</dc:creator>
      <dc:date>2013-01-03T19:48:38Z</dc:date>
    </item>
  </channel>
</rss>

