“sqrt(-4)” … “i sqrt(4)” if I remember; I see a video a week ago.
Square root of -4 is another story.
Considered advanced maths, the right answer would be like i4…
See? I need to read more and assimilate the knowledge.
Time to go out, because of the cov, I can leave an hour early for lunch, and I’m allowed not to return. But I try to stay connected from home (here and at the office)
Knowledge is a lot and plenty…
Most can’t handle more than 1-2 subjects with adequate depth.
OK, good ride home!
Hi @Andy_Wismer
What is your strategy for backing up the PVE_VZBackupDump MVs from the NAS to another NAS?
- Rsync with HyperBackup?
I made on the backup NAS a shared folder with NFS.
Of course, I will use HyperBackup to backup to a USB disk, or do you use a cron job to do this backup to the USB disk?
Regards
I found some info to read.
Hi
Sry, was on the phone with Elleni (from this forum)…
Yes, I use Hyperbackup in Synology to make a back of the whole NAS to USB.
You can set times and shedules in Hyperbackup directly.
Andy
I was saving lives at work, too.
Yes; I was having trouble with Hyperbackup, using an user without rights to create the task.
Now I will try to do something similar but I was doing another synology, now this one has space.
I don’t know what I need to do, but I guess between synologys the rsync backup should be something natural, but if the NAS 2 (target) shares a folder with NFS, maybe I need to mount it on the NAS 1 (source)
Regards
After this, I need to ask about the second interface of my proxmox1. If I want to have the “private” network between the Proxmox (two) with the NAS; without any other traffic.
I think that here I need to learn how to create a VLAN for the 2nd NIC in both Proxmox for this task.
For a (Backup) copy from NAS A to NAS B (Both Synology) instead of using Backup, you could use
Cloud Station Server on NAS A, and Cloud Station Sync on NAS B. This would be a one way sync (almost continously in background).
This needs a few tweaks during setup, but otherwise works well.
One Note:
Do NOT attempt to sync the shares DiskImage and Container - this will almost get you data corruption, as those files are constantly in use! Synology can’t really handle this, it looks good, but isn’t!
Only sync the backups, ISO (all non “live” stuff).
I use this method for backups Off-Site, mostly to my clients bosses at home…
The big advantage: Here the data is 1:1, not packed in a special highly compressed format.
Proxmox Network:
Get both your Proxmox fixed IPs (like 61, 62) next to each other.
Do the same for both NAS, like 71, 72.
Get switches ready, if possible a seperate switch for PVE1 - PVE2 and NAS (Storage Net).
Then we can do an AnyDesk session…
Don’t forget that these IPs should all be long term.
Also, change names. It’s easier to explain to a new guy also, if the name tells something about what the box does and where it is.
My first networks used
A) Planets
B) Star Trek Spaceships
C) Greek Gods
When you run things in this scale, finding names get difficult:
(My Home-LAN in 2003… Not my office !!!)
My networks had even before 2000 more than 30 hosts…
A Windows Explorer view of a Network spanning 2 sites:
Andy
I’m gonna need to buy some things, especially to reinstall the pmx2. (SDDs maybe or Black WD HDD)
I have a small unmanageable 1Gigabit switch.
This are the “current” network on both proxmox. Both have the same address in the vmbr1 but disconnected, all of this before the cluster for pmx1.
Can I change IPs for the running pmx1 192.168.16.1 → 192.168.16.61 without issues? Giving permission to access the new IP to the NFS shares on the NAS.
pmx2 would be reinstalled, so the IP could be the 192.168.16.62
Use PVE1 to make backups on the NAS of all VMs.
Then it would be best to reinstall both Proxmox, with the newer experience and know how you have.
I have a visitor for about 30 mins, I’ll be back
I was about to install CSS on NAS B, and I come across this.
Same for CSC
I’m going to look into the Syn. Drive Sync/Server
Better use the oldversion, the new one does too much…
I don’t need word files edited on both sides…
Installing you recommendation.
The recommended (by Synology) new application does not exist on my NAS B .
For us, using NextCloud makes more sense for that specific use case. (Usable on both sides…)
Here, you want a no nonsense one way sync from A to B…
Not really needed, as Proxmox does it’s own versioning
Create the share folders by hand on the other NAS (NAS-B).
With CSS (Client) just refer to the existing folder you created.
Take care to remove the “safety bit” like when creating the shares - synology likes to set this!
If you let CSS create the Target Folders, they become unusable because of the set safety bit…