<?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 Re: create image locally then scp to ignite server in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/create-image-locally-then-scp-to-ignite-server/m-p/4197844#M503485</link>
    <description>This was my intention really - to leave NFS there, and configured, but only enable it when needed... this means that in the event I need to recover (unlikely I hope) I can connect the two servers locally via some switch configuration for the duration of the restore.&lt;BR /&gt;&lt;BR /&gt;I am not sure of how to create the image locally... I cant use make_net_recovery as it expects NFS, but is there any alternative to just create the image to a local directory?</description>
    <pubDate>Wed, 14 May 2008 18:21:23 GMT</pubDate>
    <dc:creator>Richard I Curtis</dc:creator>
    <dc:date>2008-05-14T18:21:23Z</dc:date>
    <item>
      <title>create image locally then scp to ignite server</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/create-image-locally-then-scp-to-ignite-server/m-p/4197842#M503483</link>
      <description>We have a policy which prohibits NFS being running all the time...so I am trying to look for a workable alternative for creating weekly ignite images.&lt;BR /&gt;&lt;BR /&gt;We dont have local tape drives, but is there a way to essentially "stage" the archive locally, so we can then scp it to the ignite server?  That way, I can leave tftp, bootp and nfs disabled except when I need to do a build or a recovery...&lt;BR /&gt;&lt;BR /&gt;Or any other method of taking and restoring images without NFS?</description>
      <pubDate>Wed, 14 May 2008 17:26:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/create-image-locally-then-scp-to-ignite-server/m-p/4197842#M503483</guid>
      <dc:creator>Richard I Curtis</dc:creator>
      <dc:date>2008-05-14T17:26:04Z</dc:date>
    </item>
    <item>
      <title>Re: create image locally then scp to ignite server</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/create-image-locally-then-scp-to-ignite-server/m-p/4197843#M503484</link>
      <description>Shalom,&lt;BR /&gt;&lt;BR /&gt;Without NFS, there will be no make_net_recovery.&lt;BR /&gt;&lt;BR /&gt;You will have to make recovery images to local disk and then scp them to the central ignite server.&lt;BR /&gt;&lt;BR /&gt;Then you are kind of dead because recovery of the system requires an image on an NFS server.&lt;BR /&gt;&lt;BR /&gt;The alternative is to get a high capacity, mobile tape drive, an ultruim and do your ignite backups make_tape_recovery&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Wed, 14 May 2008 17:42:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/create-image-locally-then-scp-to-ignite-server/m-p/4197843#M503484</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2008-05-14T17:42:39Z</dc:date>
    </item>
    <item>
      <title>Re: create image locally then scp to ignite server</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/create-image-locally-then-scp-to-ignite-server/m-p/4197844#M503485</link>
      <description>This was my intention really - to leave NFS there, and configured, but only enable it when needed... this means that in the event I need to recover (unlikely I hope) I can connect the two servers locally via some switch configuration for the duration of the restore.&lt;BR /&gt;&lt;BR /&gt;I am not sure of how to create the image locally... I cant use make_net_recovery as it expects NFS, but is there any alternative to just create the image to a local directory?</description>
      <pubDate>Wed, 14 May 2008 18:21:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/create-image-locally-then-scp-to-ignite-server/m-p/4197844#M503485</guid>
      <dc:creator>Richard I Curtis</dc:creator>
      <dc:date>2008-05-14T18:21:23Z</dc:date>
    </item>
    <item>
      <title>Re: create image locally then scp to ignite server</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/create-image-locally-then-scp-to-ignite-server/m-p/4197845#M503486</link>
      <description>If you can run NFS for recovery, why don't you try and get permission to bring up NFS for the make_net_recovery job(s).  Someone has already approved opening up security for short periods.&lt;BR /&gt;&lt;BR /&gt;Once you have the timing down, you can bring up NFS using cron just before you kick off a make_net_recovery job and then take it down shortly after it is supposed to be completed. Give yourself a little slack time to account for growth. &lt;BR /&gt;&lt;BR /&gt;Just a thought. &lt;BR /&gt;&lt;BR /&gt;Rob...</description>
      <pubDate>Thu, 15 May 2008 19:34:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/create-image-locally-then-scp-to-ignite-server/m-p/4197845#M503486</guid>
      <dc:creator>Robin T. Slotten</dc:creator>
      <dc:date>2008-05-15T19:34:31Z</dc:date>
    </item>
    <item>
      <title>Re: create image locally then scp to ignite server</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/create-image-locally-then-scp-to-ignite-server/m-p/4197846#M503487</link>
      <description>I think that is going to be my best option for the minute.  Once I have it all in and working (the priority), I will experiment and see if I can create an image locally and script scp etc.&lt;BR /&gt;&lt;BR /&gt;Cheers for the suggestion!</description>
      <pubDate>Fri, 16 May 2008 17:54:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/create-image-locally-then-scp-to-ignite-server/m-p/4197846#M503487</guid>
      <dc:creator>Richard I Curtis</dc:creator>
      <dc:date>2008-05-16T17:54:35Z</dc:date>
    </item>
  </channel>
</rss>

