larimerE wrote:Question: We do a configuration backup. We have a separarte sql server Problem: Several servers are indexed during backup (these files are saved locally through veeam) - how will I "restore" those in case of disaster if I am not directly backing up my Veeam B&R server as Veeam suggests?
If you're referring to indexing data (stored in the catalog) recovery, then please review this topic (including subtopic), it should answer your question > Basic Backup catalog questions
cffit wrote:Is there documentation on how to backup the VEEAM physical server with VEEAM Endpoint? Do I install the full VE on my VEEAM server?
Not sure that I understand what you mean by saying "full VE", but if you want to protect VBR server with Veeam Endpoint Backup, just install VEB and configure backup job to do full image backups. You can point your backup job to any supported designation target, for example a CIFS share.
Dont know if this has been mentioned before but hey ho (12 pages of posts to check
) but im my dev platform i simply backed up the Veeam virtual server as a separate task (self backup to the cloud connect) once all other backup tasks are completed to ensure that database is the most up to date for consistancy. This is not ideal as it takes up more space in the repository for each instance/customer but in a DR scenario you can bring the Veeam server back and then your good to go. Ideally an off-site copy would be best like cloud connect repo but a DR site would be just as good. This means the extra SQL maintenance plan management is not required and is easier to restore than rebuilding the setup and recovering the DB which of course there is a chance it does not come back properly.
Yes, this could be another option of protecting your backup server.