Discussion:
Dump database across network
(too old to reply)
Jan
2008-12-09 20:01:21 UTC
Permalink
Raw Message
Using ASE 12.5.2 on Windows 2000 OS. Running low on hard
drive storage space due to its reallocation by/for another
contractor.

Can/should I modify database dumps to target a mapped drive
across the network (instead of the local server's drive)?

What cautions/risks?

TIA,
Jan
Derek Asirvadem
2008-12-10 03:35:30 UTC
Permalink
Raw Message
No problem at all.
Just longer dump/load times due to going across the network.
In case a load db is required, the network drive better be accessible.

BTW your dumpfiles shoul not be on the same set of physical disks as
you database (for both performance and recovery reasons); if they are,
they will be slow; dumping to a network drive may be faster.
--
Cheers
Derek
Senior Sybase DBA / Information Architect
Copyright © 2008 Software Gems Pty Ltd
Quality Standards = Zero Maintenance + Zero Surprises
Performance Standards = Predictability + Scaleability
Jan
2008-12-23 17:52:37 UTC
Permalink
Raw Message
Thanks for the advice. Am only here 1 day a week so took a
while getting back to you.

Parameters are not under my control under current contract;
have to work under those imposed by another contractor.

Thanks again,
Jan

Peter Collard
2008-12-13 15:37:09 UTC
Permalink
Raw Message
Post by Jan
Using ASE 12.5.2 on Windows 2000 OS. Running low on hard
drive storage space due to its reallocation by/for another
contractor.
Can/should I modify database dumps to target a mapped drive
across the network (instead of the local server's drive)?
What cautions/risks?
TIA,
Jan
Another option is to use a backupserver on another machine as well as your
own - the two backupservers will transfer the backup to a remote machine.

I've used this extensively to consolidate backups on a central machine and
never had any issues with it, apart from it being slower than direct to
disk.

Have a look at the dump database syntax.
Loading...