<?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 Recommended Backup/Storage Practices for Small GIS Teams in Data Management Questions</title>
    <link>https://community.esri.com/t5/data-management-questions/recommended-backup-storage-practices-for-small-gis/m-p/1705765#M45868</link>
    <description>&lt;P&gt;&lt;SPAN&gt;Hi! I’m looking for some advice/recommendations on practical ArcGIS Pro project storage and backup workflows for a smaller planning/GIS environment.&lt;BR /&gt;&lt;BR /&gt;I'm part of a smaller planning firm using ArcGIS Pro with mostly sequential workflows rather than a large multi-editor enterprise GIS setup. I’m currently trying to balance a few things at once:&lt;/SPAN&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;SPAN&gt;maintaining good performance for larger geoprocessing workflows,&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;minimizing file geodatabase corruption/sync conflicts,&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;and still having reliable backup/version recovery practices in place.&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;SPAN&gt;I know many people use OneDrive/SharePoint with GIS projects, but I’ve also seen frequent warnings about actively syncing ArcGIS Pro projects and file geodatabases. Internally, concerns were raised particularly around sync conflicts and long-term stability with geodatabases/toolboxes.&lt;BR /&gt;&lt;BR /&gt;At this point, the approach that seems most realistic for us is:&lt;/SPAN&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;SPAN&gt;keeping active GIS projects local or on external storage,&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;using SharePoint more as an archive/reference location,&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;and implementing a separate backup/versioning workflow.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;SPAN&gt;&lt;BR /&gt;One thing I came across was Windows File History for periodic versioned backups to an external drive. I was curious whether anyone here has used Windows File History successfully with ArcGIS Pro projects/file geodatabases, or whether there are other lightweight backup approaches you would recommend for a smaller GIS team without a dedicated enterprise GIS server environment. I’m not necessarily looking for a full enterprise GIS/database setup right now. Mostly trying to find something practical, stable, maintainable, and realistic for a smaller firm environment. Would definitely appreciate hearing what has worked well for others, what caused issues, and any lessons learned around ArcGIS Pro storage/backup practices.&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 02 Jun 2026 20:01:58 GMT</pubDate>
    <dc:creator>JazPritcClarion</dc:creator>
    <dc:date>2026-06-02T20:01:58Z</dc:date>
    <item>
      <title>Recommended Backup/Storage Practices for Small GIS Teams</title>
      <link>https://community.esri.com/t5/data-management-questions/recommended-backup-storage-practices-for-small-gis/m-p/1705765#M45868</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Hi! I’m looking for some advice/recommendations on practical ArcGIS Pro project storage and backup workflows for a smaller planning/GIS environment.&lt;BR /&gt;&lt;BR /&gt;I'm part of a smaller planning firm using ArcGIS Pro with mostly sequential workflows rather than a large multi-editor enterprise GIS setup. I’m currently trying to balance a few things at once:&lt;/SPAN&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;SPAN&gt;maintaining good performance for larger geoprocessing workflows,&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;minimizing file geodatabase corruption/sync conflicts,&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;and still having reliable backup/version recovery practices in place.&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;SPAN&gt;I know many people use OneDrive/SharePoint with GIS projects, but I’ve also seen frequent warnings about actively syncing ArcGIS Pro projects and file geodatabases. Internally, concerns were raised particularly around sync conflicts and long-term stability with geodatabases/toolboxes.&lt;BR /&gt;&lt;BR /&gt;At this point, the approach that seems most realistic for us is:&lt;/SPAN&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;SPAN&gt;keeping active GIS projects local or on external storage,&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;using SharePoint more as an archive/reference location,&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;and implementing a separate backup/versioning workflow.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;SPAN&gt;&lt;BR /&gt;One thing I came across was Windows File History for periodic versioned backups to an external drive. I was curious whether anyone here has used Windows File History successfully with ArcGIS Pro projects/file geodatabases, or whether there are other lightweight backup approaches you would recommend for a smaller GIS team without a dedicated enterprise GIS server environment. I’m not necessarily looking for a full enterprise GIS/database setup right now. Mostly trying to find something practical, stable, maintainable, and realistic for a smaller firm environment. Would definitely appreciate hearing what has worked well for others, what caused issues, and any lessons learned around ArcGIS Pro storage/backup practices.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 02 Jun 2026 20:01:58 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/recommended-backup-storage-practices-for-small-gis/m-p/1705765#M45868</guid>
      <dc:creator>JazPritcClarion</dc:creator>
      <dc:date>2026-06-02T20:01:58Z</dc:date>
    </item>
    <item>
      <title>Re: Recommended Backup/Storage Practices for Small GIS Teams</title>
      <link>https://community.esri.com/t5/data-management-questions/recommended-backup-storage-practices-for-small-gis/m-p/1705799#M45869</link>
      <description>&lt;P&gt;One Drive and the like are still a ways off for complete integration with Pro (near term column)&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.esri.com/t5/arcgis-pro-documents/arcgis-pro-roadmap-may-2026/ta-p/1701657?aduc=Organic&amp;amp;aduca=CRA_ArcGIS_Pro&amp;amp;cid=698c92e01d39d02ddde0d213_ProRoadmap&amp;amp;sf_id=701UU00000VzpWKYAZ&amp;amp;utm_activity=arcgis_pro_road_map&amp;amp;utm_campaign=CRA_ArcGIS_Pro&amp;amp;utm_id=701UU00000VzpWKYAZ&amp;amp;utm_source=Organic" target="_blank"&gt;ArcGIS Pro Roadmap - May 2026&lt;/A&gt;&lt;/P&gt;&lt;P&gt;So other than providing a static backup of your work, there are still many threads about avoiding its use for active data access.&lt;/P&gt;&lt;P&gt;Local storage and processing&amp;nbsp; is always the best unless you have multiple people that have to edit/add data at the same time.&lt;/P&gt;</description>
      <pubDate>Tue, 02 Jun 2026 21:46:01 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/recommended-backup-storage-practices-for-small-gis/m-p/1705799#M45869</guid>
      <dc:creator>DanPatterson</dc:creator>
      <dc:date>2026-06-02T21:46:01Z</dc:date>
    </item>
  </channel>
</rss>

