> If Sybase has remote raw partition capability or utility, great. Doing
> a dd|ssh "remote tape device" is questionable.
Doing a dd is questionable with Sybase.
Quote:> Don't have much experience with raw partitions.
That comes as no surprise.
Quote:> Why not run with filesystems?
Why run them?
Quote:> They'er easier to backup,
Quote:> monitor for space and utilization using the standard UNIX toolset,
If I was anything like Guy Polis, I'd be laughing at you in
histrionics now. This comment is meaning less with Sybase.
You allocate its devices and it uses the space within them.
They don't grow by themselves.
Quote:> and I've not seen that you don't really get that much of a
> performance gain with raw filesystems. That, admittedly, was with
> Oracle, but think about how you're going to monitor and backup this
> system. Have you got existing tools or are you going to have to write
Sybase has a backup server. And comparing Sybase to Orable
is akin to the proverbial apples and oranges.
Quote:> Also, unless you have a tape robot and commercial backup software that's
> going to do the backups, slice the Sybase disk into partitions that will
> fit on a single tape. Multi-volume raw partition backups are really
> very hard to do.
What are you talking about? This is totally meaningless in
the context of Sybase.
Quote:> Since most backups are done with the filesystem tools rather as a raw
> partition dump, I would suspect NOT. If this system has important data
> and needs backups, BUY A TAPE DRIVE.
Sybase's backup server supports remote backups and restores.
Quote:> Or perhaps the data isn't worth it?
Doesn't look like your reply was.
Quote:> Do you feel lucky? Well, do you?
Looks like you were out of luck on every point.
Quote:> If this system is of any importance, don't be cheap when it comes to backups.
Having a clue would be a more worthwhile start.
Quote:> A sysadmin is only as good as their last backup...
Better start checking yours then.
-am ? 2002