Specifying a remote Backup Server

Use the at server_name clause to send dump and load requests over the network to a Backup Server running on another machine.

Table 27-7 shows the syntax for dumping or loading from a remote Backup Server.

**Table 27-7: Dumping to or loading from a remote Backup Server**
	Backing up a database or log	Loading a database or log
	dump {database \| tran} database_name to [compress::[compression_level::]] stripe_device	load {database \| tran} database_name from [compress::]stripe_device
Remote Backup Server	[at server_name]	[at server_name]
	[density = density, blocksize = number_bytes, capacity = number_kilobytes, dumpvolume = volume_name, file = file_name] [stripe on [compress::[compression_ level::]] stripe_device [at server_name] [density = density, blocksize = number_bytes, capacity = number_kilobytes, dumpvolume = volume_name, file = file_name] ...] [with{ density = density, blocksize = number_bytes, capacity = number_kilobytes, dumpvolume = volume_name, file = file_name, [nodismount \| dismount], [nounload \| unload], retaindays = number_days, [noinit \| init], [notify = {client \| operator_console}] standby_access}]	[density = density, dumpvolume = volume_name, file = file_name] [stripe [compress::]stripe_device [at server_name] [density = density, dumpvolume = volume_name, file = file_name] ...] [with{ density = density, dumpvolume = volume_name, file = file_name, [nodismount \| dismount], [nounload \| unload], [notify = {client \| operator_console}] standby_access}]

Table 27-7: Dumping to or loading from a remote Backup Server

Backing up a database or log

Loading a database or log

dump {database | tran} database_name
to [compress::[compression_level::]] stripe_device

load {database | tran} database_name 
from [compress::]stripe_device

Remote Backup Server

[at server_name]

[at server_name]

[density = density,
blocksize = number_bytes,
capacity = number_kilobytes,
dumpvolume = volume_name,
file = file_name]
[stripe on
[compress::[compression_
level::]] stripe_device
[at server_name]
[density = density,
blocksize = number_bytes,
capacity = number_kilobytes,
dumpvolume = volume_name,
file = file_name] ...]
[with{
density = density,
blocksize = number_bytes,
capacity = number_kilobytes,
dumpvolume = volume_name,
file = file_name,
[nodismount | dismount],
[nounload | unload],
retaindays = number_days,
[noinit | init],
[notify = {client | operator_console}]
standby_access}]

[density = density,
dumpvolume = volume_name,
file = file_name]
[stripe 
[compress::]stripe_device
[at server_name]
[density = density,
dumpvolume = volume_name,
file = file_name] ...]
[with{
density = density,
dumpvolume = volume_name,
file = file_name,
[nodismount | dismount],
[nounload | unload],
[notify = {client | operator_console}]
standby_access}]

Sending dump and load requests over the network is ideal for installations that use a single machine with multiple tape devices for all backups and loads. Operators can be stationed at these machines, ready to service all tape change requests.

The following examples dump to and load from the remote Backup Server REMOTE_BKP_SERVER:

dump database pubs2 to "/dev/nrmt0" at REMOTE_BKP_SERVER

load database pubs2 from "/dev/nrmt0" at REMOTE_BKP_SERVER

The server_name must appear in the interfaces file on the computer where Adaptive Server is running, but does not need to appear in the sysservers table. The server_name must be the same in both the local and the remote interfaces file.