<?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 Mounting snapshots in General Topics</title>
    <link>https://community.checkpoint.com/t5/General-Topics/Mounting-snapshots/m-p/146129#M25708</link>
    <description>&lt;P&gt;I recently had the need to get a file from a snapshot on a device which had very little local storage. Rather than using the process from&amp;nbsp;&lt;SPAN&gt;&lt;A href="https://community.checkpoint.com/t5/Security-Gateways/White-Paper-Extracting-a-file-from-a-GAIA-Snapshot/m-p/52520#M3982" target="_self"&gt;White Paper - Extracting a file from a GAIA Snapshot&lt;/A&gt;, I decided to mount the snapshot directly and get the file from there. Thought others here might be interested in the process.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;First, you need to find the snapshot's node in the /dev virtual filesystem. Use 'lvdisplay'. Each logical volume will have an entry like this:&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;[Expert@DallasSA]# lvdisplay 
...
  --- Logical volume ---
  LV Path                /dev/vg_splat/lv_DemoSnap
  LV Name                lv_DemoSnap
  VG Name                vg_splat
  LV UUID                7TbELE-hYY0-9fLi-1F3y-K3MN-0AlH-octYt7
  LV Write Access        read/write
  LV Creation host, time DallasSA, 2022-04-12 16:16:55 +0000
  LV Status              available
  # open                 0
  LV Size                14.44 GiB
  Current LE             462
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           253:4
...&lt;/LI-CODE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Create a directory, and mount the snapshot:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;[Expert@DallasSA]# mkdir /mnt/snapshot

[Expert@DallasSA]# ls -lh /mnt/snapshot
total 0

[Expert@DallasSA]# mount -o ro /dev/vg_splat/lv_DemoSnap /mnt/snapshot

[Expert@DallasSA]# mount
/dev/mapper/vg_splat-lv_current on / type xfs (rw,inode32)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
/dev/sda1 on /boot type ext3 (rw)
tmpfs on /dev/shm type tmpfs (rw)
/dev/mapper/vg_splat-lv_log on /var/log type xfs (rw,inode32)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
cgroup on /sys/fs/cgroup type tmpfs (rw,uid=0,gid=0,mode=0755)
/dev/mapper/vg_splat-lv_DemoSnap on /mnt/snapshot type xfs (ro)

[Expert@DallasSA]# ls -lh /mnt/snapshot/
total 48M
-rw-rw----  1 admin root    0 Nov 20 15:33 1
-rw-r--r--  1 admin root    0 Dec 29 16:07 DEBUG
drwxr-xr-x  2 admin root   85 Nov 20 15:17 DOCS
-rw-r--r--  1 admin root  542 Oct 17  2020 License.txt
lrwxrwxrwx  1 admin root    7 Apr 12 16:17 bin -&amp;gt; usr/bin
...&lt;/LI-CODE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The '-o ro' argument in the mount command makes it read-only so you don't accidentally change something in the snapshot. With that, you now have read-only access to the whole system as it was when the snapshot was taken.&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Edit&lt;/STRONG&gt;: Added some newlines between the output of one command and the next command to make the output easier to follow visually.&lt;/P&gt;</description>
    <pubDate>Mon, 18 Apr 2022 17:43:46 GMT</pubDate>
    <dc:creator>Bob_Zimmerman</dc:creator>
    <dc:date>2022-04-18T17:43:46Z</dc:date>
    <item>
      <title>Mounting snapshots</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Mounting-snapshots/m-p/146129#M25708</link>
      <description>&lt;P&gt;I recently had the need to get a file from a snapshot on a device which had very little local storage. Rather than using the process from&amp;nbsp;&lt;SPAN&gt;&lt;A href="https://community.checkpoint.com/t5/Security-Gateways/White-Paper-Extracting-a-file-from-a-GAIA-Snapshot/m-p/52520#M3982" target="_self"&gt;White Paper - Extracting a file from a GAIA Snapshot&lt;/A&gt;, I decided to mount the snapshot directly and get the file from there. Thought others here might be interested in the process.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;First, you need to find the snapshot's node in the /dev virtual filesystem. Use 'lvdisplay'. Each logical volume will have an entry like this:&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;[Expert@DallasSA]# lvdisplay 
...
  --- Logical volume ---
  LV Path                /dev/vg_splat/lv_DemoSnap
  LV Name                lv_DemoSnap
  VG Name                vg_splat
  LV UUID                7TbELE-hYY0-9fLi-1F3y-K3MN-0AlH-octYt7
  LV Write Access        read/write
  LV Creation host, time DallasSA, 2022-04-12 16:16:55 +0000
  LV Status              available
  # open                 0
  LV Size                14.44 GiB
  Current LE             462
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           253:4
...&lt;/LI-CODE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Create a directory, and mount the snapshot:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;[Expert@DallasSA]# mkdir /mnt/snapshot

[Expert@DallasSA]# ls -lh /mnt/snapshot
total 0

[Expert@DallasSA]# mount -o ro /dev/vg_splat/lv_DemoSnap /mnt/snapshot

[Expert@DallasSA]# mount
/dev/mapper/vg_splat-lv_current on / type xfs (rw,inode32)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
/dev/sda1 on /boot type ext3 (rw)
tmpfs on /dev/shm type tmpfs (rw)
/dev/mapper/vg_splat-lv_log on /var/log type xfs (rw,inode32)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
cgroup on /sys/fs/cgroup type tmpfs (rw,uid=0,gid=0,mode=0755)
/dev/mapper/vg_splat-lv_DemoSnap on /mnt/snapshot type xfs (ro)

[Expert@DallasSA]# ls -lh /mnt/snapshot/
total 48M
-rw-rw----  1 admin root    0 Nov 20 15:33 1
-rw-r--r--  1 admin root    0 Dec 29 16:07 DEBUG
drwxr-xr-x  2 admin root   85 Nov 20 15:17 DOCS
-rw-r--r--  1 admin root  542 Oct 17  2020 License.txt
lrwxrwxrwx  1 admin root    7 Apr 12 16:17 bin -&amp;gt; usr/bin
...&lt;/LI-CODE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The '-o ro' argument in the mount command makes it read-only so you don't accidentally change something in the snapshot. With that, you now have read-only access to the whole system as it was when the snapshot was taken.&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Edit&lt;/STRONG&gt;: Added some newlines between the output of one command and the next command to make the output easier to follow visually.&lt;/P&gt;</description>
      <pubDate>Mon, 18 Apr 2022 17:43:46 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Mounting-snapshots/m-p/146129#M25708</guid>
      <dc:creator>Bob_Zimmerman</dc:creator>
      <dc:date>2022-04-18T17:43:46Z</dc:date>
    </item>
    <item>
      <title>Re: Mounting snapshots</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Mounting-snapshots/m-p/146318#M25726</link>
      <description>&lt;P&gt;That's a groovy tip, thanks for sharing!&lt;/P&gt;</description>
      <pubDate>Thu, 14 Apr 2022 21:59:56 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Mounting-snapshots/m-p/146318#M25726</guid>
      <dc:creator>PhoneBoy</dc:creator>
      <dc:date>2022-04-14T21:59:56Z</dc:date>
    </item>
  </channel>
</rss>

