First of all, backups better being automated, not done manually.
All regular semi-manually fumbling increases the risk of fatfingering, and to be forgotten to be done, so backups are not recent enough. And frequent fumbling with hardware increases the risk of hardware damage.
Install the medium you want to backup to into a safe place (temperature


), and don't touch it unless you have to.
Then see how to automate your backups: find some BU software that suits your needs or write some scripts yourself.
Distinguish:
Files need to be stored safely.
Backups are to save your time you worked on something.
What you need to backup is your
/home,
/etc,
/usr/local/etc (X11 config, and others) and all your production directories you do work in: the documents or the source code you write (

version control system & backup the repository), the pictures you create, the music you compose... - the work
you do, the files you spend on time editing them.
That needs to be backupped regulary, automatically into a safe storage.
But if
my media(photos,videos,etc)
means your mediathek - your "porn collection" - PDFs you downloaded, pictures from vacations, parties, family reunions, movies, music or image files you downloaded, bought or got by other sources... -
IMO those don't need to be backupped, at least not regulary, above all not frequently, but to be stored safely, only.
You see, those files are not going to change. You may add new ones, sometimes delete some, and sort them - but you don't work on those files, you don't change them. So, IMO it makes no sense to run a daily or even more frequent BU routine updating files on the BU medium to match the ones on the working storage, when there is nothing to update, because they don't change.
Just save them to a safe storage place where you have access to from your desktop machine: Add another ZFS pool to your machine, or get an additional machine for this job you can access to over LAN (NFS, ssh, maybe samba). Any used, old, still working junk without keyboard, GPU and monitor will do. Only the drives are important. Those must be aces. The rest of the machine may conk out anytime, doesn't matter.
Maybe manually do additional redundnat BUs of that quarterly to a single extra drive, but if the storage is redundant enough this ain't neccessary against hardware failures.
A mirror consisting of two drives was bare minimum - IMO too few for a safe storage. For a safe storage I recommend more redundancy than one drive may fail and then there is only a single drive as the last one left.
When a drive is replaced in a ZFS pool resilvering is done. That's a full load job for the drives. Depending on the size of the drives and the amount stored this can last a few hours. Imagine you replace one of your drives failed by becoming old. All your data is now on one single last drive left. And then this one needs to run full power for a couple of hours.
Depending on the size of the drives you have, what you can afford, how much space you need (avoid over 80% capacity used), how much places you have (a PCIe card providing more SATA ports cost a couple of bucks), and how valuable the files are to you (how much effort it takes, to get them again), if even I would recommend at least a three drives mirror as the barest minimum, but not optimal. Not really good.
Better use 4 drives and create a raidz2 pool.
Anyway boths ways you can afford to lose two drives without data loss.
A raidz3 pool can afford to lose 3 drives, but you need at least 5 drives to realize it.
A raid10 pool also needs at least for drives, but IMO makes only sense with >=8 drives, when lots of drives are needed at most possible redundancy. Half the drives may fail, but it provides the least storage capacity available you get by the drives you add.