Backup & Restore Altiris server (Basic)

[Migration User]

Hello, Is there any white paper that describe how to backup and restore Altiris server? Many thanks for the help.

[Migration User]

I'm also looking for white paper on how to back up and restore. Any advise/help would be appreciated.

[Migration User]

I recenly was appointed the task of setting up a test server (sandbox) I hope this helps. I started off by: 1. Researching how to do a clean install of Altiris on a new (virtual) server. 2. Installed IIS, .Net and VMWare tools on the new Altiris server. 3. Researched where to download NS. 4. Proceeded to install NS. 5. Installed roughly 80 Altiris components and solutions. 6. Tested and configured several components. 7. Imported and synced AD information into Altiris. 8. Contacted Symantec to retrieve licensing information for Altiris. 9. Imported licensing info into Altiris. 10. Created and assigned schedules to update AD info automatically for new Altiris server. Once you install NS you can can choose to either attach old DBs or have Altiris create new ones.

[Migration User]

Your disaster recovery strategy depends on the design of your Altiris Implementation.

You want to make sure you have good recurring backups of the Altiris Database(s) - including the incidents database if you have the help desk solution.

If disaster strikes, you can re-install Altiris and point it to the existing database during the install and this will get you back up and running.

Refer to the following link for Disaster recovery planning-

https://kb.altiris.com/display/1/kb/article.asp?aid=22485&n=2&s=

Note:::

When an Altiris solution is installed, the installation consists of two parts:
 

• The MSI installation creates and populates the file system (folders/files) and then it writes the required entries in the registry.
• AeXConfig.exe is launched with the /configure switch; this command is used to import the database schema and the objects into the configured Notification Server database.

Note: When solutions are installed and then configured, any existing solution specific data in the database will be overwritten.

When Notification Server is installed as a Disaster Recovery process, and when an existing database is required to be used, we recommend using the following recovery process:

IMPORTANT: The new Notification Server and installed solutions need to be taken to the same "product and version state" as was the old Notification Server

1. Install Notification Server (verify the version that needs to be installed) and configure it to use a temporary database—generally it is advised to use a name other than Altiris since this may be the name of your existing database.
2. Apply all Notification Server services packs or hotfixes that were previously used (version state is very important).
3. Install only the solutions used with the old Notification Server (product state and version state are very important).
4. Once the new Notification Server and installed solutions are in the same product and version state as was the old Notification Server, go to the Configuration tab of the NS Admin Web console and use the Database Settings option to point Notification Server to the existing database
5. Go to Add or Remove Programs, select Altiris Notification Server and run the repair option.
6. (OPTIONAL) Replace the CoreSettings.config file on the new Notification Server with the most recent CoreSettings.config file from the old Notification Server as this file is essentially the registry of the Notification Server.
7. Restart Notification Server, and the database should be aligned to the SID and the pre-existing roles

Note: The above steps will preserve all custom items created on the original Notification Server and stored in the original database (and CoreSettings.config file).