Sb5
November 15, 2022, 8:56pm
1
Hi
I have a client who had Pulse v6 installed on their Dev and Prod server separately but now would like to use a centralised architecture, i.e. Pulse installed on Prod and monitors both Prod and Dev.
I could only find a history migration article for v5 to v6 - Migrating Pulse v5.x history into Pulse v6.x - Cubewise CODE
Would this article apply to v6 to v6 history migration too?
plim
November 16, 2022, 12:21am
2
Hi @Sb5 ,
No that is not applicable for a v6 to v6 system migration and is currently not supported.
We will have to look into that, but in the meantime, could you help create an enhancement ticket for it?
Thanks!
Paul
jpaulo
February 2, 2023, 11:26pm
3
Hi All,
Something I tested and worked was restoring a backup from v6 to the same machine but in a different drive…so not exactly a migration. The steps were:
Backup Pulse folders as described in the documentation;
Uninstall Pulse v6.1.2 from drive C;
Install Pulse v6.1.3 in drive D;
Restore folders from backup.
As a result, license, config and history are all back.
plim
February 5, 2023, 11:27pm
4
Hi @jpaulo ,
Thanks for sharing these! Just a note though, this is only applicable if moving a single Pulse 6 server only to another folder / server.
Cheers!
Paul
1 Like