It's not just the bandwidth, if latency is high the backups will be dog slow. Whats the ping time to the host?
On 11 October 2011 21:08, Vandeventer, Harold [BS] < harold.vandeven...@da.ks.gov> wrote: > Thanks for the advice.... > > My only reason for considering compression is based on the fact this node > is about 60 miles away over a relativly slow link. I've asked the network > team what they expect for bandwidth, but don't have an answer yet. > > Otherwise, I'd planned to leave the "Solaris" option set details blank till > we figure out more about this node. > > > > -----Original Message----- > From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of > Zoltan Forray/AC/VCU > Sent: Tuesday, October 11, 2011 2:50 PM > To: ADSM-L@VM.MARIST.EDU > Subject: Re: [ADSM-L] First Solaris node > > Welcome to the world of mixed operating systems...... > > Don't take this the wrong way but what does the OS have to do with things > like compressability? Compressability is based on your data. For > instance, I have dozens of Notes/Domino servers that are both Solaris AND > Windows. Domino databases don't compress well or at all, so I don't. I > have hundreds of Windows servers that don't compress well due to the > application/data and then I have hundreds that compress very well....again > based on the data/application. > > I don't have any CLOPTSET for any Solaris or Linux servers. They usually > don't have problems with files being locked/exclusive access. But you may > be running an application that does. As to what you may want to exclude > from backups, that depends on how the server is setup and the application > running on it. Most of my non-Domino Solaris servers run Oracle and > therefore backup their databases using the TDP so the directories with the > actual Oracle database are excluded. > > It really is all about knowing your data. > > > > From: "Vandeventer, Harold [BS]" <harold.vandeven...@da.ks.gov> > To: ADSM-L@VM.MARIST.EDU > Date: 10/11/2011 03:33 PM > Subject: [ADSM-L] First Solaris node > Sent by: "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> > > > > I need to prepare my TSM environment (running on Windows) for it's first > Solaris client. All 400+ existing clients are Windows-based. > > Anyone have suggestions for setting any specialized Option Set values? > > My first thought is to have a "Solaris" option set, and leave most of it > blank. Probably set COMPRESSSION YES as this node is physically about 50 > miles away. > > Definitely don't hook them to an option set for Windows filters. > > Thanks.... Harold. >