Search results for query: *

Filer = a SAN attached disk sub-system. (i.e. NetApp, EMC, Hitachi). Expressions within the policy = Wildcards within the backup selection tab on the policy. We opted to use a standard Windows-NT policy and capture the flat files from the filer. The DBA's would dump their DB's to the filer...

We ran into this same issue. Jobs that only depicted a Job ID. VSupport recommended the following, and it fixed the issue: Bring NBU down on the master. Go into the following directories and delete all the files: Unix: /usr/openv/netbackup/bin/bsched.d /usr/openv/netbackup/bin/bprd.d...

No, each policy is independent. You could use the exclude lists on the client, and specify the different schedules to skip certain file systems. Bob

/usr/openv/volmgr/bin/tpconfig This will allow you to add the tape drive. Thanks, Bob

You can add an entry to the bp.conf file on a Unix server: CLIENT_READ_TIMEOUT = 900 ** Default is 300 ** On a Windows server it is changed on the Host Properties > Master Server > Timeouts. Hope this helps, Bob Thanks, Bob

Has the media been written to?? If there is data on the tape that has not expired, the media will not be able to be moved to a different volume pool. Run the following to see if the tape has a 'Time Assigned': Unix: /usr/openv/volmgr/bin/vmquery -m <tape_ID> Windows...

Back in the 3.4 days, we attempted the SQL agent (patch 645). Our DBA's didn't like the restart procedure and opted to dump the DB's to flat files. We now use a filer to dump the DB's to, and place them in dated folders. We then use expressions within the policy to do forever-incremental...

Quite a dilemma! Active Directory server crashed, and had to be rebuilt. In doing so, new domain was created. Servers and desktops had to be dropped into a workgroup, and then added to the new domain. NBU server did NOT like this scenario, and is now having MAJOR problems. All components...

http://tc5.iponet.net/en-us/assistance/HA011394511033.aspx This should help. Someone else posted a similar question, and had this as a reply...........so in short, it is not my expertise. Credit goes to jimp56. :>) hth.......... Thanks, Bob

Here is a thought.......... If this is a work (Corporate) laptop, your default save folders may be directed to a HomeSpace server at your company's location. And each time any Office application does anything with a file, it has to sense all the drives (partitions or shares) associated with...

Have you installed any of the previous SP's???? Thanks, Bob

The second location listed above c:\documents and settings\username\application data\microsoft\ is the default for AutoRecover. This option is located under Tools > Options > Save Tab. Is this something that didn't close properly?? Thanks, Bob

Hey Mickey, Not sure which one you are trying to install. The title says Office 2000 SP3, and the body of the question says SP@ for Office 2003. Thanks, Bob

Have you uninstalled, rebooted, and then reinstalled??? 98 needs a reboot for EVERYTHING. hth.......... Thanks, Bob

I would submit a issue with Microsoft. However, they are probably going to tell you to upgrade to Office 2003 completely. The application is obviously having issues with the install of Outlook 2003. Try installing the assistant from 2003. hth............. Thanks, Bob

Have you tried copying the file to another location, and then opening it?? Perhaps it is having an issue with the space between the firstname and lastname of the folder. hth............. Thanks, Bob

Is this XLSTART folder inside your My Documents folder??? Thanks, Bob

Have you checked your default save location??? Tools > Options > General Tab > Default File Location. hth...... Thanks, Bob

After further investigation, I don't even see the "work items" toolbar in my Excel. Was that add-on??? And when you say 'document' do you mean a spreadsheet or an actual Word document??? Thanks, Bob

Perhaps a stupid question, but here goes. How are you closing Excel?? Using the X in the top-right corner, or choosing File > Exit??? Some configurations do not take when you exit using the X to close the application. Just a thought...... Thanks, Bob