Some new issues with 12.5
Hello alltogether,
after the first annoying experiences with 12.5 (see other thread) I now have som enew issues:
a) Crendentials regarding StorageNodes
The Infrastructure:
- Storage node on a bare metal
- A NAS in the network as managed location that is used by the ASN
- NAS and machine with stroage node are domain computers
I had huge problems with backup plans that shall use the NAS as destination.
my way of doing:
- attached the storage node to the Management server by using domain user credentials - check
- connected the storage locations by using domain user credential and browsed to the location - works, but I had to enter the credentials very often afterward (e.g. after logoff and logon to the Mgmt Server)...
The backup plan that uses this storage locations failed with a message that the user / password is inorrect.
The I digged deeper and saw that the user that tried to connect to the NAS was missing the domain name...hmmmm
If the plan uses the NAS share directly....all works fine.
Is this a known issue ?
If a plan uses a storage node there are 2 credentials right ?
One that connects to the storage node and one that connects to the netwrotk share on the NAS.
What is the intended way of handling this?
I then entered the path to the NAS share during creating the managed location manually \\NASNAME\share... and since then all works fine....hmmm sounds weird or ?
b) Renaming a backup plan
During the research for a) I created some plans and also renamed them.
If I look in the Backups tab to the Backup Location (the upper mentioned managed location on the NAS) I see the backups that are stored there.
The naming seems to be [Machine Name] - [Plan Name] - in my case "SRV-INFRA2.DOMAINNAME - F_Fileserver"
But why is the "Plan Name" still the same as it was for the first creration.
I renamed the Plan to "F_Fileserver_new" --> no change in backup name.
I ran the backup plan --> no change.
Even if I look into the details of the serveral versions: all show the Plan Name as it was during thje frist backup creation.
I thought, that the Acronis-way that the Plan ID and the Plan Name are independent is a good idea.
Buit I expected, that a renaming of the backup plan has also effect in the Backup version details and the Bakcup name in the Backups Tab.....
Where is my misunderstanding?
If the reference to the Backup plan is to them name it was in the beginnign of time, renaming is very dangerous....
c) Statistics fot the several locations
It seems as if the Pie charts do not reflect the backup size for managed locations - correct ?
d) Feature missing
One cool feature of 11.7 was, that it was shown if a plan´s options differ from the standard backup options.
This was extremely helpful if the standard options were changed.
This feature is gone.....it´s now rather hard if a plan has specific settings to see them fast.
I have to check each setting manually....
Thanks for any comments
Sven

- Log in to post comments

Push,
really no information ?!?
One additional question:
Why are the credentials not stored in the backup console?
Each time I log on to the console and then want to look into the backups I must enter the credentials for the storage node...
Regards
Sven
- Log in to post comments

Hi Sven,
a. 1. Domain name missing: if you are sure you've entered the domain name originally, and then it was lost/forgotten by the program, please open a support ticket for the investigation
2. >If a plan uses a storage node there are 2 credentials right ?
Yes, that is correct. The backup plan is stored and edited on “Management Server”. It needs credentials for the “Storage Node” machine, that manages the backups themselves, and for the NAS, where the backup files are stored.
b. Unless you delete and recreate a backup plan from scratch, it will always have the same Plan ID, a GUID-like unique identifier. Change the human-readable name will not break the link between old and new backups, nor will it have any other negative effect.
c. Yes, it is a known issue
d. Thanks for the feedback! We may re-introduce the changes tracking when editing a backup plan, at some point in the future.
Thank you
- Log in to post comments