Cisco Server Provisioner 6.6 User's Guide ("Chuck Berry")

Imaging Control File Locations

Hide Navigation Pane

Imaging Control File Locations

Previous topic Next topic No expanding text in this topic  

Imaging Control File Locations

Previous topic Next topic JavaScript is required for expanding text JavaScript is required for the print function Mail us feedback on this topic!  

 

Image Control File Locations: For each system to be imaged, control files exist to force the client system to take appropriate actions based on the User’s requests.

You can locate these files at:

[root@baremetal ~]# cd /home/tftpboot/pxelinux.cfg

When a new Imaging profile is created, 2 files get created, containing directives for backup and for restore.

-rw-r--r-- 1 root root  465 Mar  6 04:34 01-00-02-55-b0-97-a8.backup

-rw-r--r-- 1 root root  465 Mar  6 04:34 01-00-02-55-b0-97-a8.restore

When the IT user clicks on a System’s “Next Action” icon, a third file active appears.

-rw-r--r-- 1 root root  465 Mar  6 08:34 01-00-02-55-b0-97-a8.active

-rw-r--r-- 1 root root  465 Mar  6 04:34 01-00-02-55-b0-97-a8.backup

-rw-r--r-- 1 root root  465 Mar  6 04:34 01-00-02-55-b0-97-a8.restore

If the user clicks “Backup”, then the Provisioner PXE Server copies the file backup to active.

If the user clicks “Restore”, then the Provisioner PXE Server copies the file restore to active.

If the user clicks “Reset”, then the Provisioner PXE Server deletes the file active.

After an imaging (backup or restore) event, then the Provisioner PXE Server deletes the file active.

If there is no file “active”, no action is taken. If there is a file “active”, its contents will dictate the type of imaging action.

No backup directories are created until the first backup for that directory name occurs.