Direkt zum Inhalt

Computername to be changed - best practice ?

Thread needs solution

Hello,
we have several computers in our company and the current naming scheme contains the location.
As some computers shall be moved to other locations and are replaced by new ones we have to rename them,

So first of all the status quo:
- Acronis Backlup Advanced 12.5 on ther machines and on the Acropnis Management Server
- Machines are running WIN10 Pro
- Server is running WIndows 2012 Server R2, Acrive Directory
- Backup Plans have the naming scheme "WS_[MACHINE NAME]"
- Backup filenames are named "[MACHINE NAME}_FullBackup"
- Backup Format is 12
- All Backups are Full Backups

Then the thing with the machine names (as example):

A Computer is named "PC_Main_Office1"(let us assume it is a intel-i3 machine)
The i3 machine is now replaced by a new powerful i7 machine and the "old stuff" is used ath the receptiuon as there the power is sufficient.

So after all
- the i3 is called "PC_Reception"
- the i7 is called "PC_Main_Office1"

Regarding Windows, Active Directory and so on that´s no problem.

But what is the best way to handle this within Acronis?

Topic 1: PC_Reception
As the Backup plan is newly created, there should be no problem or are there any cryptic IDs that are used by Acronis to identify the machine and that might make problems?

 

Topic 2: Replaced PC_Main_Office
If I install the agent and then assign the "old" Backup Plan to this machine, does that make any problems ?
I assume that the backups are just appended to the backup file as the machine name is the same as before.

 

Could anyone give me any hints ?

 

Regards

Sven

0 Users found this helpful
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Beiträge: 0
Kommentare: 82

Hello Sven, 

thank you for the question!

As I understand, you exchange an old PC_Main_Office1 with a new one. The new one will have the same name and the same plan assigned. 

In this scenario, you will need to do the following: 

1. Delete the old PC_Main_Office1 agent from the management server 
2. Install an agent to the new machine: 
3. Make sure that under Settings – Agents the correct agent with the new IP, MAC and other parameters are shown; 
4. In the existing backup plan, re-specify the agent by editing the plan and start a new backup. 

Note that the first backup will be a full one as this is a new machine. 

Deleting the old PC_Main_Office1 will help you avoid possible issues with reflecting the machine in the management server. 

As for the topic 1, PC_Reception, I would suggest you to create a new plan, re-add the machine and start a new backup chain. 

I hope I could answer your question. If you have any other concerns, please let me know. 

Wishing you all the best.

Hey there,

now after a few weeks....I did the rename bit...no success.
The new machine works fine.
 

What I did:
- I renamed thje machine (it was  before "PC_KIKOG" and now it is "PC6").
- updated the AD on the Windows Server
- created a Plan where I backup the PC6. Filename is created with [MachineName]...

The Filename is still with the old name of the machine.

It seems as if in the deep of the Acronis database there is still a link between the old machine name and an ID that Acronis uses.

Is there a way to solve this problem?

Another thing:
If I have a typo in the machine name during the adding step (i.e. I typed "Pc6" instead of "PC6") this can not be chaned any more...even a remove and a new adding of the machine sill leads to the wrong name (regarding uppar and lowercase).

It´s really weird that tAcronis stroes somewhere some information that I cannot change any more...

 

S

 

 

 

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Beiträge: 250
Kommentare: 7092

Hello Sven,

Have you tried re-adding the machine in question using the approach from https://kb.acronis.com/content/46110

Hello Ekaterina,
no I did not.

As Acronis had shown me the new name after renaming it in the domain I had no need to re add the machine.
Honestly spoken I was quite surprised that Acronis got it, but it seems as If I was a bit too eearly happy ;-)

What is the background of the re-adding?
It seems as if Acronis uses a unique ID in the deeps of the database and there the "old name" is still present.

I will give it a try in the next few days.

 

But as I have also a lot of different database/dashboard issues (zombie backups and backup plans that do not esist since months) I´m just thinkinfg about a complete reinstallation of Acronis.

Regarding a reinstall, is there a way how to keep my old settings ?

 

S.

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Beiträge: 250
Kommentare: 7092

Discussed the topic with colleagues - so, in fact, the expected behavior is the changes in naming of Agents are automatically reflected on AMS, as the Agents constantly communicate to AMS and sync the latest information about plans and other properties. If you observe something like 

> a remove and a new adding of the machine sill leads to the wrong name

it's better to investigate the issue together with the support team.

> Regarding a reinstall, is there a way how to keep my old settings ?

Only the way outlined in https://kb.acronis.com/content/61354