After the archive job completes, look at the used storage on the Synology/Fireball device and confirm your data is correctly being written.īrowse the archive index and verify you can see your archived data inside. Trigger the archive job using the plan you created in the previous step.ī5. Use ‘Manual Archiving’ to browse local or remote filesystems and select the data you wish to archive. Using the Archive Plan that you just created, archive your data. Only the Volume folders are migrated to cloud storage.ī4. Indexes, previews and meta-data will be stored within P5’s index databases and ‘Clips’ folders and remain part of the P5 installation on local storage within the installation directory. If needed, create your own index (rather than the ‘Default – Archive’ index), and configure meta-data fields and preview generation according to your requirements. Create an archive plan, selecting as Target Storage the ‘Disk Archive’ pool. Double click on each in turn, and set ‘Data Compression’ = ‘No’ for both of the drives.ī3. Visit ‘Standalone Tape Drive’ to edit the virtual tape drives. Avoiding have the P5 host needing to compress everything written to the Synology, allowed best possible write performance. An extra step is required to avoid P5 compressing data before it’s written to the Synology/Fireball device. Allow P5 to use ‘the entire free space’ and click to label the volumes into the ‘Default Archive Pool’.ī2. You’ll therefore need to select the folder where the SMB share is mounted. This Disk Library will create virtual tape volumes on the Synology NAS volume that is mounted. Within the P5 Archive tab, click on ‘Storage Manager’ and then the ‘New Disk Storage’ button. Connect to the Archiware P5 web-admin interface. This data will later be moved to B2 cloud storage.ī1. This will allow archival of data accessible by the P5 system. In this section, we configure an Archiware P5 Archive workflow, via configuration of storage and creation of an Archive Plan. Note the ‘mount point’ where your OS has mounted the NAS share. Make sure you begin with a completely empty share. P5 will now be able to write to this storage.Īrchive and mount the share such that you can read and write to it. This will now become mounted within your operating system. Provide the authentication information from the B2 website to connect to the DataForB2 share. Connect to the SMB share by providing the IP of the Synology device. Now that you have your Synology device configured, go to the host running P5. This will unlock/decrypt the share, you’ll now be able to mount this share via SMB from other hosts on the LAN.Ī2. You’ll be prompted for the Encryption Key password. Highlight the DataForB2 share, and select ‘Mount’ in the ‘Encryption’ menu. In order to write to this share, it must be temporarily de-crypted using the ‘Encryption Key’ password available in the Backblaze B2 website. This shared volume is encrypted by Backblaze so that any data you write here will remain encrypted as the device travels back to Backblaze. In here you’ll find a pre-configured share called ‘DataForB2’. Once connected to the web-admin interface of the Synology device, click on the Control Panel and then ‘Shared Folder’. Your Backblaze B2 account login will provide the login credentials required to login to and configure the Fireball. Point your web browser at to run a utility that will scan your LAN and provide the IP of the device which you can then use to further configure. Once unpacked, and connected to power and your LAN, you’ll need to discover the IP of the Fireball/Synology device. Let’s now go through the whole process in more detail.Ī – Configuring shared storage on B2 FireballĪ1. You should familiarise yourself with B2 by setting up an account at and learn how to create B2 storage ‘buckets’ and perform some basic operations on them. This guide assumes some knowledge of the Backblaze B2 cloud storage product.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |