BE 15 fp 5 backup to the private S3
I'm currently trying to test configuration with backup to our private S3 which is compatible with Amazaon S3 but unfortunately I am unable to complete it. here is the list of my actions: 1) configure cloud instance using BE MCLI according to BE MCLI *.chm help. It finishes with success. 2) Configure Cloud Storage using BE GUI. All configuration wizard steps completes with success, wizard even successfully retrieves the list of S3 buckets from the S3 service, and completes the configuration with no error. 3) At the end of configuration BE offers to restart it's services to finalize the cloud storage. 4) After the restart device is still shown as offline. There is an alert at the time of services start: Unable to connect to to the OpenStorage device. Ensure that the network is properly configured between the device and the Backup Exec server. For more information, see V-275-1017 on the Symantec Knowledge Base. However, I was unable to find any useful reference in KB to solve this particular issue. The main question is to understand what is missing from either configuration steps or S3 itself. Does anyone know how this can be debugged?
Backup Exec 3600 Could not connect
Hello, I need assistance our BEAPP is working perfectly fine until we re-started the server last 21-Mar-18. Since then the BEAPP is not running anymore. When connecting we are being prompt for this error. We checked the services and it could not start, we are getting error for the following services: Server:BEAPP, Service:BackupExecAgentAccelator failed to start. Error: (1068) - The dependency service or group failed to start. Server:BEAPP, Service:BackupExecDeviceMediaService failed to start. Error: (1068) - The dependency service or group failed to start. Server:BEAPP, Service:BackupExecAgentBrowser failed to start. Error: (1068) - The dependency service or group failed to start. Server:BEAPP, Service:BackupExecManagementService failed to start. Error: (1068) - The dependency service or group failed to start. We have checked this one by one by changing the logon account eitherway to Domain Admin Account with Rights and System Logon - both failed. We also update the credential on BackUpExec Utility and also to the credential manager BEAPP software (connection manager) and we got the same error.Error: (1068) - The dependency service or group failed to start.
BE the rainbow in the someone else’s cloud
During these days of social distancing, I have tried to not get stuck behind my desk all day long and regularly take conference calls while out walking. Today, while on my morning walk I saw a message of inspiration that is the perfect metaphor for what SaaS Backup brings to the SaaS applications it protects.
Backup jobs stay in a Queue state for a long time.
Hi all We have a problem to execute the backup jobs from a BE appliance console.All jobs stay in an "Active:Queued" for a long time and don't transfer any data. The jobs are send to deduplication disk storage. We can review the TN: https://www.veritas.com/content/support/en_US/article.100007231 but not "po_list_2" are present on theDeduplication Storage Folder Path\databases\catalog. Also review the TN: https://www.veritas.com/support/en_US/article.100010408 but no "*.lck" files are present. Thanks in advance for your help.
Duplicate job copy data from original location instead of source job location
We use BackupExec 22 Rev 1193.1009. BackupExec server (hardware serverProLiant BL460c Gen9) is connected to SAN and LTO8 library. Speed of Ethernet connection is 10Gb/s At first backups are saved to SAN deduplication storage. Then - duplicate job runs. We intended that duplicate job would run from SAN backup, not from original location. The speed between SAN and tape is much faster than speed between original data location and tape. We intended to make a system where 8 backups will run simultaneously to SAN. They are slow (because they copy data from original location) but we do not care - because we can run many backups simultaneously. THEN - when first stage backups are finished - they duplicate to tape. They run only in 3 streams (because library only has 3 drives), but we do not care - because the speed from SAN to LTO8 tape is fast. But it seems, that duplicate backups run from original location, instead of SAN, where first stage of backups are saved. This is VERY VERY bad to us, because we need to backup about a hundred servers and some of them are large. If duplicate backup - copy data from original location, instead from SAN - we loose speed in about 6-8 times I think. I opened topic about a year ago about this issue and I was informed that duplicate backups run from primary backup, not from original data location. Does duplicate JOB copy data from source VM or fro... - VOX (veritas.com) I tried to enable\disable "Direct copy to tape" checkbox, BacupExec still copy data in duplicate backup from original location. Also I tried to save first stage of backup to regular disk storage (without deduplication). This is disk storage on BackupExec server itself - so speed must be very high. But BacupExec still copy data in duplicate backup from original location, not from disk storage. I also checked the bandwidth of optical Ethernet which is connected to BackupExec server and it is utilized no more than on 30% I tried to look through all options of backup, but didn't found anything related to problem - from where duplicate backups run: from original location or from first stage backup. Is it possible to configure duplicate backups to run from first stage backups location? How to do it? This will increase overall speed of my backup system in 6-8 times.
