Move, back up and restore
On About > Export & Import, you can pack the server's data into one zip file, called an export. Bring the export back in later to restore the same server, or import it into a new server when you move.
Only administrators can export or import. Anyone else sees "Only administrators can export or import server data."
What an export holds
You choose which areas go into an export. Each area shows its size and number of files.
| Area | What it holds | Ticked at first |
|---|---|---|
| Server settings | Ports, services, iPXE and boot security options. Only some are imported. See "Server settings" below. | Yes |
| Boot files | Boot folders, iPXE scripts, unattend files and WinPE updates. | No |
| Operating systems | WIM, ISO and VHDX images, and Linux releases and installs. Often the largest area. | No |
| Drivers | Driver packs, downloaded catalogs and your own drivers. | No |
| Automations | Workflows and scripts. | Yes |
| Autopilot | Autopilot settings. | Yes |
| Known clients | The known client list and Active Directory sync settings. | Yes |
| Reroute | Reroute rules, machine groups and hit counts. | Yes |
| Email and alerts | Sending addresses and email alerts, with their sign ins. | Yes |
| Credentials and SDDN servers | Saved credentials and SDDN servers, with their passwords. | Yes |
| Client themes | Themes shown on PE clients. | Yes |
| Logs | Server, client and Linux install logs, and deployment history. For support only. Logs are never imported. | No |
Note
Boot files, Operating systems and Drivers are not ticked at first, as they are often very large. They are not left out. Tick them to bring your boot folders, images and drivers with you.
Server settings
An import only brings in the settings that mean the same on any server. These are the config.xml settings ClientPort, EnableHTTPServer, AutoLearnKnownClients, PausedServices, OperatingSystemsShareEnabled, DriversShareEnabled, MinimumBootSvn, UseServerBootManager, IPXEEnabled, IPXEDefaultFirstStage and LoadWIMIntoMemory.
IPXEBootFolderX64 and IPXEBootFolderArm64 are only brought in if you also import Boot files, as they point at boot folders.
The server that imports keeps its own folders, IP address, host name, certificate and Windows ADK paths.
What an export leaves out
These are never in an export:
- Users and their passwords, and the sign in settings. Set these up again on Admin > Users and Admin > Settings.
- The activity log on Admin > Activity, and its settings.
- The licence and its activation. See "The licence when you move" below.
- The server's certificate.
- The PE client itself. Only its themes are in the export, in Client themes.
- Updates the server has downloaded.
Lock the saved passwords
Credentials and SDDN servers and Email and alerts hold saved passwords and email sign ins. If you tick either one, a box shows: Lock the saved passwords with a password (optional).
| Choice | What happens |
|---|---|
| No password | The saved passwords only work if the export comes back to the server that made it. On any other server, you must enter them again. |
| A password | Enter the password when you import, and the saved passwords work on any server. |
The password needs at least 8 characters. Type it in Password and again in Password again.
Important
The password is not kept anywhere. Keep it safe. Without it, the saved passwords are imported blank.
If you move to a new server, use a password.
Make an export
- Go to About > Export & Import.
- Under Export server data, tick the areas you want. You can also use Select all or Select none. To measure the areas again, select Refresh sizes.
- If the password box shows, enter a password if you want one. See "Lock the saved passwords" above.
- Select Export. A bar shows how far it has got. To stop, select Cancel.
- When the export is ready, select Download and choose where to save it on this PC. To stop the download, select Cancel download.
The server keeps running while it makes the export.
Where the export goes
The server first makes the export on its own disk, in this folder:
C:\ProgramData\SharpDay\SharpDay Deploy\Transfers
The file is called SharpDay Deploy export <server name> <date> <time>.zip. Only administrators on the server can open this folder.
The server keeps 1 export. A new export replaces the one before. To delete the copy on the server, select Remove from server.
Download copies the file to the PC the Console runs on. Keep it somewhere safe, as it holds your server's settings.
Disk space
The server needs room in its Transfers folder for the whole export, plus 256 MB. Images and driver packs hardly get smaller in a zip, so plan for their full size. The Console shows how much is free there.
Warning
The Transfers folder is on the system drive. An export with images and drivers can need a lot of space on that drive.
If there is not enough room, the export stops and nothing is kept. Untick the larger areas, such as Operating systems or Drivers, or free up space.
The PC you download to also needs room for the whole file.
Restore on the same server
- Go to About > Export & Import.
- Under Import server data, select Choose export file... and choose the
.zipfile. The Console sends it to the server. - The server checks the file. It shows which server made it, its version and when. Read any warnings.
- Every area in the file is ticked. Untick any you do not want.
- If the file's saved passwords are locked, enter the password in Password for the saved passwords. Leave it empty to import without the saved passwords.
- Select Import and restart.
- The Console asks you to confirm. Tick "I understand that what I chose will be replaced by what is in this file." and select Import and restart.
To throw the file away instead, select Discard file.
What the import does
- The server backs up its own data folder.
- It unpacks the areas you chose. To stop, select Cancel. Nothing on the server is changed, and you can start again.
- It restarts. This stops any deployments in progress.
- As it starts, it moves the unpacked files into place.
Consoles connect again once the server is back. About > Export & Import then says how the import went. Select Dismiss to clear the message.
Files in the export replace files of the same name on the server. Nothing else is removed.
Warning
The backup only covers the server's data folder, which holds its settings. It does not cover the share folder. If you import Boot files, Operating systems or Drivers, files of the same name are replaced and no copy is kept.
The backup goes in a folder named with the date, the time and "before import", here:
C:\ProgramData\SharpDay\SharpDay Deploy\Backups
The server keeps the newest 5 backups.
If the import does not go ahead
| What you see | What to do |
|---|---|
| "That password does not open the saved passwords in this export." | Check the password, or leave it empty to import without the saved passwords. Nothing was changed. |
| "There is not enough disk space to import this" | Untick the larger areas or free up space. Nothing was changed. The server needs room for the file in its Transfers folder, and room again where each area is unpacked. |
| "That export was made by a newer version of SharpDay Deploy" | Update this server, then import the file again. |
| A warning that the file was made by a newer version | You can import it. If anything looks wrong afterwards, update this server. |
| "Restart the SharpDay Deploy service to finish it." | The server could not restart itself. Restart the SharpDay Deploy Service service. Until you do, no other export or import can start. |
Only 1 export or import can run at a time.
Move to a new server
- On the old server, make an export. Tick every area you want to keep, including Boot files, Operating systems and Drivers if you want your boot folders, images and drivers. Lock the saved passwords with a password.
- Download the export.
- Install SharpDay Deploy on the new server. Use the same version as the old server, or newer.
- Connect the Console to the new server and make the first admin account. See First time setup.
- If the setup window shows the Licence step, add your licence file. See "The licence when you move" below.
- On New or import, choose Import from another server.
- On Import file, select Choose file and choose the export. Untick any areas you do not want, and enter the password.
- Answer the Share folder and Network steps for the new server. The import does not change these.
- On Review, select Finish setup.
The new server saves your answers, backs up its own data, unpacks the export and restarts. The last page of setup says how the import went.
If the import stops, setup goes back to Import file and says why. See "If the import does not go ahead" above.
After the move
- Add your users again on Admin > Users. See Users and roles.
- Set your sign in options again on Admin > Settings.
- Build your boot images again on the new server. Boot media built on the old server reach the old server and trust its certificate. See Build a Windows PE image.
- Point your DHCP at the new server. See DHCP options.
- If you made the export without a password, enter your saved passwords again on Automations > Credentials, Automations > SDDN Servers and Automations > Email.
The licence when you move
The licence is not in the export. Add your licence file on the new server, on the Licence step of setup. The server then activates it with the licence server, so the new server must be able to reach it. See Ports and firewall.
An activation is tied to the server's hardware. The server checks 3 things: the ID Windows gives it, its serial number and its network adapter. If fewer than 2 of them match, it counts as different hardware. This can also happen on the same server, if 2 of these 3 things change.
If the server says the licence is activated on different hardware, sign in at sharp.day, open your dashboard and select Clear Machine ID on the licence. Then add the licence file again. You can do this 3 times in 12 months.
For the full steps, see Activate your licence.