hi all,
we switched from a mini M1 server with Pegasus32 to a Synology 1221+. we had terrible access rights problems on the mini server. before anyone asks. yes i tried to solve this with TinkerTool. but it was always temporary.
Now I don't want to sell the Pegasus32 but use it as a backup from the Syno. The Syno has 2 USB 3.2 Gen 1 ports and one eSata. is there any adapter to make this work?
Hi Michael,
Now I don't want to sell the Pegasus32 but use it as a backup from the Syno. The Syno has 2 USB 3.2 Gen 1 ports and one eSata. is there any adapter to make this work?
There are 2 USB-C ports at the back of the Pegasus32.
To be clear, both ports work with Thunderbolt3, but the USB-C port to the right is also USB3.2 gen2.
So you should be able to connect with a USB cable. If the Synology ports are USB3, you can connect with the Thunderbolt cable that came with the Pegasus32. If it's USB-A, you'll need a USB-A to USB-C adapter cable.
This assumes that the Synology USB ports are USB host ports and that they can connect to storage. Also there is a question as to whether the Synology can do backups to those ports. The Product Manual or Spec sheet should help here.
ok. i connected it with a USB-A/USB-C 3.2 gen. 2 cable. but the pegasus didn't even boot up. however, i can't remember if i tried both ports. i'll test that and report back here.
have several RAID systems connected to the USB port on various other synos. they work stably, e.g. some cheap icybox parts.
for example ICY BOX IB-RD3640SU3
ok, you have to configure the backup RAID as any RAID with the disks before, of course, but then you can initialise it with the syno itself as normal ext4. it recognises this as a HDD
You also have to do this with the pegasus.
but i thank you for the info. if it works, i'll get back to you here, if not also :-)
thanks in advance!
back with the result. i changed everything over the weekend. the first cable was obviously of low quality. Pegasus32 R8 now works as a backup for Synology 1A. just as RP described.
THX
and also a thank you to Zachary Lyons, for the unnecessary reply. who neither understood the posting nor the problem.
