NGL, I always do maintenance on backup systems during business hours, because I don't want to interrupt my backup schedules that primarily run at night.
Yup. Pretty much gotta be that way. Production systems do work during the day and idle at night. Production backup systems do work during the night, so their maintenance window should be during the day. Worst case, someone has to wait a bit on a restoration.
Some performance tests would be nice... especially with Veeam backups as their object size isn't always they ideal for high throughput backups... (larger is almost always better)... Suggestion for another object storage system could be StorageGRID ?
They should've named it: "JASB" Just Another Storage Box. It's literally just another supermicro server, with just another raidsystem, slapped with a barebone GUI. Nothing you cannot do with ZFS and any debian (or TrueNAS) OS.
Yeah but you can't just spin up TrueNas, assign an IP and point Veeam at it the way you can with this. Yes you pay a premium for the software/support but that's very likely worth it to an org looking for a solution like this.
You are right... actually you could proably even better just install Ubuntu yourself, using the documentation provided by Veeam (they have some good guidelines). Also backing up to an S3 bucket seems nice, exept you would need a port open for S3. An immutable repository with just Ubuntu can be setup with a single trust (one-time SSH access) to deploy some Veeam components, after that there is only outgoing traffic from the backup repo server. The way this is setup, you have an extra attack surface in the web interface and the open port for S3. Both is something you do not want cause if you can access the server using a bug in one of those two, you can probably also elevate your rights and just destroy the volume (because the files are immutable doensn't mean that there is no way to delete the files, just destroy the partition and you're golden). This is however safer than just a simple SMB storage to send the backups to, but it is certainly not the best option. Also remember to not plug in the iLO/IPMI cable cause that will allow for remote access as wel.
NGL, I always do maintenance on backup systems during business hours, because I don't want to interrupt my backup schedules that primarily run at night.
Kevin applauds your bravery!
@@StorageReview Not bravery, I just like first shift support if something breaks, and my backup cycles are after hours, so........
Yup. Pretty much gotta be that way. Production systems do work during the day and idle at night. Production backup systems do work during the night, so their maintenance window should be during the day. Worst case, someone has to wait a bit on a restoration.
Some performance tests would be nice... especially with Veeam backups as their object size isn't always they ideal for high throughput backups... (larger is almost always better)... Suggestion for another object storage system could be StorageGRID ?
It's not a bug, it's a feature!
They should've named it: "JASB"
Just Another Storage Box.
It's literally just another supermicro server, with just another raidsystem, slapped with a barebone GUI.
Nothing you cannot do with ZFS and any debian (or TrueNAS) OS.
Yeah but you can't just spin up TrueNas, assign an IP and point Veeam at it the way you can with this. Yes you pay a premium for the software/support but that's very likely worth it to an org looking for a solution like this.
You are right... actually you could proably even better just install Ubuntu yourself, using the documentation provided by Veeam (they have some good guidelines). Also backing up to an S3 bucket seems nice, exept you would need a port open for S3. An immutable repository with just Ubuntu can be setup with a single trust (one-time SSH access) to deploy some Veeam components, after that there is only outgoing traffic from the backup repo server.
The way this is setup, you have an extra attack surface in the web interface and the open port for S3. Both is something you do not want cause if you can access the server using a bug in one of those two, you can probably also elevate your rights and just destroy the volume (because the files are immutable doensn't mean that there is no way to delete the files, just destroy the partition and you're golden).
This is however safer than just a simple SMB storage to send the backups to, but it is certainly not the best option.
Also remember to not plug in the iLO/IPMI cable cause that will allow for remote access as wel.