Backing up the K2000 Systems Deployment Appliance isn’t difficult; however, it is quite different from backing up your K1000 Appliance- if you happen to own both. It’s a bit of a manual process at first, but once you’ve defined the items inside the K2000 which require backing up, configuring the K2000 appliance to off-board them is very simple.
It’s a 2 step process:
- Identify and schedule which items you’d like to export out of the K2000 database. There are 2 methods for exporting. A one-time only export for freeing up disk space on an appliance that’s tight on disk space (the item is completely removed from the database) or a regularly scheduled export (leaves a copy of said item inside the database and places a copy of the item(s) on a Samba share for offboarding. The items are exported to a Samba share called ‘Restore’. Think of it as a staging area for the offboarding process.
- Schedule the file copy process. This is the process that the K2000 will use to move those exported items to another location on your network where true backup occurs (tape backup, volume snapshots, online backup, etc). The offboarding process can leave copies of these files on the Restore share or you can configure it to ‘clean up’ (delete) the items from the Restore share after the copy process is complete.
It would be a real loss if you spent hours creating your images, post-installation tasks, etc., only to lose them in the event of a disaster and have to recreate them. If you are not backing up your K2000 on a regular basis, please visit this FAQ for an easy-to-follow step-by-step procedure:
Tight on disk space for backups? Consider switching to offboard storage:
Always remember, your backups are only as good as the data being backed up. Be sure to *test* your backups and ensure they are viable. Disaster Recovery is not the time to discover that your backups were incomplete or corrupted.