Deciding how to enter the dump command

About entering the dump command

You can enter the dump command through a Remote Shell connection, such as through the rsh command, through a Telnet session accessing the filer console, or through the filer console directly.

Other than potential problems associated with any remote connection, console access through a Telnet session and direct console connection to the filer behave the same way.

Benefits of entering the dump command through a Remote Shell connection

Entering the dump command through a Remote Shell connection gives you these benefits:

When the dump command is in progress, you can still use the console to manage the filer. If the dump command entered on the console is backing up a large number of files, you cannot use the console for a long time.
You can start multiple dump commands through the rsh command.
Data ONTAP is less likely to inadvertently terminate the dump command, especially if it is run in the background from a Solaris system. If you enter a dump command on the filer console, it could be terminated by Ctrl-C entered on a host connected to the filer using a Telnet session.
You can automate filer backups through shell scripts and crontab entries.

Benefits of entering the dump command at the console

If you enter the dump command at the console, you can read and respond to screen messages and prompts displayed by the command. For example, the command might prompt you for another tape to complete the backup, whereas a dump command entered through a Remote Shell connection does not generate any messages when the command needs user intervention, and terminates instead.