PG Move
- 📂 [Click Here] - Google G-Suite (Unlimited Hard Drive Space & Storage)
- 📂 [Click Here] - Top Performance NewsHost! - Blitz Members Receive a 58% Discount
Reference Shortcut - http://pgmove.pgblitz.com | Discord ( !pgmove )
Table of Contents
- Intro
- PG Move Advantages & Disadvantages
- PG Move - UnEncrypted
- PG Move - Encrypted Setup
- How it works
PG move was established as the transport system that was originally built for PlexGuide. PG Move provides you the ability to transfer your files in the most simplistic manner. PG Move no longer requires you to edit your rclone config for its setup. For the encrypted edition, the user no longer has to configure gcrypt. All of this is automated through PG Clone.
Advantages of PG Move over PG Blitz:
- Easy setup
- Can utilize BW to throttle upload rate
- Only utilizes your primary Google Drive (gdrive)
Disadvantages of PG Move over PG Blitz:
- Max Upload of 750GB per day
- Normally requires 10MB throttle to prevent upload ban
The setup for this process is easy.
- Have the Google OAuth Keys generated and saved!
- Select PG Move Unencrypted
- Goto PG Clone - OAuth & Mounts
- Set the Client ID
- Set the Secret ID
- Select GDrive under the rclone configuration and validate the link
- Exit to the main menu
- Select a Throttle Limit (10MB is generally safe to prevent an upload ban)
- Select Deploy
The setup for this process is easy.
- Have the Google OAuth Keys generated and saved!
- Select PG Move Encrypted
- Goto PG Clone - OAuth & Mounts
- Set the Client ID
- Set the Secret ID
- Set a Primary Password & SALT Password
- Select GDrive under the rclone configuration and validate the link
- Exit to the main menu
- Select a Throttle Limit (10MB is generally safe to prevent an upload ban)
- Select Deploy
- When radarr/lidarr/sonarr imports your downloads from
/mnt/downloads/_downloader_/_category_/...it reads the download mappings and instead of looking for/mnt/downloads/_downloader_/_category_/...it looks for/mnt/unionfs/_downloader_/_category_/.... So at this point, it's accessing the files inside the merger. - Now Arr will do a hardlink/mv operation to rename and organize the media. Arr will think it's putting the files in
/mnt/unionfs/_category_/..., but it's actually putting them into/mnt/downloads/_category_/... - At this point your files are imported and renamed, they are accessible at
/mnt/unionfs/_category_/... - The move script runs and ignores any "known downloader" folders inside
/mnt/downloads, and moves everything it doesn't ignore (like/mnt/downloads/_category_) to/mnt/movefor uploading. - Now your files are inside
/mnt/movefor uploading, runpgmoveto see the status.
-- Arr has to organize the files, To hardlink inside mergerfs, it requires everything being inside the merger (aka /mnt/unionfs) for rapid importing to work. The downloader mappers tell arr to look in /mnt/unionfs/nzbget so then it does a mv. But underlying, mergerfs will do a rename in the real location, which is /mnt/downloads. There isn't a way to force that rename operation to occur in /mnt/move instead or we would just do that, this is a behavior we cannot change.
Files that exist in /mnt/downloads/_category_ will be moved for uploading.
Move runs in a batch, it grabs everything ready at that time and uploads it. It will not move other files in the background while actively uploading!
Arr however will continue to import and organize the next set of files. So typically files sit in /mnt/downloads/_category_ for 0-45m (depending on active upload).
During this entire process, once arr does the import, the file stays at /mnt/unionfs/_category_/[...]
this is so plex can scan it and have it available without first waiting for it to be uploaded.
📂 Click Here - NZB's from USENET Server - PG Members Receive a 60% Discount
