- Joined
- Oct 30, 2020
- Messages
- 31
- Reaction score
- 3
Hello, I have a client who is running 3cx Standard 16.0.5.622 on Debian and the system is having several problems which I have not been able to resolve, in addition to the system having been built by a previous contractor who will not share the root password he installed with. The current system has 16 extensions and at peak usage has two or three simultaneous calls.
To hopefully resolve problems and get CLI access to the system, the plan tomorrow is to take a full system backup, download the backup, shut down the old system, throw up a VM on Hyper-V and install a new instance of 3cx from the Debian ISO and then restore the backup to the new install. I'm planning to give the new VM 1 proc, 2GB of memory and 600 GB of storage. I will use the same IP for the new instance as the old box is using. A full system backup with all options checked is 200MB.
Are there any gotchas or items I might be overlooking when putting up a new system and restoring a backup to it?
Thank you in advance!
To hopefully resolve problems and get CLI access to the system, the plan tomorrow is to take a full system backup, download the backup, shut down the old system, throw up a VM on Hyper-V and install a new instance of 3cx from the Debian ISO and then restore the backup to the new install. I'm planning to give the new VM 1 proc, 2GB of memory and 600 GB of storage. I will use the same IP for the new instance as the old box is using. A full system backup with all options checked is 200MB.
Are there any gotchas or items I might be overlooking when putting up a new system and restoring a backup to it?
Thank you in advance!