Skip to content

Commit

Permalink
add on enew blog
Browse files Browse the repository at this point in the history
  • Loading branch information
lomolomo2 committed Nov 3, 2024
1 parent 28e8659 commit 7ce183d
Showing 1 changed file with 82 additions and 0 deletions.
82 changes: 82 additions & 0 deletions content/blog/migrate_from_pi_win.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,82 @@

+++
title = "Simple and Fast Data Migration and Storage Expansion"
tags = ["WD", "MyCloud", "Redundancy"]
categories = ["BLOG"]
date = "2023-03-02T13:43:40"
banner = "/img/blog/migrate_from_pi_win/migrate_pi_win.jpg"
+++

**Simple and Fast Data Migration and Storage Expansion**

Recently, a user encountered an issue where their original storage disk was full and wanted to directly migrate data from their existing PI server to a Windows server while expanding the storage disk. Let's explore the fastest way to migrate and expand data, and this guide can also be used for data recovery. This article uses Windows as an example, but the process is similar for other platforms.

<!--more-->

<div align="center">
<p class="screenshot">
<img width="50%" src="/img/blog/migrate_from_pi_win/migrate_pi_win.jpg">
</p>
</div>

Contents
=================
- [Contents](#contents)
- [Step 1: Install Windows Lomorage Photo Assistant](#step-1-install-windows-lomorage-photo-assistant)
- [Step 2: Copy Data](#step-2-copy-data)
- [Step 3: Modify the `home_dir` Field in the `user` Table of the `assets.db`](#step-3-modify-the-home_dir-field-in-the-user-table-of-the-assetsdb)
- [3.1 Download Auxiliary Tool](#31-download-auxiliary-tool)
- [3.2 Stop Photo Assistant and Copy the Modified `assets.db` to the Default Installation Location:](#32-stop-photo-assistant-and-copy-the-modified-assetsdb-to-the-default-installation-location)
- [3.3 Restart Photo Assistant to Complete Data Migration, No More Worries About Full Disks!](#33-restart-photo-assistant-to-complete-data-migration-no-more-worries-about-full-disks)

# Step 1: Install Windows Lomorage Photo Assistant

Go directly to [Lomorage](https://lomorage.com) to download the Windows version of the Photo Assistant and install it with the default settings.

# Step 2: Copy Data

Since the original storage disk was full, User A chose a new **10TB** large hard disk and transferred the data from the old storage disk to the new disk.

The new folder in new disk is:

**d:\imagebk**

Ensure the folder under **d:\imagebk** same like as below

```
d:\imagebk
|-- test
|-- user_name
|-- user_name2
|-- assets.db
```


# Step 3: Modify the `home_dir` Field in the `user` Table of the `assets.db`

Now we need to point the Lomorage photo assistant to the new storage disk. You can do this by modifying the `home_dir` field in the `user` table in the `assets.db` database.

## 3.1 Download Auxiliary Tool

Download a database management tool (like `sqlitebrowser`) to help edit the `assets.db` database file.




<div align="center">
<p class="screenshoot">
<img width="100%" src="/img/blog/migrate_from_pi_win/assets_db_zh.png">
</p>
</div>

## 3.2 Stop Photo Assistant and Copy the Modified `assets.db` to the Default Installation Location:

**> c:\Users\\%username%\AppData\Local\lomoware\var\assets.db**


Once you have modified the `home_dir` field, stop the Lomorage Photo Assistant and replace the old `assets.db` with the newly modified one at the default installation path. The default location is usually in the `Lomorage` folder under your user directory.

## 3.3 Restart Photo Assistant to Complete Data Migration, No More Worries About Full Disks!

After copying the modified `assets.db`, restart the Lomorage Photo Assistant. At this point, your data migration is complete, and the storage limit issue has been resolved!

0 comments on commit 7ce183d

Please sign in to comment.