I am running into an issue with password protected shares right now and thought i got around it by adding the following net use statement to the script.
But all i get is a functionality that is able to connect to the share and create folders successfully...but when it comes to Start-VBRZip...it seems to fail...no reaction on the vSphere(normally is see changing this and that in the log)
Without the net use part i get access denied on the network share...
Can someone see the culprit right away that i don't see?!
v.Eremin wrote:A lot of people in this thread said that granting Veeam account as well as Computer account read/write permissions on the given share have helped them to solve the said issue. Thanks
Ok...got that...but "Veeam" account ?!?!
Which user is veeam using?! Will not be Veeam as user name or do i miss something here?!
How can i authenticate the Veeam service?!
No worries. So far this has been number one request we got in regarding Start-VBRZip cmdlet enhancements. We're planning to add -NetworkCredentials parameter to the said cmdlet down the road in order to make our customers' lives easier. Thanks.
unfortunately I seem to be to stupid to get it working with my Synology NAS. I want to Backup directly with the script to a NAS Share called "Backup":
\\10.10.10.5\Backup\
The Backup&Replication Software is installed on a Windows 10 Machine in a Non-Domain (WORKGROUP) where I execute the script in Powershell with admin rights testwise.
The Backup fails due to an access error (username or password is false).
I assume I have to solve these issues according to posts above:
1) Veeam account read/write permissions on the given share
2) Computer account read/write permissions on the given share
I do not know what is meant by that? What is the "Veeam account" and how do I give it permission to the share?
Do I have to map the UNC on the PC in advance?
I created a user on the NAS with the same name of the PC-User logged in (e.g. Tom) and gave the user the same password than on the PC.
This user has the right to access the Backup share but this does not work??
Can someone be so kind to explain this more in depth?
OK, I finally solved the problem myself. If anyone else having this problem, here is the solution:
Change the Veeam services on the backup machine (e.g. PC) that they are not running under "local system account" but under your specific account that has corresponding rights to access (read/write) the NAS. The local system account has no rights to access network destinations.
Correct, by Veeam account we refer to account under which Veeam-specific services are running. Sometimes changing that account does not solve the issue, and additional permissions must be granted to VB&R computer account.
Thankfully your script makes it easy for newcomers to successfully perform backups ;D Thank you for that!
Can you tell me one more thing in respect of he $Retention date in your script? Is the date stored in the .vbk file or is just processed by B&R software with the next backup?
I ask because I backup the .vbk to a CIFS share and afterwards the same .vbk will be copied by the NAS to an external HDD (rotation) via USB.
So e.g. when I set "Retention" to "Tomorrow" in B&R I assume the .vbk will be deleted on the next day on the CIFS share after creation.
But does this also mean that this particular backup cannot be restored later e.g. after a week when I try to restore a copy of the .vbk stored on a external HDD?
Is the date stored in the .vbk file or is just processed by B&R software with the next backup?
The backup file itself does not have any time bomb or something. It's backup software that issues remove command when time comes (not with the next backup). Thanks.
Hi, i take your script from 3/24/2015 (update)
But i also tried some other scripts.
If i start the script over powershell and the first vm finishs, the error is coming.
Checked the script with 9.5 free version, everything has worked as expected. Most likely, you've modified the script somehow, so that it tries to pass several VMs to -Entity parameter of Start-VBRZip commandlet. Thus, the error. Thanks.
When using power shell command Start-VBRZip resulting backup files are always created using local administrator's account instead of the account used to run the script / command.
Thus resulting in access denied error for the NAS file system which only knows about domain users.
Has anyone encountered this issue before or knows a solution?
I'd say this is an expected behaviour. Backups are always created with the use of account specified as backup service account (under which VB&R related services are running). The account used to run script doesn't play crucial role here.
Well, using Veeam Backup & Replication Console, the backup files will be created for the user starting the console....
That's why I was expecting similar result using command line tool.....
And btw. the Veeam Backup Service is running by a domain user which would be fine to access the NAS....
Which Veeam service would need to be changed to use the expected domain user having proper access rights for the NAS?
this is my first post about this product I think is really powerful. Considering the various possibilities I stumbled into powershell script released by Vlad Eremin and I was wandering if someone in this forum has used or is using it
I am going to try it very soon but I am interested in paticular in the encryption feature
Hello Vlad, thank you so much for the script that you created, its very useful!
Yes, I was just talking about that, in the encryption portion its demonstrated how to use a password via Read-Host and ConvertFrom-SecureString from a file. In the first case its not so useful to automate in a task scheduler job. In the second case it still requires a txt file containing an encrypted password but it is still easy decriptable
Personally I haven't tried that (just covered the very basic scenario), and doubt that anyone else has. So, I'd be interested to hear the results of your findings. Thanks.