Using minIO as a S3 Cloud Storage Device on Synology NAS
Has anyone had luck installing minIO on a Synology NAS as s3 storage? I have followed some instructions that I found for another backup product using minIO which has you install Docker on the Synology NAS and then install the minIO Image. I then installed a new Cloud Instance in the Backup Exec Command Line and set the User to match the assigned Access Key ID and the Password to match the assigned Secret Key. We are using port 9000 on the minIO server. When I try to then add Cloud Storage in Backup Exec I get the error: The server was unable to complete the requested operation. Unable to connect to the CloudStorage device. Ensure that the network is properly configured between the device and the Backup Exec server. BEMSDK Failure Code: E0009B3F. See the following Wireshark trace sent to and from Backup Exec to the minIO server when the error occurs: GET / HTTP/1.1 Host: redacted.bgibson.com:9000 Accept: */* Date:Fri, 03 Feb 2023 21:54:10 GMT Authorization: AWS Redacted :/swUqJpyTy9cvIJItoOyDtxNEd0= user-agent:APN/1.0 Veritas/1.0 BackupExec/21.3 I then see the following reply from the minIO server: HTTP/1.1 400 Bad Request Accept-Ranges: bytes Content-Length: 239 Content-Security-Policy: block-all-mixed-content Content-Type: application/xml Server: MinIO Strict-Transport-Security: max-age=31536000; includeSubDomains Vary: Origin Vary: Accept-Encoding X-Amz-Id-2: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 X-Amz-Request-Id: 17406EE9229F98CF X-Content-Type-Options: nosniff X-Xss-Protection: 1; mode=block Date: Fri, 03 Feb 2023 21:50:08 GMT <?xml version="1.0" encoding="UTF-8"?> <Error><Code>MissingFields</Code><Message>Missing fields in request.</Message><Resource>/</Resource><RequestId>17406EE9229F98CF</RequestId><HostId>090c0eb5-9a28-4741-80d3-36c5388de3cc</HostId></Error> Any ideas? Thanks, Brett Gibson
vffinstall log file deleted but agent not rebooted.
vffinstall log file kept increasing so I followed the method in the following link: Backup Exec VffInstall log size keeps increasing (veritas.com) and deleted the vffinstall log file but agent was not rebooted before that so is that the problem because the server is not backing up and also has an Oracle Database installed on it. Please reply as soon as possible. Thanks
Backup Exec 22.0 to 22.2 Upgrade/Update
I just wanna know if we are in the same series like if I wanna upgrade from Backup Exec 22.0 to 22.2 then will we have to run the setup of Backup Exec 22.2 Or we just need to install the update that comes in Backup Exec 22.0. Btw I have selected the install option but it is stuck in the downloading phase. Can anybody help please?Backup Exec support for encrypted VMware Virtual Machines
VMware vSphere encryptionwas first introduced in vSphere 6.5 and vSAN 6.6, enabling encryption in both virtual machine and disk storage.It only requires the vCenter vSphere Server, a third-party Key Management Server, and ESXi host to work. Security nowadays is very crucial, andencryption provides a solution towards cyber threats. If anyone gets a copy of the raw VMDKs, it can be easily mounted on aVMware server. Hence, the feature getting widely adapted by many organizations. Backup Exec provides support for encrypted VMware Virtual Machines stating with VMware 6.5. The Virtual Machines must be preconfigured for VM Encryption per VMware Documentation.Encrypt an Existing Virtual Machine or Virtual DiskVirtual Machine Encryption For the default backup job settings, it will use the NBD transport mode and the user can also select Network transport mode with SSL. Encrypted VM usingtheHotAddmethod can be backed up ifBackup Exec server VMis encrypted as well. Permissions required -Cryptographer.Access, Cryptographer.AddDisk SAN transport mode is not currently supported for backups of encrypted virtual machines. File GRT and Application GRT are supported during backup & restore. The backup is taken in decrypted format, hence when a backed-up virtual machine is restored, it is restored in decrypted format. The common Key Management Server (KMS) or Key Management Server is not required during a restore job. Restore or Redirect restores of VM's can be performed back to vCenter, ESXi hosts, and NTFS file systems. Validate VM for recovery and Instant recovery feature is also supported for encrypted VMware Virtual Machines.So with all the added security benefits to encrypting VMware virtual machines, this is certainly a security feature that most users will want to secure sensitive virtual machines running in the environment. With Backup Exec, you get a simple, powerful solution that ensures your business-critical data is never at risk of being lost, stolen or corrupted.
