Re: [Veritas-bu] Restore of exchange 2003 to exchange 2007 ?

Michael The Exchaneg Admin guide should cover the basics for the restore process. At least this is what I ended up using for Ex2k3. Sorry, not got Ex2k7 yet Regards Simon Weaver 3rd Line Technical Support Windows Domain Administrator EADS Astrium Limited, B23AA IM (DCS) Anchorage Road,

Re: [Veritas-bu] how can i back up NT4

I use 3.4 clients which work with 5.1 - I think your right, the older client should still work for NT Regards Simon Weaver 3rd Line Technical Support Windows Domain Administrator EADS Astrium Limited, B23AA IM (DCS) Anchorage Road, Portsmouth, PO3 5PU Email: mailto:[EMAIL PROTECTED]

Re: [Veritas-bu] Error 13

Dan Symantec product a troubleshooting guide for this code, which is worth looking into. It could be AV, 3rd party software creating I/O while backups are running, Network speeds or configuration. (even ports possibly, if the Server has moved). Regards Simon Weaver 3rd Line Technical Support

Re: [Veritas-bu] Upgrade to 6.5 or 6.0MP4

On 10/26/07, Dave Carpe [EMAIL PROTECTED] wrote: NetBackup 6.5 is huge feature release, not a Maintenance Pack for NBU 6.0. NBU 6.5 adds things like SAN Client, a new Open Disk API for better support of Storage and VTL's. When PureDisk 6.5 comes out, it will support PureDisk media servers,

Re: [Veritas-bu] Upgrade to 6.5 or 6.0MP4

NetBackup 6.5 was one of the major themes at Vision 2007 in Las Vegas this past June 12-14. All of the Vision presentations are available on the Symantec Technology Network here: http://www.symantec.com/enterprise/stn/vision/index.jsp Of special interest on NetBackup 6.5, I would point you to

Re: [Veritas-bu] VSP in 6.x

If I'm not mistaken VSS is only available on Windows 2003. Windows 2000 users are kind of up the creek. If you want the software installed the same way every time I'd recommend creating a .mst or modifying Symantec's .msi so it can only be installed one way. Software deployment FTW. =) I've

Re: [Veritas-bu] VSP in 6.x

Use VSS, not VSP and you won't have the issues in 6.0. We've instructed our Windows admins to always do a custom install and disable the VSS installation and let Windows do the snapshots. No more cache files. Now getting the Windows admins to actually follow the installation instructions and do

[Veritas-bu] VSP in 6.x

Has NBU 6.0 or 6.5 fixed the issue with the VSP Cache file becoming locked and not cleaning up after itself? This remains a common problem for me in 5.1 so we try not to use it. Thanks, Rusty Major, MCSE, BCFP Sr. Data Assurance Engineer (281) 584-4693 VeriCenter, Inc.

Re: [Veritas-bu] VSP in 6.x

That idea works very well if your Windows clients are all running Win2k3. If they're still running Win2k, though, you must use VSP (or simply accept not having WOFB). Though there are a variety of pieces of software that can cause the VSP file lockups, I see it most frequently with Symantec

[Veritas-bu] enhanced vmoprcmd

All - Not sure if anyone is actively using this (updated?) command in the NBU 6x environment. If you are not, you might want to look at it, and if you are, maybe you can shed some more light. This could come in handy for automating drive down, pending request notification, etc. which is what I

Re: [Veritas-bu] VSP in 6.x

Rusty, Make sure you virus scan is set to ignore .VSP file. VSP will be required of W2K servers; whereas, VSS should be used on W2K3. Thanks, Rockey J. Reed You're not obligated to win. You're obligated to keep trying to do the best you can every day. Marian Wright Edelman