VERITAS Storage ExecTM Version 5.3
Last Updated: January 6th, 2005
This document contains release notes for Storage ExecTM and contains information that may not be in the Storage Exec Administrator's Guide. The information in this document is more current than information in the Administrator's Guide. If information in this file conflicts with the Administrator's Guide, the information in this file is correct.
For the most current information on VERITAS Software products and services, please visit our website at http://www.veritas.com/.
Contents
Licensing and Deployment
Storage Exec™ is now available in multiple editions that can be purchased to fit your environment:
Storage Exec offers storage quota management, file auditing, file blocking, and basic reporting capabilities. Add-on options allow you to extend the functionality of Storage Exec to remote Windows computers.
Storage Exec Small Business Server Edition offers the same functionality as the full product, but is installed on, and works with, Microsoft Small Business Server Premium and Standard Editions only.
Storage Exec QuickStart Edition is designed for single server environments and includes standard Storage Exec functionality such as storage quota management, file auditing, file blocking, and basic reporting capabilities. Add-on options and remote agents are not supported.
New Options and Agents
With new Storage Exec add-on options and agents, you can enhance the functionality of Storage Exec, as well as extend Storage Exec functionality to remote Windows computers.
Storage Exec Enterprise Administration Option provides integration with Microsoft’s Active Directory, which enhances reporting and enables global policies on multiple computers.
Storage Exec Advanced Reporting Option offers additional reports not available in Storage Exec, while also providing advanced report writing tools.
Storage Exec Network Appliance Option integrates with and uses ONTAP qtrees to provide quota management and reporting for Network Appliance Filers.
Storage Exec Remote Server Agent adds quota management, content filtering, and file blocking to a remote server. When used in conjunction with a Storage Exec Server, it allows administration from a remote console.
Storage Exec Remote Workstation Agent offers content filtering and file blocking for remote workstations running Microsoft Windows 2000 Professional and Microsoft Windows XP operating systems. When used in conjunction with Storage Exec Server, it allows administration from a remote console.
Enhanced Installation
With a completely redesigned installation program, Storage Exec makes it easier than ever to configure your systems. In addition, you can install the remote agents from the Administration Console to remote Windows computers across the network.
Information Desk-based Administration Console
Storage Exec now provides a new overview page that guides you through various Storage Exec tasks. The Storage Exec Information Desk offers links to commonly asked questions, configuration dialog boxes, and configuration wizards.
Advanced Configuration Wizards
Storage Exec includes new configuration wizards that are designed to simplify the configuration of Storage Exec in complex environments.
With the Enterprise Administration Wizard, you can configure a centralized repository for policy definitions and management. The Enterprise Administration Option leverages Microsoft Active Directory to enable the application of storage policies across the enterprise.
Using the Cluster Configuration Wizard, you can add Storage Exec resources to existing resource groups to provide high availability.
Integration with Backup Exec for Windows Servers
When using Backup ExecTM 9.1 or 10.0 for Windows Servers in your environment, Storage Exec seamlessly integrates with Backup Exec via Backup Exec SmartLinkTM. This integration enables you to immediately back up or archive data from Storage Exec reports using Backup Exec.
Microsoft Certified
VERITAS Storage Exec has been certified by Microsoft for Windows 2000 Server (Server, Advanced Server, and Datacenter) and Microsoft for Windows Server 2003 (Standard, Enterprise, and Datacenter Edition) platforms—assuring you the highest quality product, designed specifically to meet Microsoft's stringent demands for quality and reliability.
Quick Installation Guide
The Quick Installation Guide is a printed manual that is shipped with Storage Exec. One manual contains both English and Japanese versions of the document. The document provides the information you need to install Storage Exec. The Quick Installation Guide does not replace the Storage Exec Administrator’s Guide, which is available in electronic (PDF) format on the Storage Exec installation CD and in printed format from the VERITAS WebStore.
Removal of the report collector – Installing the report collection component separately is no longer supported. All report generation is now performed on the Storage Exec Server.
A report query can no longer be edited from within a report. You can edit the report query directly, or you can create a new report query, and then select the new query in the report.
Transparent policies.
User or group association in policies.
Storage Exec Installation Notes
During installation, when prompted to enter an account for Storage Exec to use as its service account, enter an existing account. If you specify a domain, you must enter an existing account.
When installing Storage Exec on Windows XP Professional Workgroup, you may get the error "The Credentials entered are not valid" even though the username and password are valid. This is a known issue with Windows XP. To fix this, edit the registry setting: KEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa and change ForceGuest=1 to ForceGuest=0.
If you encounter the following error when performing a remote installation:
"Attempting to connect to server <server name> failed with the following error: Unable to connect through Remote Install object. Will not check remote credentials"
Perform the following steps:
Cancel the current remote installation session.
Navigate to the directory path %ProgramFiles%\Common Files\VERITAS Shared
Remove the Read-Only file attribute from the following files:
becomreg.exe
becomutil.exe
ExecPush.exe
becombinder.dll
msvcr71.dll
Retry the remote installation.
If your computer has the Multilingual User Interface installed, you may receive the following error message when installing Storage Exec: The Windows Installer service cannot update the system file mfc42u.dll because the file is protected by Windows. You may need to update your operating system for this program to work correctly.
The mfc42u.dll file is language-specific. Storage Exec attempts to update the file because of language differences. The existing mfc42u.dll file on the computer is the correct file needed by the Storage Exec installation. There is no need to update the operating system. Click OK to continue with the installation.
When push installing the Remote Server Agent to an NT 4.0 machine and no one is logged on locally on the target server (that is, the Windows NT 4.0 machine is still sitting at the CTRL+ALT+DEL screen), the installation will appear to have been successful, but no files or services are installed.
You can now push install Storage Exec 5.3 remote agents to remote computers
while simultaneously upgrading a local Storage Exec 5.3 installation.
When making changes to a local Storage Exec installation such as upgrading from
an evaluation version of Storage Exec 5.3 or adding Storage Exec 5.3 options,
you can now select the options Remote Agent Install and Local Install
simultaneously from the Program Maintenance screen.
The Program Maintenance screen appears after you open Windows Add/Remove
Programs. Select VERITAS Storage Exec and then click Change.
If you try to push install to a Storage Exec 5.0 computer during an upgrade for a 5.3 Remote Agent or Administration Console, prompts are displayed on the remote computer that will not allow the push installation to continue. You must upgrade a 5.0 computer locally when installing the Remote Server Agent, the Remote Workstation Agent, or the Remote Administration Console.
When using the command line to install a remote agent as an evaluation version on Windows XP Professional and Windows 2000 Professional, only the Remote Workstation Agent can be installed.
When installing the Remote Workstation Agent or the Remote Server Agent as evaluation versions, the Remote Administration Console will also always be installed, even if it is not selected. However, the Remote Administration Console will not be installed on Windows NT 4.
You can only install Storage Exec to a remote computer from a local computer on which Storage Exec Server is installed.
During installation, the event log may show the error "Failed to connect to server. Error: 0x800401F0". This is a known issue and does not affect software functionality.
With no other file system filter drivers, the order of components on the filesystem stack will be File System (Ntfs, etc.), NmSvFsf.sys (over Ntfs only, not Fat), QaFilter.sys, and then FileScreenFilter.sys. Other products may have file system filter drivers which will be above, below or interspersed with these drivers, depending on their start types and load order groups. Storage Exec drivers have the following characteristics: FileScreenFilter Start:Manual (started by FileScreen service); QaFilter Start:Boot, Group: FSFilter Physical Quota Management; NmSvFsf Start:Boot, Group: FSFilter Infrastructure.
All Storage Exec drivers are file system filter drivers, so they commonly interact with the file systems. NmSvFsf.sys is a filter which provides services to QaFilter.sys. It has no user mode interaction. QaFilter receives Ioctls from the Quota Advisor service. It sends messages to the Quota Advisor service through a named pipe. FileScreenFilter receives Ioctls from the FileScreen Service. It reads configuration information from the SOFTWARE registry. It sends information to the the FileScreen service through a mailslot, and through a pagefile section.
Operating System
Storage Exec
Microsoft Windows Server 2003 family
Microsoft Windows Storage Server 2003
Microsoft Windows 2000 Server family
Microsoft Windows XP Professional Service Pack 1 or later
Storage Exec Small Business Server Edition
Microsoft Small Business Server 2003 Standard
Microsoft Small Business Server 2003 Premium
Microsoft Small Business Server 2000
Note: Please refer to the Storage Exec Software Compatibility List
(http://support.veritas.com/rd/se-compatibility.htm)
for a complete list of supported environments.
Network Appliance Filer
ONTAP 6.4 or later
Internet browser
Internet Explorer 6.0 or later
Processor
Intel Pentium, Xeon, or compatible
Memory
Storage Exec Server
Required: 256 MB RAM
Recommended: 512 MB (or more for better performance)
Storage Exec Server and Backup Exec Server integration
Required: 512 MB RAM
Recommended: 1 GB
Note: RAM requirements may
vary depending on operations performed, the options installed, and the
specific system configuration.
Virtual Memory Recommendations
20 MB above the Windows recommended size for total paging file size (total for all disk volumes)
To view or set the paging file size:
On Windows 2000, click Start | Settings | Control Panel. Double-click System, click the Advanced tab, and then click Performance Options. Click Change to reset the paging file size for all drives.
On Windows Server 2003 and Windows XP, go to Control Panel, double-click System, click the Advanced tab, and then in Performance, click Settings. Click the Advanced tab, and then in Virtual memory, click Change to reset the paging file size for all drives.
Installation Disk Space
195 MB (Storage Exec Server with no options)
225 MB (Storage Exec Server and all options)
Note: Disk space requirements may
vary depending on operations performed, the options installed, and the
specific system configuration.
Other hardware
Network interface card or a virtual network adapter device
CD-ROM drive
(Recommended) A mouse
(Optional for printer notification) Printer supported by Microsoft Windows
Remote Installation of the Storage Exec Remote Administration Console
Although push installation is the preferred method when installing the Storage Exec Remote Administration Console on remote Windows computers, you can also install the Remote Administration Console by physically moving to the remote computer and using the Storage Exec product CD.
Use the following steps to install the Remote Administration Console at the remote computer:
Move to a remote computer where you want to install the Remote Administration Console.
Insert the Storage Exec CD in the computer’s CD drive. The Windows Autorun feature automatically launches the Storage Exec Browser.
NOTE: If the Storage Exec Browser does not automatically appear, start the Windows Explorer and navigate to the CD drive containing the Storage Exec CD media. Double-click Browser.exe to start the Storage Exec Browser.
Select a language and then click OK.
Click Install Storage Exec.
Click Next to continue with the installation.
Select I accept the terms of the license agreement, and then click Next.
On the VERITAS Storage Exec Install Menu, select both Local Install and Remote Administration Console.
Click Next, and the Storage Exec Remote Administration Console installation begins.
When the installation completes, click Finish.
Click Exit.
These notes pertain to an upgrade of StorageCentral 4.1 and 5.x to Storage Exec 5.3.
To upgrade a Storage Exec evaluation version to a licensed version:
From the Windows Control Panel, select Add or Remove Programs, then select Storage Exec.
Click the Change button and then click Next.
Select Additional Options and Serial Numbers and click Next.
Enter the serial numbers and click Add. Click Next three times and then click Finish.
Storage Exec 5.3 does not support transparent policies. Any transparent space allocation policies or file blocking policies that existed in StorageCentral 4.1 or 5.x will be converted to regular policies during the upgrade to Storage Exec 5.3.
In StorageCentral 5.x, if you created an allocation policy and associated it with a group, after upgrading to Storage Exec 5.3, this association is no longer available. You must specify the policy in Storage Exec 5.3 that was previously associated with the group when you create or modify managed resources for the group.
StorageCentral 5.x supported policies containing both space allocation and file blocking properties. Storage Exec 5.3 supports space allocation policies and file blocking policies, but not policies with a combination of space allocation and file blocking properties.
When upgrading from StorageCentral 5.x, the following will happen:
StorageCentral 5.x policies having only space allocation properties will be copied to the list of Storage Exec 5.3 space allocation policies.
StorageCentral 5.x policies having only file blocking properties will be copied to the list of Storage Exec 5.3 file blocking policies.
StorageCentral 5.x policies having a combination of space allocation and file blocking properties will be copied to the Storage Exec 5.3 space allocation policy list and to the 5.3 file blocking policy list. This may result in policies having inappropriate names. For example, say there was a 5.x policy named “250MB Limit with No Media Files” that had both space allocation and file blocking properties. The upgrade procedure...
Will create a 5.3 space allocation policy with this name that enforces a 250MB disk space quota but does not contain any file blocking properties
Will create a 5.3 file blocking policy with this name that prevents users from storing media files, but does not contain any space allocation properties
After you upgrade to Storage Exec 5.3, review the lists of space allocation and file blocking policies. You may need to rename some policies to better reflect what they now do.
StorageCentral 5.x came with a policy named "500MB limit in 250MB increments" and Storage Exec 5.3 comes with a policy named "500MB limit with a 250MB increment." These two allocation policies have the same properties. Assuming "500MB limit in 250MB increments" still exists on your system and has not been modified, the two policies will be identical after the upgrade.
StorageCentral 5.x came with two report queries named “Files With ACL” and “Space By Folder Object.” (In 5.x, report queries were called report definitions.) Storage Exec 5.3 comes with two related report queries named “Files With ACL Properties” and “Space By Folder Resource.” Each of the 5.x report queries has the same properties as its 5.3 counterpart. Assuming the two 5.x report queries still exist on your system and have not been modified, they will be identical to the two respective 5.3 report queries after the upgrade.
StorageCentral 5.x came with two reports named “Large Folder Object Summary” and “Space By Folder Object Summary.” (In 5.x, reports were called report sets.) Storage Exec 5.3 comes with two related reports named “Large Folder Resource Summary” and “Space By Folder Resource Summary.” Each of the 5.x reports has the same properties as its 5.3 counterpart. Assuming the two 5.x reports still exist on your system and have not been modified, they will be identical to the two respective 5.3 reports after the upgrade.
When the Enterprise Administration Wizard is run after upgrading from StorageCentral 5.x Standard Edition to Storage Exec 5.3 with the Enterprise Administration Option, policies stored locally are copied to the Active Directory the first time you run the wizard, and these policies continue to be associated with managed resources.
If multiple computers running StorageCentral 5.x Standard Edition will be upgraded, you must first copy StorageCentral policies from all computers to the first computer that will be upgraded to Storage Exec 5.3 before running the Enterprise Administration Wizard. This ensures that all policies will be copied to the AD and will be available to all computers in the domain that are upgraded to Storage Exec 5.3 with the Enterprise Administration Option.
Policies having the same name should not exist on separate computers, or the local computer and the Active Directory, before upgrading from StorageCentral 5.x Standard Edition to Storage Exec 5.3 with the Enterprise Administration Option, or when adding the Enterprise Administration Option to Storage Exec Server.
There are two scenarios in which the problem occurs:
Upgrading StorageCentral 5.x Standard Edition to Storage Exec 5.3 with Enterprise Administration Option
Adding Storage Exec 5.3 Enterprise Administration Option to a Storage Exec 5.3 Server
When the Enterprise Administration Wizard is run after upgrading to Storage Exec 5.3 with the Enterprise Administration Option, policies stored locally are copied to the Active Directory the first time you run the wizard, and these policies continue to be associated with managed resources. This happens when Storage Exec or StorageCentral policies don’t already exist in the Active Directory. If policies having the same name exist on other computers that are upgraded, managed resources on those computers will now be associated with the first policy by that name that was upgraded to Storage Exec. If this is the case, after the upgrade the managed resource from the second computer has settings different than the policy it was originally associated with.
In the second case, if StorageCentral or Storage Exec policies already exist in the Active Directory when the Enterprise Administration Wizard is run, then the wizard will update policies in managed resources with policies of the same name as found in the AD. Policies in the AD may have different settings than the local policies the managed resources were associated with before. After the wizard runs, managed resources will be associated with a policy of the same name as before but the settings in the managed resource will not match the settings of the policy in the AD.
To prevent this issue from occurring in either case, check to make sure that policies having the same name but different settings do not exist on separate computers, or the local computer and the AD before adding the Enterprise Administration Option. If such policies are found, they can be renamed prior to adding the Enterprise Administration Option.
If a managed resource is inadvertently associated with the incorrect policy during the upgrade, you can correct the situation by reapplying the correct policy to the managed resource.
Do not delete files in the %TEMP% folder (%SYSTEMDRIVE%\Documents and Settings\%USERNAME%\Local Settings\Temp) after installing StorageCentral 5.0 or 5.1. This temporary folder contains files the 5.0 or 5.1 installer requires for upgrade or uninstallation. If these files are deleted, or if this folder is deleted, upgrade from StorageCentral 5.0 or 5.1 to Storage Exec 5.3 will fail.
Auto detect users no longer supports user or group association. After upgrading from StorageCentral 5.x to Storage Exec 5.3, Auto detect users managed resources will no longer apply to multiple policies. Review the specified policy to make sure it applies to all users and make adjustments to the policy as needed.
All policies propagate changes after upgrading to 5.3. Any new managed resources created with a policy in Storage Exec 5.3 will receive modifications from the policy when they are made to the policy itself.
After upgrading from
StorageCentral 5.2 for Network Appliance Editions to Storage Exec 5.3 with
Network Appliance Option, you must re-add the NetApp Filer or Filers to
the NetApp proxy on the Network Appliance tab.
In StorageCentral 4.1, if options to activate an alarm both below a threshold and above a threshold were selected, then the option to activate below a threshold is selected after upgrading to Storage Exec 5.3.
The status for reports that were scheduled in StorageCentral 4.1 changes to 'Immediately' after upgrading to Storage Exec 5.3.
The following reports that
were available in StorageCentral 4.0 are not supported in Storage
Exec 5.3:
- Wasted Space Report
- Usage by Share
The report to Generate Alarm Action that was available in StorageCentral 4.1 is not supported in Storage Exec 5.3.
Reports that used the StorageCentral 4.1 Trend databases are not supported in Storage Exec 5.3.
When upgrading from StorageCentral 4.1, if a report set contains more than one report, only the properties of the first report are converted to report set properties in Storage Exec 5.3.
When managing a computer that has StorageCentral 5.x Standard Edition installed, from a Storage Exec Server that has the Advanced Reporting Option installed, the wizards and functionality from Storage Exec 5.3 will be available. However, to view the computer audit trail on the StorageCentral 5.x Standard Edition computer, you must upgrade the computer to Storage Exec 5.3. Also, to use the DBF output format, you must start StorageCentral 5.x locally, and then select DBF. If you had associated a space allocation policy to a user or group, this policy association will not be available.
This section contains notes regarding these topics:
Enterprise Administration Option
When running the Enterprise Administration Wizard, you must be an administrator on the domain in which you are populating and adding remote agents. To populate the Active Directory on a remote domain, run the Enterprise Administration Wizard on that domain.
When using the Storage Exec Enterprise Administration Option (requires Active Directory), the Access Denied error message may appear when you are trying to connect to a remote machine or a remote domain in Windows Server 2003. This can be caused by the user account not being configured as "safe for delegation" in Windows.
In Windows Server 2003 running in native mode, delegation must be enabled for a user account.
To configure the user account:
Open Active Directory Users and Computers.
In the console tree, click Users. Right-click the user you want to configure and choose Properties.
Click the Account tab and under account options, scroll down to Account is trusted for delegation and select it.
Click OK.
Storage Exec computers in the Active Directory typically inherit the global properties of the AD root or organizational unit they belong to (if the OU has settings different from the AD root). However, when a computer is moved to a different OU (or from the Computers container to an OU), the computer does not automatically inherit the destination properties.
To force the moved Storage Exec computer to inherit the properties of the destination OU, restart Storage Exec services on that computer after moving it to the new OU.
When using the Enterprise Administration Option, the service account on the computer where the Administration Console is installed must be the same as the service account on the remote agent to be managed.
If you use the Enterprise Administration Option Wizard to remove a computer from Active Directory, you must reboot that computer.
When upgrading from StorageCentral 5.2 Active
Directory Edition, you must enter the Enterprise Administration Option
(EAO) serial number even if you did not configure 5.2 to use the Active
Directory. Although you are required to enter the EAO serial number,
Storage Exec will not be configured for use with Active Directory until
you run the EAO wizard.
When attempting to add a computer that has only the Remote Administration Console installed to an Enterprise Administration Option (EAO) environment, the following is displayed on the EAO summary page:
Added agent failed: The agent could not be configured. Check the log for details.
The log that is being referred to is the SEADConfig.log. Following is an example of what you will see in the SEADConfig.log:
[0][2004/12/07 22:12:52:276] Configuration for Enterprise Administration Option on computer (QASWCOMPUTER10) has started...
[0][2004/12/07 22:12:52:376] 1060 : The specified service does not exist as an installed service.
[0][2004/12/07 22:12:52:386] Could not stop the QuotaAdvisor Server service.
[0][2004/12/07 22:12:52:386] Computer (QASWCOMPUTER10) failed Enterprise Administration Option configuration.
The result of this scenario is that the computer with the Remote Administration Console will not be part of the EAO environment.
For step-by-step instructions to set up a Network Appliance Filer for use with VERITAS Storage Exec, read the TechNote located at http://seer.support.veritas.com/docs/273085.htm.
You must have administrator privileges on the Network Appliance (NetApp) Filer
to use the Storage Exec Network Appliance Option. Administrator privileges are
required for the UNIX logon account on the NetApp Filer and for the CIFS shares
exposed by the Filer.
Running the Network Appliance Option without administrator privileges will
cause errors and unreliable results.
To back up data that has been reported by
Storage Exec and that resides on the Network Appliance Filer, you
must configure Backup Exec 9.x. For more information, go to
http://atlas.veritas.com/avf/aca-1/dispatch.exe/mynotes/lookup/270396/0.
After upgrading from StorageCentral 5.2 for Network
Appliance Standard Edition to Storage Exec 5.3 with Network Appliance Option, you must create a
VERITAS share on the Network Appliance Filer and then add the Filer to Storage
Exec 5.3.
The StorageCentral SRM for Network Appliance Standard Edition uses
the "Precise" share on the Filer, but Storage Exec 5.3 with Network
Appliance Option uses the "VERITAS"
share on the Filer. During an upgrade, the share cannot be renamed from
"Precise" to "VERITAS", and so cannot create the "VERITAS" share on a Filer.
Therefore, after the upgrade, you must do the following:
After upgrading to Storage Exec 5.3, reboot the computer.
Go to the FilerView on the Filer (http://FilerName/na_admin/), and enter a user name and password to access the FilerView.
On the FilerView, go to CIFS, then to Shares, and then to Add to create the VERITAS
share.Start the Storage Exec 5.3 Microsoft Management Console. On the left tree view, right-click My Computer, and then click Properties.
Click the Network Appliance tab and add a Filer.
Enter a user name and password.
Click OK or Apply on Properties to close the dialog box.
Storage Exec backup jobs can be submitted to any Backup Exec remote media server. However, if the remote media server is running Backup Exec version 9.1 or 10.0, then the location where the data resides must also have the Remote Agent for Windows Servers (RAWS) agent of the same version installed.
Processing large numbers of files (20,000+) using the Back Up With Backup Exec Wizard can result in a significant time delay before the job is submitted.
The Disk Drive Summary report will fail to report on drives mapped to Windows Server 2003 and XP computers. Security enhancements for Windows XP and Windows 2003 have restricted access to mapped drives. Reports can be run on the computers directly, just not via mapped drives.
Viewing Active HTML reports via Internet Information Server (IIS) is not supported. When an Active HTML report is displayed by Internet Explorer via IIS, the report does not display the table of information and does not allow drill down reporting.
View the Active HTML report using the "DeviceName:\FolderName\FileName.htm" or "\\ServerName\Share\FileName.htm" formats.
Instead of serving the reports directly using IIS, create an HTML index document with links to a Windows share containing the files. Internet Explorer will obtain the files using the "\\ServerName\Share\FileName.htm" method, which will display the data correctly.
A share needs to be created on the server holding the files. The default location for reports, C:\Program Files\VERITAS\Storage Exec\Reports, is shared as "WQReportParameters". The HTML index document should contain links to each report in the following format:
<a href = "\\Servername\WQReportParameters\reportname.htm"> Report Name </a>
On computers running Microsoft Windows Server 2003 with the Internet Explorer Enhanced Security Configuration, Active HTML reports received via e-mail may not be viewable. To view these reports, save the files to the local drive and view the reports from Windows Explorer.
When you create a report with an HTML (also called a static HTML) output format, there may be a discrepancy between the header, which may state that many thousands of files were found, and the actual number of files presented in the report. This is because a static HTML report cannot display more than 1000 files.
A non-administrative user cannot run the Disk Drive Summary report. This is because the report requires access to administrative shares on the server. To work around this issue, set a managed resource on all the drives on the system using the Partition Alert space allocation policy. Then a non-administrative user may run the Space Allocation Summary report against the local drives to see the disk utilization.
If you want to open, move, copy, or delete a file listed in an Active HTML report, you must include the file’s path in the list of columns that will appear in the report. You specify the path by including the Display Fields column “Path” when you create or modify an enhanced report query.
To view a log file, a non-admin user must have rights to the UNC path on which the log file resides. Users receive an "Access is denied" error if they have insufficient rights to the UNC path. To allow a user to view the reports log file, create a new share on the drive where Storage Exec is installed and grant the user Read access rights.
Some user interface abnormalities can occur when viewing active reports on computers running Windows XP. (For example, when viewing an Active HTML-format report using the Windows XP theme, clicking in the report grid’s vertical scroll bar will not move the display up or down a page at a time.) To resolve the issue, change your screen theme properties from Windows XP style to Windows Classic style. To change the style, right-click an empty space on the desktop, and then click Properties. On the Themes tab, select "Windows Classic" in the Theme box.
When printing a report to a printer that contains Unicode characters in the printer name, the report will always print to fit. For example, if the report has 10 columns, it prints only the number of columns that can fit to the page. The rest of columns are not printed. To prevent this, make sure that the name of the printer does not contain Unicode characters.
When running the SEReport.exe at the command
line while using a parameter file, if the Enterprise
Administration Option (EAO) has been configured by running the
EAO wizard, the parameter file will cause the following error
message to display:
Could not find the key in the registry.
To work around this issue, do any of the following:
Do not run the EAO wizard, which configures Storage Exec for use with Active Directory.
Do not use a parameter file.
Use the Administration Console instead of the command line interface.
Find the Lightweight Directory Access Protocol (LDAP) report name and enter it in the parameter file instead of entering the Report Name.
To find out what the LDAP report name is:
Use the Administration Console to run the report that you want to put in the
parameter file, and schedule the report to run tomorrow.Go to \Program Files\VERITAS\Storage Exec\Reports and open the file
that begins with 'SR'. The entry after '/R' is the LDAP report name.
An example LDAP report name is:
/R "LDAP://CN=Disk Drive Summary,CN=ReportSet,CN=5.0,CN=StorageCentral
SRM,cn=wquinn,DC=QASWW200302DOM,DC=nsmg,DC=veritas,DC=com"
When EAO is NOT configured, the correct way to use the report name in
the parameter file is /R "Disk Drive Summary".
Adding a user to the SCWrite group only allows a user to access the product as it is shipped in its unmodified configuration. It does not allow the user unlimited access to the file system, or the Active Directory beyond the WQuinn object under the domain root. If a user does not have access to a file system, registry, or AD object beyond those that are part of Storage Exec, adding the user to the SCWrite group will not grant privilege to access them. In addition, if a user is denied access to any object, including those that are part of Storage Exec, adding the user to the SCWrite group will not allow this user access to the object. This includes file system, registry and AD objects.
For example, if UserA is denied all access to the folder C:\Program Files, and Storage Exec is installed in C:\Program Files\VERITAS\Storage Exec then even if UserA is a member of SCWrite, he will still not be able to run Storage Exec. The SCRead and SCWrite groups are only used to facilitate access to Storage Exec, not to guarantee it.
On a Windows 2003 server, if you attempt to delete a file from a share while viewing an active report, you may receive an access denied error. This is because when a share is created in Windows 2003 Server, the default permission granted for any user is set to "Read only." To resolve the issue, make sure you grant permission for the specific user to either "Change" or "Full Control."
The SCRead and SCWrite groups will be created if one of the following is true:
The user is a member of the Domain Admins group
The user is a member of the BUILTIN\Administrators group and the operation is taking place on a domain controller
The SEClusterConfig command, documented in the “Command Line Interface” appendix, is not supported in Storage Exec 5.3.
The content of section "Reconfiguring the Storage Exec Resource" in appendix "Cluster Support in Storage Exec" of the Administrator's Guide has changed. View the new contents in section Appendix "Cluster Support in Storage Exec" of this Readme file.
The content of section "VERITAS Cluster Server Support" in appendix "Cluster Support in Storage Exec" of the Administrator's Guide has changed. View the new contents in section Appendix "Cluster Support in Storage Exec" of this Readme file.
If you upgrade Storage Exec to 5.3 in a clustered environment, upgrade all of the licensed nodes to 5.3 before you modify existing policies or managed resources.
When switching between High Contrast Mode and Normal Contrast Mode, you must close and restart the Administration Console for changes to take effect.
Users with non-administrative rights cannot view the audit trail from the Storage Exec console. Users who try to view the audit trail receive the following message: Unable to make connection to source: Provider=Microsoft.Jet.OLEDB.4.0;datasource=\\SERVERNAME\C$\Program Files\Veritas\Storage Exec\DB\SCAudit.mdb. To allow users with non-administrative rights to view the audit trail, change the Storage Exec data source for the audit database to a location which the user (or SCWrite group) has READ permission. Refer to the Storage Exec Administrator's Guide for instructions to change the audit data source.
Under some circumstances, trend data for Real Time Allocation objects may be duplicated erroneously on a cluster shared resource. This causes the user interface to show duplicate quota objects. Additionally, this creates duplicate entries in the SQL Trend Database for the quota objects on that cluster.
Some user interface abnormalities can occur when viewing active reports on computers running Windows XP. (For example, when viewing an Active HTML-format report using the Windows XP theme, clicking in the report grid’s vertical scroll bar will not move the display up or down a page at a time.) To resolve the issue, change your screen theme properties from Windows XP style to Windows Classic style. To change the style, right-click an empty space on the desktop, and then click Properties. On the Themes tab, select "Windows Classic" in the Theme box.
Microsoft Windows XP Service Pack 2 (SP2) includes many changes to existing Windows security functionality. One of these changes includes enabling the Internet Connection Firewall by default. After installing Windows XP SP2 you cannot push install Storage Exec Agents to remote computers without turning the Windows Firewall option off. This option affects other Storage Exec functionality as well. See http://www.microsoft.com/athome/security/protect/default.aspx for information on turning the option off.
If you apply the Windows XP Service Pack 2, and Storage Exec 5.3 is already installed, you must restart the services. To restart the services, click Start, then click Control Panel, then click Administrative Tools, and then click Services. Right-click the QuotaAdvisor Server service, and click Restart.
If you apply the Windows XP Service Pack 2, and the Windows Firewall was not enabled, and then Storage Exec 5.3 is installed and the Windows Firewall is enabled, you must restart the services. To restart the services, click Start, then click Control Panel, then click Administrative Tools, and then click Services. Right-click the QuotaAdvisor Server service, and click Restart. Follow the same steps to restart the Filescreen Server service.
When installing Windows XP Service Pack 2, the Windows Messenger Service is stopped by default. Storage Exec notifications cannot be sent unless the Messenger Service is running.
To restart the Windows Messenger Service:
Right-click My Computer and select Manage.
From the left pane of the Computer Management dialog box, expand the Services and Applications tree.
Click Services.
From the Services pane, right-click Messenger and then choose Properties.
On the Messenger Properties dialog box, change Startup Type to Automatic.
Click Apply and then click the Start button.
After the services have started, click OK.
When you run an Active HTML report on a computer with Windows XP Service Pack 2 installed, the report displays the message, "Your current security settings prohibit running ActiveX controls on this page. As a result, the page may not display correctly."
This is due to the Windows XP SP2 Local Machine Zone Lockdown feature. Prior to Windows XP SP2, the content on the local file system, aside from that cached by Internet Explorer, was considered to be secure and was assigned to the Local Machine security zone. With Windows XP SP2, Local Machine Zone Lockdown will be even more restrictive than the Internet zone. As a result, scripts and Active X controls will not run.
For more information on this, see "Internet Explorer Local Machine Zone Lockdown" on the Microsoft Web site at: http://www.microsoft.com/technet/prodtechnol/winxppro/maintain/sp2brows.mspx#XSLTsection132121120120
Information bar and security warning messages appear when reports are run in Active HTML-format on Windows XP Pro Service Pack 2 computers. This is due to the Windows XP SP2 Local Machine Zone Lockdown feature. For more information on this feature, see http://www.microsoft.com/technet/prodtechnol/winxppro/maintain/sp2brows.mspx#XSLTsection132121120120
To view Active HTML reports on XP SP2 computers:
Click OK on the Information Bar prompt which is displayed after the report appears.
Click the Information Bar and select Allow Blocked Content.
Select 'yes' on the Security Warning prompt that comes up.
You will not be able to push install to remote Windows XP Service Pack 2 computers because some Storage Exec operations create an exclusion in the Microsoft firewall. Additional information regarding Windows XP SP2 and changes to its firewall functionality can be found on Microsoft's website.
When viewing an Active HTML-format report using the Windows XP theme under Windows XP, clicking in the report grid’s vertical scroll bar does not move the display up or down a page at a time. Changing to the Windows Classic theme gives the desired behavior.
Silently installing a remote agent on a computer running under Windows XP Service Pack 2 is not supported.
Windows XP Service Pack 2 machines are not supported under Storage Exec preferred computers and groups.
Incorrect function: If a volume has been previously disabled using the SEAlloc /-z command, and then a user attempts to create, modify, or delete a space allocation managed resource on the disabled volume, an Incorrect function error message displays. Storage Exec returns the same error message if the user attempts to apply a space allocation policy to an existing space allocation managed resource on a disabled volume.
The server process could not be started because the configured identity is incorrect. Check the username and password.: If you get this message when trying to launch Storage Exec, read the TechNote located at http://seer.support.veritas.com/docs/266231.htm.
This section provides updates and additions to the Storage Exec Administrator's Guide.
General
In two sections ("Changing Properties for a
Folder Limit or User Limit Managed Resource Type" and "Changing Space Allocation Policy
Properties"), add the following paragraph to the description of
the Disk space limit field:
The value you enter for the disk space limit can be overridden
by the value in the Minimum limit field on the Space
Allocation global property tab; for more information about
this field, read the section "Setting Space Allocation
Properties."
Chapter "Installing Storage Exec"
The steps in the section “Configuring Microsoft SQL Server as the Centralized Storage Exec Database” are replaced by the following steps:
Configure the Microsoft SQL Server to enable SQL Server authentication.
On the computer on which Storage Exec is installed, navigate to install-directory\DB.
Type SESQLConfig.exe followed by the appropriate switches. The following switches are available.
Note: Running SESQLConfig.exe with the /A, /U, or /C switch will delete the existing SQL Server SCSRMDB database.
SESQLConfig.exe uses Microsoft SQL Server’s isql command prompt utility to install or convert the Microsoft SQL Server database for Storage Exec. If you want to run SESQLConfig.exe with the /A, /U, or /C switch to install or convert the SQL Server database on a remote computer, make sure that the Client Tools for the SQL Server are installed on the local computer.
| Switch | Description |
| /A | Installs a Microsoft SQL Server database for Storage Exec in ANSI format. |
| /U | Installs a Microsoft SQL Server database for Storage Exec in Unicode format. |
| /O | Configures an ODBC DSN for the Microsoft SQL Server database for Storage Exec. |
| /C | Converts the Microsoft SQL Server database for Storage Exec to Unicode. |
| /S | Uses the Microsoft SQL Server that is installed on the remote computer identified by “server_name” for Storage Exec. If you do not use the /S switch, the SQL server on the local computer will be used. |
| /Q |
Specify the user name for a SQL Server account that can create and access databases, tables, and indexes. |
|
/P |
Specify the password for this SQL Server account. |
Use the following syntax:
SESQLConfig.exe /A [/O] [/S “server_name”] [/Q “user_name” [/P “password”]
SESQLConfig.exe /U [/O] [/S “server_name”] [/Q “user_name” [/P “password”]
SESQLConfig.exe /O [/S “server_name”] [/Q “user_name” [/P “password”]
SESQLConfig.exe /C [/S “server_name”] [/Q “user_name” [/P “password”]
Set the appropriate user permissions to the SCSRMDB database.
Note: You are prompted for the user name and password if it is not specified on the command line.
Close the Administration Console and restart the QuotaAdvisor Server and FileScreen Server services.
Chapter "Getting Started"
In the section "Setting Space Allocation
Properties," the following text is
the revised description of the Minimum limit field:
Type the smallest disk space limit (in megabytes) that can be assigned to a managed resource. This minimum limit applies only to percentage limits, not limits you specify when you create a space allocation policy having a specific disk space limit.
For example, you set this limit to 1MB. Then you create a space allocation policy with a disk space limit of "100% of current used," and then apply the policy to a managed resource containing 250KB of data. The resulting managed resource will have a space allocation limit of 1MB, not 250KB.
In another example, you set this limit to 1MB and then you create a space allocation policy with a disk space limit of 50KB. If you use the policy to create a managed resource, the resulting managed resource will have a space allocation limit of 50KB.
This minimum limit applies when new managed resources are created and when a space allocation policy is applied to an existing managed resource.
In the section "Viewing Version Information," the following text is now available to describe the Property Level field:
If you have installed the Storage Exec Enterprise Administration Option, the Property Level field also displays. The value in this field indicates from where your computer is getting its properties. The properties can come from your computer, your Organizational Unit, or the domain.
Chapter "Audit Trail"
In the section "Introduction to Audit Trail," delete the paragraph that begins, "To see the audit records for all computers in the domain, use a centralized Microsoft Access database."
Chapter "Space Allocation"
In the section "Setting Up Space Allocation Alarm Notification," the definition of the Subject field now includes the following text: You can use any of the macros that are available in the Message field. To use a macro, type the macro in the format in which it displays in the Message field, such as [OBJECT NAME].
In the section "Setting Reports to Run for Space Allocation Alarms," the definition of the Save to field now includes the following text: You can type the folder name or use the following macros: [USER NO DOMAIN], [OBJECT NAME SHARE], and [OBJECT NAME]. For a definition of these macros, see the definition of the Message field in “Setting Up Space Allocation Alarm Notification.”
Chapter "File Blocking"
In the section "Setting Up File Blocking Alarm Notification," the definition of the Subject field now includes the following text: You can use any of the macros that are available in the Message field. To use a macro, type the macro in the format in which it displays in the Message field, such as [OBJECT NAME].
In the section "Setting Reports to Run for File Blocking Alarms," the definition of the Save to field now includes the following text: You can type the folder name or use the following macros: [USER NO DOMAIN], [OBJECT NAME SHARE], and [OBJECT NAME]. For a definition of these macros, see the definition of the Message field in “Setting Up File Blocking Alarm Notification.”
Chapter "Report Queries"
In the section “Creating a New Enhanced Report Query,” add this note to step 6, which documents the Display Fields dialog box:
Note: You must select the Path column if you want to later open, move, copy, or delete a file listed in an Active HTML report that uses this report query.
Chapter "Reports"
In the section “Setting Format Properties for a Report,” add this paragraph to the description in the Active HTML row:
If you want to open, move, copy, or delete a file listed in an Active HTML report, you must set up the associated report query to include the Path field. For more information, see the section “Setting Display Field Options for Report Queries” in the "Report Queries" chapter.
Appendix "Command Line Interface"
In the section “Command SEAlloc,” add the following to the description of the /P, /P:KB, /P:MB, /P:GB, /R, /R:KB, /R:MB, and /R:GB switches: “The value must be a whole number (for example, 10) rather than a fractional value (for example, 10.50).”
In the table that documents the SEAlloc command’s switches, add the following to the description of the /[-]Z switch: “Use this switch only with a lettered drive (for example, C:). Do not use the /[-]Z switch with a mount point.”
In the section "Command SEAlloc," the following text changed:
In the list of SEAlloc switches, the description of the /[-]Z switch now includes the following additional information: [/DEFER] allows deferral of enable/disable until the next reboot if files are open on the volume.
In the list of syntax examples, the example
SEAlloc [\\server] /[-]Z /O "object"
should now be
SEAlloc [\\server] /[-]Z [/DEFER] /O "object"
The SEClusterConfig command, documented in the “Command Line Interface” appendix, is not supported in Storage Exec 5.3.
Appendix "Cluster Support in Storage Exec"
The contents of section "VERITAS Cluster Server Support" are replaced by the following:
Storage Exec does not have direct support for VERITAS
Cluster Server. However,
the registry replication feature of VCS may be used to maintain
consistency of
Storage Exec registry information.
The following keys should be replicated:
HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\Storage Exec\5.0\Definitions
HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\Storage Exec\5.0\Groups
HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\Storage Exec\5.0\Policies
HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\Storage Exec\5.0\ReportSet
HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\Storage Exec\5.0\Rules
HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\Storage Exec\5.0\ServerPolicies
HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\Storage Exec\5.0\Collector
HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\Storage Exec\5.0\Prefmachines
HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\Storage Exec\5.0\Rules
HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\Storage Exec\Signature
You must also back up the registry entries for shared drives.
For example, if
a shared disk has a partition K, then you must add an entry to the
backup list:
HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\Storage Exec\5.0\Devices\K.
If there are several logical drives on the same shared disk, for
example, K and
S, you must add entries for each logical drive to the backup list:
HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\Storage Exec\5.0\Devices\K
HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\Storage Exec\5.0\Devices\S
See the VERITAS Cluster Server System Administrator’s Guide for
information on
configuring registry replication.
The contents of section "Reconfiguring the Storage Exec Resource" are replaced by the following:
You should reconfigure the Storage Exec Resources when any of the following occurs:
A new shared disk is added to a group. The Cluster Configuration Wizard will detect the new shared disk, but you must reconfigure the group.
A new partition is created on a shared disk.
Changes are made to shared disk settings.
To reconfigure the Storage Exec resource:
On the management pane, select Information Desk.
Under Configuration, select Configuring Storage Exec for a clustered environment.
On the Welcome screen, click Next.
Select Add, remove, or reconfigure the Storage Exec resource for groups that have shared disks, and then click Next.
If a new partition was created on a shared disk or if changes were made to the shared disk settings, proceed to step 6.
If a new shared disk was added to the group:
On the Configure screen, click Next.
On the Group Settings screen, from the Groups with the Storage Exec resource column, select a group that has changed, and then click the right arrow to move the group to the Selected groups column.
Click Next, and then click Finish.
The group is now reconfigured. You have completed this procedure.
On the Configure screen, from the Groups with the Storage Exec resource columns, select a group that has changed and then click the left arrow to move the group to the Groups column.
Click Next, and then click Finish.
On the management pane, select Information Desk.
Under Configuration, select Configuring Storage Exec for a clustered environment.
On the Welcome screen, click Next.
Select Add, remove, or reconfigure the Storage Exec resource for groups that have shared disks, and then click Next.
On the Configure screen, from the Groups column, select the group that was changed, and then click the right arrow to move the group to the Groups with the Storage Exec resource column.
Click Next, and then click Finish.
Appendix "Permissions"
Add this note at the very end of the section "Standard Storage Exec Security:"
Note: The SCRead and SCWrite groups will be created if one of the following is true:
The user is a member of the Domain Admins group
The user is a member of the BUILTIN\Administrators group and the operation is taking place on a domain controller
To enable logging, read the TechNote located at http://library.veritas.com/docs/273364.
When a space allocation policy is applied to a system partition, Storage Exec will apply a device capacity quota to the partition instead of the space limit specified in the policy. The device capacity quota will be applied as a passive limit that is the same size as the partition.
Do not include drives named A: or B: when creating quota policies. The error message The system cannot find the path specified. will be returned if drives named A: or B: are used in the quota policy.
To receive File Blocking and Quota notification as well as report emails, the following conditions must exist:
The services account (Quota as well as
File Screening) and the
Report server should have access to the user's Exchange mailbox. If the
Exchange
Server is in a different domain then there should be a trust relationship
between the domain that the services account is in and the Exchange Server domain.
The logged-on user account, the services
account (Quota as
well as File Screening), and the
Report server should have access to the user's Exchange profile.
If you change the Exchange profile and password in
the global
properties, then you must restart the services as well as the MMC UI.
To check your Storage Exec version, do one of the following:
From the Storage Exec management pane, right click My Computer and then select Properties
From the Help menu, select About Storage Exec
Active space allocation resources are not
allowed on the Microsoft Windows installation directory. When the
Windows operating system boots, it must create new files in the
Windows directory. If it cannot do so, the operating system fails
to boot.
Also, if you try to create an active user space allocation resource
on the root of the volume, the message 'Parameter Incorrect' is
displayed, since placing a quota on the root of a boot partition is
effectively the same as placing a quota on the \Windows folder,
which could make the system unbootable.
Placing an active quota limit on a Storage Exec folder can cause the application to stop working if the limit is exceeded. This is true for all applications in the Program files folder.
The QaQuotaV4.dat file is a driver metadata file which is specific to the volume on which it resides. It contains the quota information for the volume, and must reside on the volume to which it applies, much as filesystem metadata resides on the volume it describes. Maintaining the metadata on the volume in question allows for cluster shared volumes, hardware reconfigurations, etc. The file is installed without user location selection because it must reside on the root of every volume. You can not move or copy the file to an alternate location. The file will be removed from the system if you select the option to remove all Storage Exec data when uninstalling. You may manually remove the file at a later time.
This section identifies some problems you may encounter with Storage Exec and offers suggestions for resolving the issue.
Administration Console
Managed Resources Fail to Display (1 of 2)
Problem: If you are at the managed resource grid and attempt to
turn on quotas on a NetApp Filer volume that is online, nothing happens
and no error message displays.
Explanation: This may happen when there are quotas defined for a
different volume that is offline.
Possible solution: Wait until all volumes are online before turning on
quotas.
Managed Resources Fail to Display (2 of 2)
Problem: Managed resources on a Network Appliance Filer that
previously displayed in the list of managed resources no longer show
there.
Explanation 1: If a managed resource that resides on a Network
Appliance Filer is renamed, Storage Exec will not know about the newly
renamed resource. The resource will no longer display in the list of
managed resources.
Explanation 2: If you are at the managed resource grid and
attempt to restart quotas on a Network Appliance Filer volume that is
online, the quotas for that volume may disappear and be replaced with an
entry that reads “quotas off.” This may happen when there are quotas
defined for a different volume that is offline. Possible solutions: (a)
Restart quotas only when all volumes are online. (b) Wait until all
volumes are online before restarting quotas.
Auto Detected Users or Folders Space Allocation Managed Resources Do Not Get Specified Policy
Problem: When an auto detect users or folders space allocation
managed resource is created on a resource, the users or folders are
correctly detected and space allocation managed resources get created
for them. The space allocation managed resources for auto detected users
or folders correctly receive the policy settings. However, the Policy
column of the managed resource details pane shows blanks for those
resources.
Explanation: This can happen if an active user or folder space
allocation managed resource on the profile of the logged-on user (for
example, %SYSTEMROOT%\Documents and Settings\username)
has exceeded its limit.
Solution: Delete the user or folder space allocation managed
resource on the logged-on user's profile or make the space
allocation managed resource passive by selecting its Passive Limit
option.
Microsoft Exchange was Configured on Mail Tab in Domain Properties, but the Global Address Book Browse Buttons are Unavailable
Problem: Microsoft Exchange was configured on the Mail tab in the domain properties, which should enable the browse buttons on the Mail and Report tabs in the Space Allocation and File Blocking policy properties as well as managed resource properties. However, the browse buttons are not available.
Explanation: The property level on the local server is not pointing to the root of the domain, so the local server cannot receive the Exchange configuration settings in the local registry. Because the local registry does not have Exchange configuration settings, the browse buttons are not available.
Solution 1: If the domain root level is the only level that has properties, then right-click on the local server and choose Clear Properties. The property level will point to the root of the domain, and can receive the Exchange configuration settings and all other settings defined in the domain properties. The browse buttons will be available.
Solution 2: If you want the local server to receive properties from its OU level, for example, then configure Exchange on the Mail tab in OU properties. Right-click on the local server and choose Clear Properties. The property level will point to the OU level, and can receive the Exchange configuration settings and all other settings defined in OU properties. The browse buttons will be available.
Solution 3: If you want the local server to receive its properties from itself, then configure Exchange on the Mail tab in computer properties. The browse buttons will be available.
Space Limit is not Enforced
Problem: Space limit is not being enforced.
Solution: Check the policy to make sure it is not passive. If the policy applies only to specific users, make sure the files are owned by those users. If an overdraft has been specified, the limit will not be enforced until the limit plus the overdraft is exceeded. If "Always save open files" is selected, the limit will not be enforced until after handles to open files have been closed.
Storage Exec Allows 10.1 MB Copied to a Directory That Has a 10 MB Space Limit
Problem: Storage Exec allows 10.1 MB to be copied to a directory that has a 10MB Space Limit.
Explanation: Storage Exec uses a file system filter driver called QaFilter to enforce space allocation limits. When a user thread makes a request for the file system to allocate space for the file, QaFilter checks to see if the request would cause the limit to be exceeded, and fails the request if so. Otherwise the request is passed to the file system. In some cases, the file system, particularly NTFS, will allocate more space for the file than was actually requested by the user's I/O. When this happens, it is possible for the user to slightly exceed the limit. Future requests for more space will be failed, however.
Usage Amount for a Space Allocation Object in Storage Exec Does Not Match Windows Explorer Size for a Directory
Problem: The amount used for a space allocation object in Storage Exec does not match Windows Explorer size for a directory.
Explanation: Storage Exec counts allocated space for files, not the data size. This can be significantly different with compressed or sparse files. The "Size on disk" in Windows Explorer is the allocated space, and should match Storage Exec's usage amount. In the case of the root directory of a volume, Windows Explorer reports the space used on the entire partition, which includes file system metadata. Storage Exec reports the sum of the allocation sizes of the files beneath the root directory. Therefore, these counts should not be expected to match.
Reports
Disk Drive Summary Report Shows Different Figures in a Drill-Down
Problem: The space used numbers in the Disk Drive Summary report
and in drill downs on individual and All Local Drives do not match.
Explanation: The Disk Drive Summary report does not use the
global filtering settings used by the other reports because it displays
volume information about each volume, rather than totaling file usage
statistics on all the files on a volume.
Solution: To make the totals match, use the Administration
Console and right-click the computer where the server totals are
different. (In the Storage Exec Enterprise Administration Option,
right-click the root.) Select the Properties option. Then select
the Reports tab and clear Exclude OS Files, Exclude DLL
Files, and Exclude Administrators.
Error Messages
"Log in Failure"
Problem: The Log in failure error
message displays.
Explanation: This message displays when access to the computer is
denied. Access may be denied if the space allocation and file
blocking services cannot log in.
Suggested solutions:
Check access to the computer
If this computer is in a different domain than the current login account, then do the following:
Create a trust between the domains
Add the current user to a known group in the destination domain
"Server threw an exception"
Problem: The Server threw an exception
error message displays.
Explanation: If the QuotaAdvisor service is running as a member
of a specified local account other than System on an XP computer, you
may receive this error when creating or modifying a Storage Exec policy.
This is especially true if you attempt to create the policy with a
drag-and-drop operation.
Resolution: If you run the services as a member of the Domain
Admins group (as recommended in the Storage Exec documentation), this
problem will not occur.
Upgrade Issues
Upgrade from StorageCentral 5.0 or 5.1 failed
Problem: The upgrade from StorageCentral 5.0 or 5.1 to Storage Exec 5.3 failed.
Explanation: The upgrade requires certain files that were placed in the %TEMP% folder (%SYSTEMDRIVE%\Documents and Settings\%USERNAME%\Local Settings\Temp) when StorageCentral 5.0 or 5.1 was installed. If these files are not present, the upgrade to 5.3 will fail.
Solution: Restore these files from a system backup made just after StorageCentral 5.0 or 5.1 was installed. If you do not have these files backed up, you are not able to upgrade from 5.0 or 5.1 to 5.3.
Other Issues
Unable to Connect to a Server
Problem: You cannot connect to a server.
Possible explanation: While installing or upgrading Storage Exec,
the installation setup failed to create the necessary services.
Resolution: Run createservice.exe to create the necessary
services. Follow these instructions:
Log on to the server after it reboots.
From a command-line prompt, change to the install-directory\bin folder.
Type the following:
createservice -c "QuotaAdvisor Server" "QuotaAdvisor Server" "seqasvr.exe" "domain-name\username" "user-password"
createservice -c "FileScreen Server" "FileScreen Server" "sefssvr.exe" "domain-name\username" "user-password"
where domain-name, username, and user-password are the server’s log-on credentials.
Email is Not Received From Alarms
Problem: A space allocation or file blocking alarm is configured
to email a notification to the user, but no email is received. That the
alarm level was triggered can be verified by checking the application
event log for the alarm message.
Suggested solutions:
Verify email settings:
If you are not running the Storage Exec Enterprise Administration Option, check the Mail tab in the server global properties (see section “Setting Mail Properties” in chapter “Getting Started”). Verify the correct mail server is specified, and the sender address and password are correct. Verify that the mail server is reachable from the server running Storage Exec using the Test button.
If you are running the Storage Exec Enterprise Administration Option, check the Mail tab (see section “Setting Mail Properties” in chapter “Getting Started”) in the console root global properties "Storage Exec (your domain)." Verify the correct mail server is specified, and the sender address and password are correct. Verify that the mail server is reachable from the server running Storage Exec using the Test button.
If you selected the Use Active Directory for email check box (described in section “Setting Mail Properties” in chapter “Getting Started”) in the server or AD properties, verify the user account has an email address in Active Directory's Users and Computers. The email address appears on the General tab of user account properties.
Check the policy alarm settings. On the policy Alarm Threshold Settings tab, click the Actions button. Make sure the Mail To field is filled in. Also verify a message has been entered. (For more information about these fields, read sections “Setting Up Space Allocation Alarm Notification” and “Setting Up File Blocking Alarm Notification.”) If the policy settings are correct, also make sure this policy was applied to the managed resource, and check the settings in the managed resource itself.
If you are using a macro in the Mail To or Mail CC address fields, verify the macro is configured correctly. For regular email, the macro should read: [USER NO DOMAIN]@domain.com. Also verify the user's logon ID matches his or her email address. For Active Directory or Exchange email, use only [USER NO DOMAIN].
Use the [USER] macro in your message, and review the message sent to the application event log. Verify that the expected user triggered the alarm.
Quota Alerts Are Not Triggered From a Network
Appliance Filer
Problem: Quota violations on the Filer are not detected by the
NetApp proxy and associated actions are not triggered.
Explanation: When a quota is exceeded on the Filer it attempts to
send an SNMP trap to all defined "trap hosts." The Storage Exec
NetApp proxy will process the traps as, and when, they arrive.
Suggested solutions:
Verify the SNMP service on the NetApp Filer has been configured. If it is not, configure it using the instructions in section “Configuring SNMP for Space Allocation on Network Appliance Filers” in appendix “Working With Network Appliance Filers.”
Verify the SNMP component has been installed on the same host as the NetApp proxy by following these instructions:
From the control panel, double-click Add or Remove Programs.
Click Add/Remove Windows Components.
Double-click Management and Monitoring Tools.
Select the Simple Network Management Protocol option if it is not already selected.
Click OK and then click Next. After the wizard finishes running, close the Add or Remove Programs dialog box and the control panel.
If you modified the system by following either suggested solution, you must stop and restart the services on the NetApp proxy.