[Networker] Telnet failed
2011-11-05 06:23:47
Using IP addresses in general is fine - as long as they do not change. That's
the reason why the name resolution must perfectly work.
In other words: If the FW is not the issue then the problem must be the name
resolution.
With respect to individually listed save sets:
You do this when you do not want to backup everything or additional network
paths which are not covered by the "All" alias. In general you have the choice
to declare the list in either way:
- Use "All" for all local hard disks partitions and OS specific SSs and use
directives for exclusions
- Use an individual SS list when this would be shorter and/or the data has to
be backed up by a special procedure
You can even have more than one client resource in this case.
One simple example:
- File system backup client
Save Set: All
Directive: 'skip the DB files'
Backup Command: ---
- DB backup client
Save Set: /db_directory
Directive: ----
Backup Command: save_db_script
+----------------------------------------------------------------------
|This was sent by carsten_reinfeld AT avus-cr DOT de via Backup Central.
|Forward SPAM to abuse AT backupcentral DOT com.
+----------------------------------------------------------------------
To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the body of the email. Please write to
networker-request AT listserv.temple DOT edu if you have any problems with this
list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
|
|
|