Distribute backup on multiple disks

I know ew can distribute backup files on multiple disks.
is there a way to specify the size also ? to illustrate :
my backup size is 105 GB. I want to specify to save xGB on
Disk1 and rest on disk2 . Is it poosible ? Any hellp will
be highly appreciated>--Original Message--
>I know ew can distribute backup files on multiple disks.
>is there a way to specify the size also ? to illustrate :
>my backup size is 105 GB. I want to specify to save xGB
on
>Disk1 and rest on disk2 . Is it poosible ? Any hellp will
>be highly appreciated
>.
>
Reply:
Opps on that last reply, you said backup files, and I was
thinking database files. Sorry about that.|||When you strip your backup to multiple files, these files seem to be of
similar size. As the result, you can take advantage of this observation. For
instance, if you want about 34GB on disk1 and the other on disk2, you can
issue the following:
BACKUP DATABASE <yourDB> to disk='DiskDrive1\yourDB.bak',
disk='DiskDrive2\yourDB1.bak',
disk='DiskDrive2\yourDB2.bak'
--
Linchi Shea
linchi_shea@.NOSPAMml.com
"Debasish" <debasish.paul@.karma-group.com> wrote in message
news:09aa01c38216$e87a5ad0$a101280a@.phx.gbl...
> I know ew can distribute backup files on multiple disks.
> is there a way to specify the size also ? to illustrate :
> my backup size is 105 GB. I want to specify to save xGB on
> Disk1 and rest on disk2 . Is it poosible ? Any hellp will
> be highly appreciatedsql

Distibution servers ...

So what happens when the Distribution Server blows a gasket? Somehow I get
the feeling that restoring from last nights backup isn't going to get things
back to normal? I ask because we are going to build a replication solution
that will fall under Sarbanes Oxely issues, one of which is documented
business continuity plans. Our solution will likely have a dedicated
distribution server and even though we haven't even budgeted hardware yet, I
am having visions of a major meltdown and a trip to the mental ward.
P.S. to Hilary Cotter. I think your replication book is great. I would
suggest that a follow up title would be a book (or additional chapters in a
new edition) that deal with such questions as replication headaches during
recovery and restoration. At least from personal experience, our worst days
as IT people are when we are under the gun to restore failed services.
Bob Castleman
DBA Poseur
Nope. Basically you need to cluster your distributor and hope for the best.
There is a kb article which describes how to recover from this.
http://support.microsoft.com/default...b;en-us;886839
I am working on an article of my own explaining how to do this.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Bob Castleman" <nomail@.here> wrote in message
news:uzw0o4EcFHA.3204@.TK2MSFTNGP12.phx.gbl...
> So what happens when the Distribution Server blows a gasket? Somehow I get
> the feeling that restoring from last nights backup isn't going to get
things
> back to normal? I ask because we are going to build a replication solution
> that will fall under Sarbanes Oxely issues, one of which is documented
> business continuity plans. Our solution will likely have a dedicated
> distribution server and even though we haven't even budgeted hardware yet,
I
> am having visions of a major meltdown and a trip to the mental ward.
> P.S. to Hilary Cotter. I think your replication book is great. I would
> suggest that a follow up title would be a book (or additional chapters in
a
> new edition) that deal with such questions as replication headaches during
> recovery and restoration. At least from personal experience, our worst
days
> as IT people are when we are under the gun to restore failed services.
>
> Bob Castleman
> DBA Poseur
>
|||Thanks for the reference.
In your book there is mention of a second volume for merge replication. Is
this still in the works? Is there a publication date?
Thanks,
Bob
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:uy11nLFcFHA.720@.TK2MSFTNGP15.phx.gbl...
> Nope. Basically you need to cluster your distributor and hope for the
> best.
> There is a kb article which describes how to recover from this.
> http://support.microsoft.com/default...b;en-us;886839
> I am working on an article of my own explaining how to do this.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "Bob Castleman" <nomail@.here> wrote in message
> news:uzw0o4EcFHA.3204@.TK2MSFTNGP12.phx.gbl...
> things
> I
> a
> days
>

Displaying Backup file locations

Hi,

I have an application that I want to allow a user to backup their sql 2005 database. I use the SMO classes to actually perform the backup, but my application can run on a client machine, not just the database server. As I allow the user to select the location for their backup I would really like to show a folder list of server locations, not local (i.e. client) folders.

Basically I wondered if there were any UI objects available for Sql 2005 ( in the SMO namespaces perhaps), something that will display a list of server folders and could be used from a client machine.

Thanks for your help

Graham

You can get the server's default backup directory within SMO from the server's .Settings.BackupDirectory property. You should be able to find other directories using WMI queries, I'd think.

|||As Allan said, this is done through WMI.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de