- #Backblaze synology intigrations how to
- #Backblaze synology intigrations install
- #Backblaze synology intigrations password
Shared Folder: select the ‘ DataForB2 ’ folder. Server name or IP Address: fireball123.local (replace 123 with the number of your personal Fireball order). Create your backup task, then click Next. Choose the ‘ rsync ’ Backup Destination, then click ‘ Next ’. Click the + in the bottom left corner of the window, select ‘ Data backup task ’. #Backblaze synology intigrations install
Install Hyper Backup from the Package Center.Sign in to the Synology DSM for your personal Synology device (not the Fireball).Create and finish your Hyper Backup job from your Synology device Repeat this step on your Synology device so that both devices have rsync enabled.Ħ.Open File Services under the File Sharing section.
From the Synology DSM, navigate to the Control Panel.Enable rsync on the Fireball and your personal Synology NAS. Every time the NAS is powered down or reset, this configuration information (the encryption key) must be re-entered.ĥ. Please Note: The encryption key is kept only in volatile storage (in memory) on the Fireball. Enter the encryption key you obtained from your B2 account to mount the encrypted Shared Folder.In the browser window, navigate to ‘Control Panel’.
#Backblaze synology intigrations password
Log in using 'backblaze' as the username and the password you obtained from your B2 account. If no Fireballs are detected, double check your network connection with the Fireball, ensuring it's on the same subnet as your computer. Double click the Fireball in the list, and your browser should connect directly to the Fireball's web page. Visit to scan your local network for all Synology devices. To protect customer data, all data sent to Backblaze on the NAS is encrypted. Enter your Fireball's password and encryption key on your Fireball Keep these credentials accessible- you will need them in later in step 6F. Click the blue ‘ i ’ icon associated with this Fireball order. Sign into the B2 account to which the data is to be transferred. To obtain this particular Fireball’s password and encryption key: The username for all Fireballs is always “backblaze”. Get your Fireball's password and encryption key Connect the power cable to the NAS, plug the NAS in, and then turn it on with the power button.ģ. Also, network traffic to other devices on the wireless network can suffer performance loss when competing for bandwidth with the NAS. Wireless (Wi-Fi) connections have limited bandwidth, and data transfer will take much longer than with a direct connection. The NAS should not be connected to the data source over a wireless connection. The NAS supports only a direct network connection via either the 1GigE or 10GigE ports. The NAS cannot be directly connected to a computer. At a small office, this might be a network switch or router. The Fireball NAS must be connected directly to the network. Please note: Although the illustration shows only two drive bays, all eight of the included drives must be inserted into the Synology NAS.Ģ. The disks are installed in trays, and the trays need to be placed into the NAS. If you do not have a Backblaze account yet, you can sign up from the same page.īackblaze ships the Synology NAS without the drives trays installed to better protect both NAS and drives. Ready to order your B2 Fireball? Visit our B2 Fireball Home Page and sign in to order. #Backblaze synology intigrations how to
Not what you’re looking for? If you are a Fireball customer looking for our standard upload guide, you can find it here: How to Upload Files to B2 Using Fireball Creating a Hyper Backup job on your personal Synology device.Connecting the Fireball to your network.This guide will cover the following topics: Your internet connection is not fast enough to complete the initial backup in a reasonable amount of time.You do not have a backup in B2 Cloud Storage, but would like to.Synology NAS owners can now create Hyper Backup jobs and use a B2 Fireball as the destination. B2 Fireball Guide: Creating and Relinking a Hyper Backup Job
0 kommentar(er)
