Appliance 12.5 U3 kann sich nicht selbst Backup-en
Hi,
Nachdem mein (VM)Windows-Backup-Server nach einem Update gecrashed ist und sich nicht restoren läßt, versuche ich das Backup mit der Appliance durchzuführen (vorerst noch mit Demo-Key). Nach der Installation wird der Rechner auch gleich als erste Maschine angeboten. Aber nicht mal das Backup funktioniert. Als Meldung kommt:
Was soll diese Meldung aussagen?
Thank you for the answer. On first start, only one Maschine was ready to Backup. Now I have added the Host-ESX and I got a second Maschine with the same name. I started the Backup and it seems to work til end. But then I got the Message: Die Aktivität 'Deleting snapshot' ist fehlgeschlagen. The file is read-only.
Is something wrong with the configuration?
The message you quoted does not reveal the actual problem unfortunately. Can you please attach the full log from the backup operation, so that I can advise? Also please clarify which exact item you selected as source for backup? A screen shot from "Devices" list with "Backup" tab opened (to see backup plan settings) would be most helpful.
Thank you.
Hi Vasily,
I think, the agent has created a snapshot, the backup is finished and then, the agent has no rights to consolidate the snapshot. ESX shows a message, that the machine has a snapshot and has to be consolidated.
Logs are attached.
Hi Wolfgang,
The error from the log:
| error 0x40007: Error occurred while opening the file.
| line: 0xc3bc4c1eb2299b0f
| file: e:/206/enterprise/applications/archiving/storages/archive3/src/archive3.cpp:357
| function: OpenArchive
| Archive3Code: 0x138f
| Name: BackupAppliance-074175A6-7FB4-474E-AA31-8B17E475CFEA-52F47760-5869-D4FA-9B36-DB09AC0AB30CA.tibx
| $module: archive3_adapter_lxa64_10130
|
| error 0x4000c: The file is read-only.
| line: 0xc8d8731ce106f9ca
| file: e:/206/archive/ver3/adapter/error.cpp:60
| function: ConvertArchive3Error
| $module: archive3_adapter_lxa64_10130
The problem is related to specifics of target backup location used, e.g. NFS server somehow locks the file and prevents modifications in it. This issue should be investigated with help from our support team.
The workaround should be to switch to legacy archive format (which won't require modifications to be made in existing file, so the problem should be gone):
- Create a new backup plan
- In Backup Options->Backup format->choose "version 11" format
- Save the backup plan
P.S. As I mentioned earlier, please remember NOT select "BackupAppliance" as "Virtual Machine" when applying backup plan - on your screen shot you are trying to backup appliance in agentless mode which is not recommended.
Thank you.
Hi Vasily,
sorry, but now I have a problem to understand, wich vm I should take. The "VM with agent" reports the error in the start-message of this thread.
I have deleted all other plans, created a new one with "VM with agent" and Backup-Format 11.
What can be wrong? the log should be equal the first one.
This is the correct item to select shown on your last screen shot. On your previous screen shot (from https://forum.acronis.com/comment/452708#comment-452708) however the backup for this item completed successfully.
If the backup problem is reproduced for this item too, but only on 2nd backup attempt (e.g. during incremental backup), then the issue should be related to backup archive + NFS server specific (that it doesn't allow modification of existing file) and the workaround would be to create new backup plan with Backup format set to "version 11". If it still fails, then please attach the new log - there must be different error in it.
Thank you.
Hi Vasily,
I think, I have found a working solution.
It was the first time, I used nfs to my NAS and maybe I have a wrong rights-management on this folder.
So I have created a new Plan using "smb://nas/Backup/ESX/Backup" as target and with this protocoll and machine's without Agent works fine. I got the Appliance backup'd and three other VM's mixed windows an linux.
The full backup works and the the incremental Backup too.
I have now tried with "VM with agent", but I got the same error.
So I will work agentless.
And the thread can be set to 'solved' if it is possible.
Thank you for your help.
PS.: You don't want to use agentless backup?. What's the difference?
Hi Wolfgang,
>> PS.: You don't want to use agentless backup?. What's the difference?
If you select backup appliance as VM then it would try to backup itself by itself (it's like biting own tail :)) which essentially means that the appliance VM will be snapshotted on vSphere level and during this snapshot there potentially could be network disconnection issues between the appliance and the vSphere. The automatic connection re-tries do handle these situations, but still it's not really a good way to protect the appliance itself as "VM".
One possible variant (to backup all-in-one appliance in agentless mode) is to deploy another (not "all-in-one") appliance from web console GUI: Devices->Click Add button->ESXi->Choose default deploy appliance option. In this scenario another smaller VM (smaller since it doesn't contain the management server services) will be deployed to vSphere and it will be acting as stateless backup agent registered on original "all-in-one" appliance management server.
Next you can bind the "all-in-one" appliance VM to this new agent from Details tab in "Assigned agent" section so that it's being backed up by "external" agent. See below screen shot:
...where
1 = additional appliance which serves as pure backup agent for VMware
2 = original all-in-one appliance shown as "VM with agent inside" - it can also serve as backup agent for VMware
3 = original all-in-one appliance shown as "VM"
When choosing which agent will be used to backup specific VM ("Change" button on the right), you can select either 1 or 2 when using "Manual" option.
Thank you.